You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently started to produce formal release candidates for vss/vss-tools by tagging, creating PyPI packages and sometimes also releases. That is good, but in the long term I see no reason to keep them as they just clutter the list of tags and releases, so I am considering removing them when they "get old". One possible process could be to allow release candidate tags/releases to be removed 6 months after the official release of that version. That would give downstream projects sufficient time to migrate to the official release.
If you object to removing RCs after 6 months please comment before 2024-01-01
The text was updated successfully, but these errors were encountered:
We recently started to produce formal release candidates for vss/vss-tools by tagging, creating PyPI packages and sometimes also releases. That is good, but in the long term I see no reason to keep them as they just clutter the list of tags and releases, so I am considering removing them when they "get old". One possible process could be to allow release candidate tags/releases to be removed 6 months after the official release of that version. That would give downstream projects sufficient time to migrate to the official release.
If you object to removing RCs after 6 months please comment before 2024-01-01
The text was updated successfully, but these errors were encountered: