Pyribs roughly follows a trunk-based development model. Previously, for releases, we only released from the trunk (master branch). However, this does not work well if we need to perform a patch release while trunk already has several features implemented for the next release. This PR shifts to the branch-based release model where we create release branches for minor versions. If we need to release patches, we can cherry pick commits from trunk into the release branch and then push the patch release. We will use this to properly release 0.6.2, as 0.6.1 was released with features for 0.7.0 (namely, OMG-MEGA and OG-MAP-Elites).
Description
Pyribs roughly follows a trunk-based development model. Previously, for releases, we only released from the trunk (master branch). However, this does not work well if we need to perform a patch release while trunk already has several features implemented for the next release. This PR shifts to the branch-based release model where we create release branches for minor versions. If we need to release patches, we can cherry pick commits from trunk into the release branch and then push the patch release. We will use this to properly release 0.6.2, as 0.6.1 was released with features for 0.7.0 (namely, OMG-MEGA and OG-MAP-Elites).
TODO
Questions
Status
yapfpytestpylintHISTORY.md