Upgrade path from TAP13 to TAP14

As this is a recurring topic elsewhere this needs it's own issue.

This will be a overarching issue for the collective issues (we may break these out into sub issues):

Discussion of how consumers and producers will handle the upgrade from TAP 13 to 14.
Backwards compatibility of producers
Informing the community of the latest changes

Any support for both formats should be recommendations within the specification itself, backwards compatibility should be advised for at least one prior version.

The specification should be separate to the implementation of the backwards compatibility setup for example there should be no mention of environment variables.

fix TestAnything#13: correct typo

@isaacs

@isaacs Hmm was this closure accidental? I see only a typo fix in that commit, possibly related to #31, not the new upgrade section proposed here.

whoops, that was supposed to close a different PR, my bad.

31 vs 13 🤦

Navigation Menu

Repository navigation

Upgrade path from TAP13 to TAP14 #13

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Upgrade path from TAP13 to TAP14 #13

Description

Activity

jonathanKingston commented on Feb 7, 2015

Krinkle commented on Nov 15, 2022

isaacs commented on Nov 16, 2022

isaacs commented on Nov 16, 2022

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions