Conversation
…eCandidateVersion spec
alecslupu
left a comment
There was a problem hiding this comment.
One small change, and i think is good to go.
|
@alecslupu this is ready for another round (I forget about this PR and it'd be nice to have it for the v0.30 release :D) |
alecslupu
left a comment
There was a problem hiding this comment.
👍
LGTM . let's see how it behaves ..
|
@alecslupu this is ready for another round! I try it out with #14096 and #14109, and apart from some missing requires (like using the About the documentation, the instructions are available at #14066, so we can merge that after this is merged. |
alecslupu
left a comment
There was a problem hiding this comment.
I haven't managed to test it, but reading through it, LGTM
Until now, the
decidim-releaserscript only was working for Patch versions (i.e. from v0.28.0 to v0.28.1).This PR introduces the feature to make Release Candidates using this same tool (i.e. from v0.29.0.dev to v0.29.0.rc1).
For doing that, what I've done is:
ReleasePatchVersion)ReleaseCandidateVersionclassReleaserUtilsmoduleAfter this is merged, the next iteration would be to have a new class from
ReleaseMinorVersion(from v0.29.0.rcX to v0.29.0)As it is specially tricky to actually run this script without making a release, I can confirm that I've used this to create the branches for:
To check that I didn't break anything with the
ReleasePatchVersionrefactor, I've used this to create the branches for:I think this is ready for a merge.