The proposal<http://www.mediawiki.org/wiki/Requests_for_comment/RELEASE-NOTES_bot>is for a bot to parse commit message for special "commands" to add some text to specific sections of the release-notes file. When bot detects a master merge, it will pull the latest release-notes, change it, and merge it to master right away, avoiding any conflicts.
If the bot messes up, or if a more complex file edit is needed, we can do it through the regular git/gerrit process. On Fri, Mar 1, 2013 at 5:28 PM, Chad <[email protected]> wrote: > Well, that's true if you're only building release notes by copy+pasting > the first line. If it's scripted, it's trivial to pull the bug # from the > footer > as well. > > And no, commit messages cannot be auto-generated by Gerrit, as > that changes the sha1. > > -Chad > > On Fri, Mar 1, 2013 at 2:23 PM, Erik Moeller <[email protected]> wrote: > > On Fri, Mar 1, 2013 at 2:20 PM, Jon Robson <[email protected]> wrote: > >> I actually prefer bug numbers in the header. > > > > +1, also useful for release notes. Could the footer line be > > auto-generated for indexing purposes? > > > > Yay for bikeshed topics ;-) > > -- > > Erik Möller > > VP of Engineering and Product Development, Wikimedia Foundation > > > > Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate > > > > _______________________________________________ > > Wikitech-l mailing list > > [email protected] > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
