Conversation
tynanford
marked this pull request as draft
August 31, 2026 16:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is in preparation for creating new releases (#54) and proposes a road map for that:
Create retroactive tags/releases:
1.0 at 2fbe91c (from https://github.com/epics-modules/pyDevSup/blob/master/debian/changelog#L16)
1.1 at ae755cd (from https://github.com/epics-modules/pyDevSup/blob/master/debian/changelog#L10)
1.2 tag already exists, just create github release
2.0.0 at 1e933f3
The next release, 2.1.0, is noted as unreleased here and is planned after #52 is merged
If this sounds good, I can create the tags 1.0, 1.1, and 2.0.0. Then update the links/dates in this CHANGELOG and then it should be ready to merge