We also need to look at releasing ClickIDE. I assume we go through the
same procedure for releasing a subproject?
bob
Malcolm Edgar wrote:
Yes an RC would probably be good, with a code feature freeze after
that. So it 2.1.0 doesn't drag out.
regards Malcolm
On Mon, May 18, 2009 at 10:12 PM, Bob Schellink <[email protected]> wrote:
Agreed, lets get 2.1.0 out. Probably a RC?
On 5/18/09, Malcolm Edgar <[email protected]> wrote:
Click didn't progress through to a TLP yet as feedback from the Apache
was that the community needed to be bigger. So we will try again in a
few months time.
In the mean time we need to increase the visibility of the framework.
I think a good way of doing this is through a release, and promotion
and some articles.
If we don't time box the 2.1.0 release date, it can drag on forever.
regards Malcolm Edgar
On Mon, May 18, 2009 at 9:50 PM, Adrian A. <[email protected]> wrote:
What do people think about targeting the end of May as the release
date for Apache Click 2.1.0 ?
I would rather see the many issues standing out to be solved first, and
only
after to do a release (otherwise the difference between patches and trunk
will be bigger and bigger each day).
Also, since the voting of moving click to TLP was done, it would be much
nicer if Click 2.1.0 would be released that way (without the incubator
tag).
--
http://incubator.apache.org/click/
