On Wed, Jun 12, 2019 at 4:59 PM Sebastian Berg <sebast...@sipsolutions.net> wrote:
> Hi all, > > we had discussed trying a new strategy to gather release notes on the > last community call, but not followed up on it on the list yet. > > For the next release, we decided to try a strategy of using a wiki page > to gather release notes. The main purpose for this is to avoid merge > conflicts in the release notes file. It may also make things slightly > easier for new contributors even without merge conflicts. > Any comments/opinions about other alternatives are welcome. > > We probably still need to fix some details, but I this will probably > mean: > > 1. We tag issues with "Needs Release Notes" > 2. We ask contributors/maintainers to edit the initial PR post/comment > with a release note snippet. (I expect maintainers may typically put in > a placeholder as a start for the contributor.) > 3. After merging, the release notes are copied into the wiki by the > user or a contributor. After the copy happened, the label could/should > be removed? > > SciPy uses a similar strategy, so they may already have some experience > to do it slightly different that I am missing. > Sounds great to me. It's actually a little more formalized already then what we do for SciPy. I like the "needs release notes" label ideae. Cheers, Ralf
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
