Think we already have this as per the issue tracker concept of 'leads' but I do agree formalizing the role a little more would help. I'd really love it if we got back to shipping to a date and not to any set of features, only finished work was being merged back to master, so cutting a release is a ceremony not a struggle.
On Tue, Jun 18, 2013 at 3:48 AM, Andrew Grieve <agri...@chromium.org> wrote: > Idea here would be to label someone as the "Release Master" for each > release. Responsibilities would include: > > - Creating branches > - Managing release bugs > - Nagging people responsible for unfinished release items > - Creating the final release .zip and uploading it > - Announcing the release > - Ensuring that the release process wiki page is up-to-date > > I think this would help make sure releases happen quicker and that release > tasks are not overlooked. It will also help with knowledge sharing I think.
