Skip to content

Conversation

@Krzmbrzl
Copy link
Member

@Krzmbrzl Krzmbrzl commented Jan 1, 2022

Having a separate RELEASE_ID just unnecessarily complicates drafting
releases. Plus, now that we are using different build numbers for every
new build anyway, a separate release ID is really not necessary.

Checks

@Krzmbrzl Krzmbrzl added build Everything related to compiling/building the code release-management labels Jan 1, 2022
Having a separate RELEASE_ID just unnecessarily complicates drafting
releases. Plus, now that we are using different build numbers for every
new build anyway, a separate release ID is really not necessary.
@Krzmbrzl Krzmbrzl force-pushed the build-remove-release-id branch from ff60250 to 6caa808 Compare January 1, 2022 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Everything related to compiling/building the code release-management

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants