Hi! all the "management" stuff is done, I think that it's just matter of demonstrating community readiness/knowing the apache way, which is something rather difuse. Our next board report is due to next April, so arriving there with a second release and exposing our intentions of graduating (previous discussions, voting) should be enough to pass the graduation IPMC vote, IMO.
@mentors, WDYT? br, juan pablo On Wed, Jan 30, 2013 at 6:21 PM, Harry Metske <harry.met...@gmail.com>wrote: > +1 > > but what about graduation, what steps are still necessary, we can't stay in > the incubator forever... > > kind regards, > Harry > > > On 28 January 2013 21:38, Juan Pablo Santos Rodríguez < > juanpablo.san...@gmail.com> wrote: > > > Hi, > > > > 2.9.0 was released last December, and I was wondering if we could release > > 2.9.1, somewhere in late March*. > > > > 2.9.1 would be mainly a manteinance release, including not only ~15 fixed > > issues, or whatever the number of issues solved by then, but also: > > * requirement of at least Java 6 to compile (as Java 6 is being outdated > > this February I think it isn't a break-dealer) > > * ChangeLog published on site > > * initial maven support (JSPWIKI-651) > > * drop TranslatorReader (deprecated since 2.3 and unused in src) > > > > The last one should -technically- be done on 2.10 scope, but it's been > ages > > since it was deprecated and unused... Anyone using it nowadays, is it > safe > > to remove? Thoughts on the other points? > > > > * saying "late March", but meaning "as the points agreed to be included > in > > 2.9.1 are done" > > > > > > br, > > juan pablo > > >
