On Thu, Jan 9, 2020 at 1:25 PM Watson Sato <[email protected]> wrote: > Hello all, > > Time for release of v0.1.48 is close, so the stabilization branch has been > created. > The release is scheduled to happen at the beginning of next week, at the > latest on 14.02.2020. >
Correction, January 14th, (14.01.2020). > > Last time we followed approach of merging fixes to the stabilization > branch, and them merge the stabilization branch to master. > But that showed potential to really complicate the merge of the fixes back > into master. > This approach also left master hanging out with the bugs discovered during > the stabilization phase until after the release was finished, which is not > ideal. > > So this time we propose to do the fixes on master branch and cherry pick > them to the stabilization branch. > The next version milestone is 0.1.49, please use it when resolving issues > and pull requests from now. > When a PR is cherry picked into the stabilization branch, change the > milestone to 0.1.48, so that it is easy to track in which version a patch > was released. > > -- > Watson Sato > Security Technologies | Red Hat, Inc > -- Watson Sato Security Technologies | Red Hat, Inc
_______________________________________________ scap-security-guide mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected]
