Hi Norman,
JAMES-1074 must not block M1 release: it does not impact user config,..
.it's only some core discussions :) around API,... that we target for M2.
I have updated it to 3.0 version number.
It may be worth to already define a 3.0-M2 version in JIRA.
Also, not working on repackaging will free up time for the docs.
As I said in other post, I will regulary scp some files to the web site,
and will ping from time to time here to review them.
Yes, the feature set must not rise and we must keep all the existing
ones (such as the mailing lists and all the other ones we may not have
deeply tested in the 3.0 architecture).
Tks,
Eric
On 23/10/2010 09:57, Norman Maurer wrote:
Hi there,
we are mostly ready to cut the M1 release. I will try to push things
to get it out at the end of the next week, so stay prepared for the
upcomming VOTE. After M1 was done I would like to try to get things
stable (api) and cut the next alpha/beta shortly (should not take more
time then 4 weeks). After that we should concentrate on just close
bugs and improve things. No new features should get into the tree
until 3.0 is finally out, so kind of feature freeze. WDYT ?
Bye,
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
