generally, i consider releasing more often a good idea. but shouldn't we also have some kind of (serious) release plan? yes, we can say we want to release every two weeks, but when does that stop? 1.3-0-beta42 ? yes, there are bugs and yes they need to be fixed, but at some point we need to get a clearer picture how we want to go on. also, what are the constraints for a 1.3.0-final release? all bugs fixed? then we should release beta5 and pronounce a feature freeze and get those bugs fixed.
i'll come up with a list of bugs that either seem to be fixed (but haven't been resolved, verified yet) or are just not valid anymore. Gerolf On 10/20/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > fine by me. i dont mind a release every one or two weeks. > > -igor > > > On 10/19/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > Hey, > > > > If someone (Frank?) is up to helping me a bit this weekend, how about > > putting our beta 5 this weekend. The reason is selfish: we > > (Teachscape) are gonna do a big release this weekend, I just fixed an > > issue I need, and I also would like to use the memory improvements, > > but I don't want to fix on a SNAPSHOT. But it's also a practice round > > to see whether we can release more often. > > > > WDYT? > > > > Eelco > > >
