+1 Sounds fine with me. I am still working on the composite buffer support, but I do not think that it is critical to get into a release right away.
On Mon, Jul 28, 2008 at 1:15 PM, W.B. Garvelink <[EMAIL PROTECTED]>wrote: > I'd say stick to the 72 hours. Rushing a release is seldom a good idea > in my experience. > > I haven't yet gotten around to finishing up on DIRMINA-608, but I see > no problems pushing that to M4. > > > Barend > > > > > On Mon, Jul 28, 2008 at 4:07 PM, Julien Vermillard > <[EMAIL PROTECTED]> wrote: > > yep, and me to gather time and fix the distribution :) > > Julien > > > > On Mon, 28 Jul 2008 09:47:04 -0400 > > "Alex Karasulu" <[EMAIL PROTECTED]> wrote: > > > >> +1 to releasing. Do we really have to cut down the 72 hrs? Might > >> want to give some time for people to test it? > >> > >> Alex > >> > >> On Mon, Jul 28, 2008 at 5:19 AM, Emmanuel Lecharny > >> <[EMAIL PROTECTED]>wrote: > >> > >> > Julien Vermillard wrote: > >> > > >> >> Hi guys, > >> >> > >> >> 2.0.0-M2 release is suffering some serious issues : > >> >> - DIRMINA-609 a big perf regression on big message (quite common) > >> >> - the tarballs are fubared, you miss half of the modules > >> >> > >> >> I tihkn we need to redo a release soon (M3), specially for > >> >> DIRMINA-609 > >> >> > >> >> WDYT ? > >> >> > >> >> > >> > +1. > >> > > >> > You can launch a quick vote, and if the PMC aggreed on, we can even > >> > shorten the 72 hours wait to something like 24hours, as we are now > >> > on monday. That make sense for such a big regression. > >> > > >> > Otherwise, I also think that the Write issue should be addressed > >> > correctly in 2.0.0-M4 : > >> > https://issues.apache.org/jira/browse/DIRMINA-577 > >> > https://issues.apache.org/jira/browse/DIRMINA-518 > >> > > >> > (more to come) > >> > > >> > Thanks ! > >> > > >> > -- > >> > -- > >> > cordialement, regards, > >> > Emmanuel Lécharny > >> > www.iktek.com > >> > directory.apache.org > >> > > >> > > >> > > >> > >> > > >