On 12 June 2016 at 13:27, Dimitry Andric via llvm-dev <llvm-...@lists.llvm.org> wrote: >> 1) Right after the branch, the version number of the trunk will be >> incremented. I assume this means bumping the major version number, >> taking us to 4.0? IIUC, that's what happened after 1.9 and 2.9. > > 4.0. Since gcc is already at 7.0, we need to catch up! ;-)
Or, we can do like ARM and go from 3 straight to 7! :) >> 2) Following up on the May thread about the release process [1], I'd >> like to make the schedule we've followed for the last few years more >> official by posting somewhere on the web page that we're committed to >> shipping two major releases per year: one in early March (branching >> mid-January), and one early September (branching mid-July), usually >> with one (or sometimes two) "dot" releases in between. > > Having predictable release schedules is nice. If everybody knows the > tree should be in fairly good shape at the point of branching, any heavy > refactoring can be postponed until after such branching (or preferably, > until after the actual release). Yup, +1 for a webpage with all this, in addition to the existing snippet on the homepage. >> 3) Another follow-up from that thread: it's usually the same people >> who test the releases for their platform. Rather than asking everyone >> each time, I'd like to make a list of who's responsible for each >> platform and put that on the web page. Testers can still sign-up or >> resign as they like, of course. Would you testers be OK with this? > > You can put me up for the FreeBSD platform, obviously. And me for ARM and AArch64. cheers, --renato _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
