Include versioning to sequencer and compatibility to sequences #2

New Issue

efelon · 2019-04-05T14:11:43+02:00

efelon commented

2019-04-05 14:11:43 +02:00

Giving sequencer a dedicated versioning, where one of the numbers is for compatibility check with sequences.

Versioning

Compatibility.Major.Minor

1.0.0 - first version

Compatibility

Compatibility refers mainly to the interface; What functions need to be provided by a sequence.

Sequencer 2.0.0 may still understand sequences with compatibility of 1, but it is not guaranteed.
This is implemented in the compatibility check of the sequencer.
Sequencer 1.0.0 cannot work with sequences of version 2

Giving sequencer a dedicated versioning, where one of the numbers is for compatibility check with sequences. ## Versioning **Compatibility.Major.Minor** > 1.0.0 - first version ## Compatibility Compatibility refers mainly to the interface; What functions need to be provided by a sequence. * Sequencer 2.0.0 may still understand sequences with compatibility of 1, but it is not guaranteed. * This is implemented in the compatibility check of the sequencer. * Sequencer 1.0.0 cannot work with sequences of version 2

efelon changed title from ~~Include versioning to sequencer and compatibility to step definition~~ to Include versioning to sequencer and compatibility to sequences

2019-04-05 14:21:21 +02:00

efelon referenced this issue from a commit

2019-04-05 16:33:07 +02:00

fixes #2 Introduce versioning to sequencer and seqs Refactored sequencer option handling More robust way to include sequencer.sh to seqs

efelon closed this issue

2019-04-05 16:33:07 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: efelon/shell_sequencer#2