On Tue, 10 Jul 2007, Karl Fogel wrote:
> "Mark Phippard" <markphip@gmail.com> writes:
> > ... It seems like we are drawing closer to the end of the 1.5
> > development cycle. There is still work to be done for sure, things we
> > all want to see done. I am not suggesting we are ready to branch,
> > because we are not.
> >
> > In the interests of working towards the point when we can branch,
> > however, I think it would be a good time to start defining what is
> > left to do. I know that Dan has been doing a good job maintaining a
> > to-do list for merge tracking in:
> >
> > http://svn.collab.net/repos/svn/trunk/notes/merge-tracking.txt
I'd be happy to move this into another location to provide a single
place in which to track tasks.
> > ... I get the sense that there are a lot of
> > "loose-ends" throughout various aspects of the product that only
> > different sets of people know much about. I think it would make sense
> > to establish some kind of master TODO file in trunk where we can start
> > to record all of the things that need to get done before we branch.
+1, it's absolutely time to start tracking outstanding loose ends on a
checklist.
> > This would accomplish a few things:
> >
> > 1) Increase visibility of what is left to be done.
...
> > 2) It should help with communication and help set our expectations
> > for the release.
...
> > 3) Give us a better idea of when we are going to branch.
...
> > Finally, I am not proposing any kind of high ceremony process or
> > document here. Just a place where people can record things that
> > either they want to get done themselves or maybe no needs to be done
> > before we can release. This issue with the fsfs transaction names is
> > a good a recent example.
>
> Good idea -- how about just making it be the 1.5 release notes file,
> with extra slots for individual "todo" sub-items? As they are done,
> we can just remove them. What remains would be the high-level feature
> and change descriptions, that is, the usual release notes.
Blair echoed the suggestion of a TODO file for tracking the 1.5
release. In the past, we've used such a file for tracking the status
of a feature branch.
A third suggestion would be to use the issue tracker. I suppose I
lean more towards the issue tracker (since it means fewer places in
which we're tracking tasks), but the only thing I feel strongly about
is that we Just Pick One and start using it.
I know there's been a lot of discussion about 2.0, which gets everyone
excited. But how about shipping 1.5, probably the biggest and most
anticipated release since 1.0, before getting too deep into 2.0...
- Dan
- application/pgp-signature attachment: stored
Received on Fri Jul 13 02:00:38 2007