OK. Don't want to be pushy of course. I would suggest we simply replace '0.2' with '0.3' in that sentence myself. (Or perhaps ask -- if we cut a release right now, what if anything would make you say 'oops, that really should have been fixed...') I think we're not releasing nearly often enough myself, and that has implications. But without just about unanimous consent we can't push something out.
On Tue, Sep 29, 2009 at 7:39 AM, Isabel Drost <isa...@apache.org> wrote: > On Mon, 28 Sep 2009 21:08:32 -0400 > Grant Ingersoll <gsing...@apache.org> wrote: > >> > I can drive this and propose we publish 0.2 from code as of this >> > Friday. Is that too soon to polish what's there? > > Sorry, I wanted to spend some time on some of the issues this weekend* - > won't have time before Friday. > > >> Well, we should go through and evaluate what is open and whether it >> really should be in 0.2, instead of just fixing a date and cutting >> things off. There are a few open items that I think need to be in >> 0.2, most importantly the SparseVector speedups. > > +1 > > Isabel > > * http://wiki.upstream-berlin.com/index.php/DevHouseBerlin2 >
