My github account is eskimor. I think the model described in: http://nvie.com/posts/a-successful-git-branching-model/
is a really good one, to get started. If we want to keep changes to a minimum, then the development branch in the model could simply be the current master. The master branch in the model would be the master branch of dmd-stable. Feature branches already exist in form of pull requests. Release/hotfix branches would have to be introduced. A little education of people would be needed. (E.g. where and when to merge things, bugs/features.) Where and how changes are documented. I would volunteer to help writing an automatic upgrade tool. We should, define things there, so reports of breaking changes/deprecations, the developers provide, could then be already in a format the tool can understand. On Thu, 2012-11-29 at 23:49 -0600, 1100110 wrote: > On 11/29/2012 11:17 PM, Rob T wrote: > > On Friday, 30 November 2012 at 04:30:10 UTC, 1100110 wrote: > >> Let's do this thing. > > > > I can help with formulating a process and I can also help write up the > > guidelines and so forth, so I'll sign up. > > > > If we can decide on a road map and write it up, and get enough consensus > > for implementing it, then everyone will know what they should be working > > on, and also what to expect. > > > > How many people do you think we need to get started, 5 or so? > > > > --rt > > > > I've started work on the specification here > https://github.com/D-Programming-Language-Stable/dmd/wiki/Specification > > I'd like for someone else to start with the writeup, since I've pretty > much made my ideal known by this point. > > If you have a github account, give me your user name and I'll add you to > the Project. > > It'll at least give us a public place to define things for right now.