search

silverstripe / cow

Release tool for Silverstripe CMS
BSD 3-Clause "New" or "Revised" License
6 stars 8 forks source link

Allow release planning with "future" versions of upgrade-only modules #182

Closed dnsl48 closed 1 year ago

dnsl48 commented 4 years ago

Hypothesis

Planning a release with "future" versions of upgrade-only modules would allow us to co-plan two recipes and then perform sequential release:publish for both of them quickly.

Real life application

Currently, we have to release CMS Recipe ahead of beginning the release process for CWP Recipe. With this feature we could plan both CMS Recipe and CWP Recipe releases simultaneously, and then on the release day we would only need to run release:publish for both. That could allow us to couple the CWP and CMS releases and prepare CWP release plan before CMS is out.

ScopeyNZ commented 4 years ago

Now that the same team manages the whole process, is there a reason to not remove the "upgrade-only" restriction? We only really had that (IIRC) because CWP release management was very much independent of core.

dnsl48 commented 4 years ago

That's a good point, I didn't think about that. Thanks for chiming in! :)

GuySartorelli commented 1 year ago

This is no longer relevant to the current process.