For the last 2 major TC releases (3.x and 4.x) we've been appointing an open source release manager for the entirety of the major release:
4.x - Rawlin 3.x - Derek IMO this can be a lot of work if there are multiple minor releases inside a major and can be quite a lengthy commitment for one person (sorry Derek and Rawlin). How would everyone feel if we instead appointed release managers for each release (minor or major)....and if we aim for quarterly releases, this will limit the commitment to 3 months for a RM. The lower commitment may also help in finding volunteers. Also, each release (major or minor) has it's own branch derived from master, therefore, there's no reason you can't have different "branch owners" of (for example): 5.0.x 5.1.x 5.2.x (fyi, a RM must be a TC committer) Thoughts? Jeremy
