On 9 June 2012 05:54, David Crossley <[email protected]> wrote:
> sebb wrote:
>> > Author: crossley
>> > Date: Fri Jun  8 23:55:11 2012
>> > New Revision: 1348282
>> >
>> > URL: http://svn.apache.org/viewvc?rev=1348282&view=rev
>> > Log:
>> > flume started to graduate.
>> > oozie updated status page.
>> > oozie news about 2 new committers.
>> >
>> > Modified:
>> >    incubator/public/trunk/clutch-graduating.txt
>> >    incubator/public/trunk/content/clutchr1.ent
>> >    incubator/public/trunk/content/clutchr2.ent
>> >    incubator/public/trunk/content/clutcht.ent
>> >
>> > Modified: incubator/public/trunk/clutch-graduating.txt
>> > URL: 
>> > http://svn.apache.org/viewvc/incubator/public/trunk/clutch-graduating.txt?rev=1348282&r1=1348281&r2=1348282&view=diff
>> > ==============================================================================
>> > --- incubator/public/trunk/clutch-graduating.txt (original)
>> > +++ incubator/public/trunk/clutch-graduating.txt Fri Jun  8 23:55:11 2012
>> > @@ -6,3 +6,4 @@
>> >  # Manually maintained.
>> >  # One name per line, matches the ReportingSchedule name, lower-case, no 
>> > spaces.
>> >  #
>> > +flume
>>
>> Rather than a separate file, how about introducing a new tag or
>> attribute to podling.xml?
>> [A new tag might be easier to maintain as it can go on its own line,
>> and the current attribute list is quite long.]
>>
>> It would also be possible to introduce status="graduating", but the
>> status is used in lots of places so this would be a lot more work.
>
> Yes please. The separate optional element seems the way.
> It is a temporary thing while they are finalising their graduation
> wheras the "graduated" status and enddate are for another purpose.

Done.

> -David
>
> ---------------------------------------------------------------------
> 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]

Reply via email to