Maybe Dec 1, Jan 1, Feb 1, then final release April 1?
On 11/4/07, Shawn Walker <[EMAIL PROTECTED]> wrote: > > On 04/11/2007, Glynn Foster <[EMAIL PROTECTED]> wrote: > > > > > > S h i v wrote: > > > May I suggest a patched release of the distro atleast with this one > > > particular bug. > > > > > > While all other bugs can have their own correction cycles and can wait > > > for the next planned release, I believe this too important to be left > > > till the next release since till the fix this is a FUD bomb ticking. > > > > One thing that needs to be discussed is how frequently to refresh the > base ISO > > image. With the '1.0' (or equivalent) expected sometime in March/April, > we need > > to come up with the ideal number of ISO refreshes. There's one planned > for > > January, but it might be nice to put another one in before and after > that date. > > This is particularly useful for anyone wanting to hand out a bunch of > CDs at a > > conference or user group. > > > > thoughts? > > I would like to see one built automatically by the system and posted > nightly to make it easy to test regressions. It would be named with a > timestamp or something and put into a "nightly" folder. This would be > a great way to identify build problems. > > I would also like to see a more "formal" test release done every month. > > Just my view, > -- > Shawn Walker, Software and Systems Analyst > http://binarycrusader.blogspot.com/ > > "We don't have enough parallel universes to allow all uses of all > junction types--in the absence of quantum computing the combinatorics > are not in our favor..." --Larry Wall > _______________________________________________ > indiana-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/indiana-discuss >
_______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
