Hello, On Monday 08 December 2008 19:38, Thorkil Naur wrote: > Hello Petr, > > On Monday 08 December 2008 18:36, Eric Kow wrote: > > Hi everybody, > > > > It's time to start gearing up for our first time based release of darcs! > > > > We aim to release darcs 2.2 by 2009-01-15, including some improvements > > from the darcs hacking sprint, a bit of optional Cabal support, and > > Windows stability fixes. > > > > Unfortunately, Jason Dagit has had to step down as Release Manager (for > > lack of time). Fortunately, Petr Ročkai will be taking over in this > > role. Many thanks and good luck to both of you! > > Let me second that: Thanks a lot. > > > We'll be looking > > forward to seeing Jason hacking with us again when he has gotten the > > better of his time commitments. > > > > Note that for this release, we will be experimenting with a notion of > > release branches. More news on that later! > > > > Thanks, > > > > -- > > Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> > > PGP Key ID: 08AC04F9 > > > > This release gives me the opportunity to do something that I have neglected > for a while, namely running over all the (mostly: outstanding) issues in the > bug tracker. This will hopefully get me a better overview of what is there, > as well as some ideas for organizing things, ways of using the various > priority codes, status codes, and topics, for example. And perhaps I will > even manage to clean up a bit. > > Specifically, by Friday this week, I will try to separate all the outstanding > issues into some hopefully suitable groups and produce a list of these > groups. Typical headings of these groups I imagine to be something like: > > 1. Critical bug that we would like to have fixed by next release: In good > hands (meaning assigned to somebody that works on it and that has a good > chance of finishing in time to be included in the next release). > > 2. Critical bug, same as 1, but with noone actually working on it or not > likely, with the present level of activity, to catch the release. > > 3. Less critical bugs. > > 4. Ideas that we can take up at any opportunity. > > And there are probably more. Obviously, this could very well match some of the > status/priority settings presently used, but until I have looked, I really > don't know for sure. > > Equally obviously, I could reflect this grouping in the setting of priorities, > status codes, topics, and perhaps other indicators in the bug tracker itself. > However, I am afraid that if I start doing that and regret some decision on > the way, then it will end up in a terrible mess. So I prefer to do some > homework first, separately. This will also allow me to invite others to > comment on what I am up to. But eventually, of course, the grouping should > end up being reflected in the bug tracker. And this sort of work being done > using the bug tracker directly. > > I am writing since you may find this sort of thing useful in your Release > Manager role. Just so that you know what I am doing. And also giving myself a > deadline to meet. > > Thanks and best regards > Thorkil >
In preparation for this, I have produced http://wiki.darcs.net/DarcsWiki/BugTrackerIssueManagement with a description of my current ideas for managing issues on the bug tracker. Comments from you or other darcs users are most welcome. Thanks and best regards Thorkil _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
