On Nov 19, 2013, at 8:59 AM, Till Westmann wrote:

> Hi,
> 
> I think that most of us agree that graduation to a TLP would be the right 
> path. 
> 
> From my point of view there are only 2 open questions right now:
> 1) Should we aim to graduate "all the way" immediately or should we become a 
> pTLP?

All the way.

> 2) Should we create a second incubator release before we attempt graduation 
> (there has been quite a bit of development on the master branch while we were 
> working on the release)?

Second release could make sense, it may take some time to adjust infrastructure 
once you become a TLP (or pTLP)

Final approval for TLP can happen only once a month at the board meeting.

(a) finish the last release steps.
(b) role another release. If not done by Dec. 4 then skip.
(c) graduation votes
(d) TLP in December.

Regards,
Dave

> 
> Thanks,
> Till
> 
> On Nov 19, 2013, at 1:51 AM, Jochen Wiedmann <[email protected]> 
> wrote:
> 
>> [Sorry for the truncated message from some minutes ago.. Was pressing
>> "Send" accidentally. So to continue:]
>> 
>> 
>> As a reminder: Publishing this release will be taken as a sign, that the
>> project is ready for graduation.
>> 
>> So, it seems about time to discuss our further intentions. Our options, as
>> I see them,  are:
>> 
>> 1.) Graduate as a new TLP, as ant has already suggested. I would expect
>> that the board would approve a corresponding request. (After minor
>> discussions, perhaps.)
>> 2.) Become a subproject of another TLP. Problem is, that there is no
>> obvious choice, that would welcome VXQuery. For example, speaking as a
>> member of Apache Commons, I'd personally reject VXQuery as not sufficiently
>> generic. I'd expect at least applicability on DOM nodes, or something like
>> that, with some examples demonstrating the use as part of the documentation.
>> 
>> The main difference between these options: As a TLP, there's addidional
>> work to do. With option 2, that would be done by the parent project. Mainly
>> like it was, except that Incubator was the TLP so far. Additional jobs to
>> do:
>> 
>> - Elect a chair. (I'd suggest Till, as he did an excellent job so far in
>> adapting to the Apache policies, acting as a release manager, and so on.)
>> - Elect a PMC.
>> 
>> 
>> 
>> On Tue, Nov 19, 2013 at 10:48 AM, Jochen Wiedmann <[email protected]
>>> wrote:
>> 
>>> [Sorry for the truncated message from some minutes ago.. Was pressing
>>> "Send" accidentally. So to continue:]
>>> 
>>> 
>>> As a reminder: Publishing this release will be taken as a sign, that the
>>> project is ready for graduation.
>>> 
>>> So, it seems about time to discuss our further intentions. Our options, as
>>> I see them,  are:
>>> 
>>> 1.) Graduate as a new TLP, as ant has already suggested. I would expect
>>> that the board would approve a corresponding request. (After minor
>>> discussions, perhaps.)
>>> 2.) Become a subproject of another TLP. Problem is, that there is no
>>> obvious choice, that would welcome VXQuery. For example, speaking as a
>>> member of Apache Commons, I'd personally reject VXQuery as not sufficiently
>>> generic. I'd expect at least applicability on DOM nodes, or something like
>>> that, with some examples demonstrating the use as part of the documentation.
>>> 
>>> The main difference between these options: As a TLP, there's addidional
>>> work to do. With option 2, that would be done by the parent project. Mainly
>>> like
>>> 
>>> 
>>> On Tue, Nov 19, 2013 at 10:42 AM, Jochen Wiedmann <
>>> [email protected]> wrote:
>>> 
>>>> As a reminder: Publishing this release will be taken as a sign, that the
>>>> project is ready for graduation.
>>>> 
>>>> So, it seems about time to discuss our further intentions. Our options,
>>>> as I see them,  are:
>>>> 
>>>> 1.) Graduate as a new TLP, as ant has already suggested. I would expect
>>>> that the board would approve a corresponding request. (After minor
>>>> discussions, perhaps.)
>>>> 2.) Become a subproject of another TLP. Problem is, that there is no
>>>> obvious choice, that would welcome VXQuery. For example, speaking as a
>>>> member of Apache
>>>> 
>>>> 
>>>> On Tue, Nov 12, 2013 at 7:13 PM, Till Westmann <[email protected]> wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> our release was finally approved by the IPMC:
>>>>> 
>>>>> 
>>>>> http://mail-archives.apache.org/mod_mbox/incubator-general/201311.mbox/browser
>>>>> 
>>>>> Unfortunately, we were not completely prepared for this event, as we are
>>>>> still missing the distribution area to distribute the release artifacts.
>>>>> I've filed a JIRA to create it
>>>>> 
>>>>> https://issues.apache.org/jira/browse/INFRA-6983
>>>>> 
>>>>> but since there are 110 other JIRAs in the state "Waiting for Infra",
>>>>> there has been no activity so far.
>>>>> 
>>>>> So maybe if we could all vote for the issue, it might catch Infra's
>>>>> attention a little earlier :)
>>>>> 
>>>>> Thanks,
>>>>> Till
>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> "That's what prayers are ... it's frightened people trying to make
>>>> friends with the bully!"
>>>> 
>>>> Terry Pratchett. The Last Hero
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> "That's what prayers are ... it's frightened people trying to make friends
>>> with the bully!"
>>> 
>>> Terry Pratchett. The Last Hero
>>> 
>>> 
>> 
>> 
>> -- 
>> "That's what prayers are ... it's frightened people trying to make friends
>> with the bully!"
>> 
>> Terry Pratchett. The Last Hero
> 

Reply via email to