Vinod Johnson - Sun Microsystems wrote: > >> >> I find v0.1 not ambitious enough. I think it is important to do some >> bug-fixes and RFEs that have been completed and lingering around for a >> very long time in some peoples workspaces. Just to release so most >> people can sit on the sideline watching v0.1 being released is not that >> interesting to me (I also want to get rid of a lot of fixes and small >> RFEs I've been carrying for too long). Therefore I'm inclined to merge >> the goals for v0.1 and v0.2 as most of it likely represents completed >> work. Based on what is in Bugtraq, has been added to River and is >> completed in the Sun internal version control system we can make a >> selection of what to put into that first release. Whether there is still >> a need for a release between the first release and the 'meat to it' >> release I find hard to say at this point. >> > Part of what is in play here is how much more time and effort (I would > imagine the effort part would me more process oriented rather than > technical) it would take to do a 0.1 vs a 0.2. If the answer is 'not > that much more' then there seems to be little to be gained from > splitting the two. If it is 'reasonably more' then I think there is > value in having a binary distribution as an initial artifact for people > to be able to download and touch and feel. This value judgment, of > course, comes with the assumption (perhaps misguided) that the slant > initially is towards showing people that we have a binary that works > rather than the magnitude of active ongoing work. > > My 2c.
I can imagine that a release with some bug fixes mightn't get too much contention but would take longer as we thrash around unit tests etc (which I think are essential). If we get into RFE's, from my own past discussions in this area, I know I'm going to have a lot of things to say and a lot of stuff to challenge/thrash out. Basically my view is that will delay the first release far too long. Dan.
