Click 2.1.0 release date?

[Malcolm Edgar <ma...@gmail.com>]

Hi All,

What do people think about targeting the end of May as the release
date for Apache Click 2.1.0 ?

regards Malcolm Edgar

Re: ClickIDE release

[Bob Schellink <sa...@gmail.com>]

Hi Naoki,

Yes that document outlines my current understanding of Apache releases.

I think we should push out ClickIDE after Click 2.1.0.

In the meantime you could setup your OpenGPG public/private key as 
outlined here[1].

Feel free to contact me offline if you have any questions regarding 
these steps.

kind regards

bob

[1]: 
http://incubator.apache.org/click/docs/developer-guide/releasing.html#prerequisites

Naoki Takezoe wrote:
> Hi,
> 
> ClickIDE (supports Apache Click 2.1.0) release is ready.
> 
> But I don't understand a release process completely...
> Should I release ClickIDE according to the following documents?
> http://incubator.apache.org/click/docs/developer-guide/releasing-subprojects.html
> 

Re: ClickIDE release

[Naoki Takezoe <ta...@gmail.com>]

Hi,

ClickIDE (supports Apache Click 2.1.0) release is ready.

But I don't understand a release process completely...
Should I release ClickIDE according to the following documents?
http://incubator.apache.org/click/docs/developer-guide/releasing-subprojects.html

2009/5/19 Bob Schellink <sa...@gmail.com>:
> 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 <sa...@gmail.com> wrote:
>>>
>>> Agreed, lets get 2.1.0 out. Probably a RC?
>>>
>>> On 5/18/09, Malcolm Edgar <ma...@gmail.com> 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. <a....@gmail.com>
>>>> 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/
>>>
>>
>
>



-- 
Naoki Takezoe

ClickIDE release

[Bob Schellink <sa...@gmail.com>]

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 <sa...@gmail.com> wrote:
>> Agreed, lets get 2.1.0 out. Probably a RC?
>>
>> On 5/18/09, Malcolm Edgar <ma...@gmail.com> 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. <a....@gmail.com> 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/
>>
> 

Re: Click 2.1.0 release date?

[Malcolm Edgar <ma...@gmail.com>]

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 <sa...@gmail.com> wrote:
> Agreed, lets get 2.1.0 out. Probably a RC?
>
> On 5/18/09, Malcolm Edgar <ma...@gmail.com> 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. <a....@gmail.com> 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/
>

Re: Click 2.1.0 release date?

[Bob Schellink <sa...@gmail.com>]

Agreed, lets get 2.1.0 out. Probably a RC?

On 5/18/09, Malcolm Edgar <ma...@gmail.com> 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. <a....@gmail.com> 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/

Re: Click 2.1.0 release date?

[Malcolm Edgar <ma...@gmail.com>]

Yes I was a bit surprised by the response too. I think we will get
there we just need to raise the profile.

regards Malcolm Edgar

On Mon, May 18, 2009 at 10:14 PM, Adrian A. <a....@gmail.com> 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.
>
> Very strange. So let me think loud :) :
> #1. - click has very good docs, so there's no need for the users to ask many
> questions. As a consequence the traffic is very small on the lists.
> #2. - click users can build very easily click themselves (as opposed to the
> many projects moved to maven) - so no need to download it. So the traffic is
> small again.
>
> So #1 and #2 being a plus (for me and my simple logic), it is considered a
> minus at apache.org? :)
>
> very strange :).
>
>

Re: Click 2.1.0 release date?

["Adrian A." <a....@gmail.com>]

> I think the explicit concern about the community was a desire for more
> committers.   Click has contributions from a variety of people, but
> needs more people contributing regularly to provide assurances of the
> longevity desired at Apache.
That supposition looks also strange to me :) :
If I compare the SVN check-in logs of Click (even starting from click 
0.6 - so a good few years ago) - it's more constant and high than that 
of many Apache projects.

The backward compatibility level trumps too :).
(e.g. concurrent frameworks like to rewrite from scratch entire new 
releases - of course in an incompatible manner :). Book publishers might 
be charmed by this strategy, user's however aren't :) ).

> I think frequent releases (..) can only help.
I guess there might be a misunderstanding  here too :) :
- the quality of Click trunk code is higher than that of most projects' 
RC release quality. Of course, the "disadvantage" of this is that the 
issue tracker has a very low "bug traffic" level :). Again, this used to 
be a "plus" :).

Adrian.

Re: Click 2.1.0 release date?

[Will Glass-Husain <wg...@gmail.com>]

I think the explicit concern about the community was a desire for more
committers.   Click has contributions from a variety of people, but
needs more people contributing regularly to provide assurances of the
longevity desired at Apache.

It does seem a little paradoxical.  Is there a need for a few rough
edges to irritate users enough to get more involved?  That's how I
came on board Velocity :-)

I think frequent releases (and articles - great idea!) can only help.
Plus a little time.

WILL

On Mon, May 18, 2009 at 5:14 AM, Adrian A. <a....@gmail.com> 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.
>
> Very strange. So let me think loud :) :
> #1. - click has very good docs, so there's no need for the users to ask many
> questions. As a consequence the traffic is very small on the lists.
> #2. - click users can build very easily click themselves (as opposed to the
> many projects moved to maven) - so no need to download it. So the traffic is
> small again.
>
> So #1 and #2 being a plus (for me and my simple logic), it is considered a
> minus at apache.org? :)
>
> very strange :).
>
>

Re: Click 2.1.0 release date?

["Adrian A." <a....@gmail.com>]

> 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.
Very strange. So let me think loud :) :
#1. - click has very good docs, so there's no need for the users to ask 
many questions. As a consequence the traffic is very small on the lists.
#2. - click users can build very easily click themselves (as opposed to 
the many projects moved to maven) - so no need to download it. So the 
traffic is small again.

So #1 and #2 being a plus (for me and my simple logic), it is considered 
a minus at apache.org? :)

very strange :).

Re: Click 2.1.0 release date?

[Malcolm Edgar <ma...@gmail.com>]

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. <a....@gmail.com> 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).
>
>

Re: Click 2.1.0 release date?

["Adrian A." <a....@gmail.com>]

> 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).