Steps to graduate from incubator (was: plans for 1.x and 2.x)

[Dave Johnson <da...@rollerweblogger.org>]

On Jul 8, 2005, at 10:24 AM, Anil Gangolli wrote:
> I'd like to understand the plans for 1.x and 2.x a bit better than I 
> do.
>
> (1) Are we expecting to put out any further 1.x releases (other than 
> bug fixes)?   I have one bug fix 
> (http://opensource.atlassian.com/projects/roller/browse/ROL-754) that 
> should be in a 1.3 release.
> This is due to our numbering conventions and the expectation that 
> MySQL 5.0 may come out before Roller 2.0.

I think Allen covered this well.


> (2) Do we have a list of tasks we need to do to the codebase 
> prerequisite to graduating from the incubator, and are we planning to 
> do that work be done on trunk or the 2.0 branch?

I believe that the next step is to create a STATUS file to track the 
status of our incubation and to set out all of the exit criteria -- 
that's our list of tasks.

See: http://incubator.apache.org/incubation/Incubation_Policy.html

Here's what I think we might have on that list of tasks (not meant to 
imply ordering of tasks). Regarding the timeline and branching: I might 
want to delay some of these until after 2.0 is merged back in.

* Deal with licensing issues
    - Roller requires Hibernate, which is LGPL
    - Roller also has a JSPWiki plugin, we it requires the JSPWiki jars 
(LGPL)
    - Can we keep the LGPL jars in Apache Subversion?
    - If not, what are the alternatives for source and binary releases?

* Setup project website
    - A roller/jspwiki driven site like rollerweblogger.org?
    - Or just a static site generated by build process?

* Make a release through website
    - To learn the Apache release process

* Apply Apache license
    - In every source file
    - Other places?

* What else?

Sam or Henri: is there a standard "graduation checklist" somewhere? I 
couldn't find one on the Apache site.


- Dave



>
> --a.
>
>
>
>
>

Re: Steps to graduate from incubator

[Allen Gilliland <Al...@Sun.COM>]

I actually took Anil's comment to mean what features/fixes do we want 
present in the code before we feel that we are finished with the 
incubator.  That's what I meant when I said I had a list of remaining items.

-- Allen


Dave Johnson wrote:

>
> On Jul 8, 2005, at 10:24 AM, Anil Gangolli wrote:
>
>> I'd like to understand the plans for 1.x and 2.x a bit better than I do.
>>
>> (1) Are we expecting to put out any further 1.x releases (other than 
>> bug fixes)?   I have one bug fix 
>> (http://opensource.atlassian.com/projects/roller/browse/ROL-754) that 
>> should be in a 1.3 release.
>> This is due to our numbering conventions and the expectation that 
>> MySQL 5.0 may come out before Roller 2.0.
>
>
> I think Allen covered this well.
>
>
>> (2) Do we have a list of tasks we need to do to the codebase 
>> prerequisite to graduating from the incubator, and are we planning to 
>> do that work be done on trunk or the 2.0 branch?
>
>
> I believe that the next step is to create a STATUS file to track the 
> status of our incubation and to set out all of the exit criteria -- 
> that's our list of tasks.
>
> See: http://incubator.apache.org/incubation/Incubation_Policy.html
>
> Here's what I think we might have on that list of tasks (not meant to 
> imply ordering of tasks). Regarding the timeline and branching: I 
> might want to delay some of these until after 2.0 is merged back in.
>
> * Deal with licensing issues
>    - Roller requires Hibernate, which is LGPL
>    - Roller also has a JSPWiki plugin, we it requires the JSPWiki jars 
> (LGPL)
>    - Can we keep the LGPL jars in Apache Subversion?
>    - If not, what are the alternatives for source and binary releases?
>
> * Setup project website
>    - A roller/jspwiki driven site like rollerweblogger.org?
>    - Or just a static site generated by build process?
>
> * Make a release through website
>    - To learn the Apache release process
>
> * Apply Apache license
>    - In every source file
>    - Other places?
>
> * What else?
>
> Sam or Henri: is there a standard "graduation checklist" somewhere? I 
> couldn't find one on the Apache site.
>
>
> - Dave
>
>
>
>>
>> --a.
>>
>>
>>
>>
>>
>

RE: Steps to graduate from incubator (was: plans for 1.x and 2.x)

["Noel J. Bergman" <no...@devtech.com>]

Dave Johnson wrote:

> * Deal with licensing issues
>    - Roller requires Hibernate, which is LGPL
>    - Roller also has a JSPWiki plugin [(LGPL)]
>    - Can we keep the LGPL jars in Apache Subversion?

At this time, LGPL code is an issue unless you access it very indirectly,
e.g., an LGPL JDBC driver, where your code is entirely naive about which
driver is in use.  We are hopeful that these issues will be resolved with
the FSF, but until then, LGPL would be a blocker.  Cliff Schmidt is managing
licensing issues for the ASF at this time, and can go into detail.

> * Setup project website
>    - A roller/jspwiki driven site like rollerweblogger.org?
>    - Or just a static site generated by build process?

A static site is no problem, and should go under
http://incubator.apache.org/roller, which means placing it under
/www/incubator.apache.org/roller.  A roller-based site is a bit more of an
issue, would go under roller.zones.apache.org, and perhaps should wait for
graduation.

> * Make a release through website
>     - To learn the Apache release process

Your mentors can definitely help out here.

> * Apply Apache license

This should be done immediately.

	--- Noel