Tracking Geronimo 3.0 status.

[Rick McGuire <ri...@gmail.com>]

I've heard a number of complaints from people working on Geronimo 3.0 
about the difficulty in keeping track of who is working on what items 
for the release.  David Blevins made an excellent suggestion a couple 
weeks ago that we use something like the system that OpenEJB is using to 
track everything via Jiras and use swizzle scripts to generate a wiki 
page to generate an at-a-glance summary of work status.  I've spent a 
bit of time over the last couple of weeks creating top-level task Jiras 
for the Geronimo 3.0 work and organizing the currently open 3.0 Jiras as 
subtasks under these items.  There is a major item for each of the Java 
EE 6 components that are required for a Java EE 6 compliant server, as 
well as a few major tasks for the OSGi work.  The summary page can be 
found here:

http://cwiki.apache.org/GMOxDEV/java-ee-6-roadmap.html

It will be updated once a week or so...more frequently if there appears 
to be a lot of Jira activity.

Additional information on 3.0 can be found at this wiki page, which 
organizes the work using the style used for the Geronimo 2.0 server 
release.  This is wiki page also contains more detailed information 
about the state of the components Geronimo is dependent on and the work 
needed to integrate these components into 3.0. \

http://cwiki.apache.org/confluence/display/GMOxDEV/Road+map+for+Java+EE6+Web+Profile

There are steps that individual contributors can take to ensure this

1)  Try to create new Jiras as subtasks of one of the major tasks so 
that new work gets categorized appropriately.
2)  The major tasks were my best-guess first attempt at organizing 
this.  If you feel additional major categories are required, go ahead 
and create them.  New major tasks need to be added to the script for the 
summary page.  I'll volunteer to maintain that, so nudge me when new 
tasks are created in case I happen to miss it.
3)  I've tried to create links between the Geronimo tasks and Jiras in 
other projects where the dependencies are known.  It is a good idea to 
create new links if you open Jiras in other projects to help fix 
Geronimo problems.
4)  If you start working on a Jira item, please assign to yourself so 
that others know the item is being worked on.

I hope this proves useful.  I've already spotted some missing work areas 
by using this page.


Rick

Re: Tracking Geronimo 3.0 status.

[Shawn Jiang <ge...@gmail.com>]

On Fri, Feb 12, 2010 at 2:48 AM, Rick McGuire <ri...@gmail.com> wrote:

> I've heard a number of complaints from people working on Geronimo 3.0 about
> the difficulty in keeping track of who is working on what items for the
> release.  David Blevins made an excellent suggestion a couple weeks ago that
> we use something like the system that OpenEJB is using to track everything
> via Jiras and use swizzle scripts to generate a wiki page to generate an
> at-a-glance summary of work status.  I've spent a bit of time over the last
> couple of weeks creating top-level task Jiras for the Geronimo 3.0 work and
> organizing the currently open 3.0 Jiras as subtasks under these items.
>  There is a major item for each of the Java EE 6 components that are
> required for a Java EE 6 compliant server, as well as a few major tasks for
> the OSGi work.  The summary page can be found here:
>
> http://cwiki.apache.org/GMOxDEV/java-ee-6-roadmap.html
>
> It will be updated once a week or so...more frequently if there appears to
> be a lot of Jira activity.
>
> Additional information on 3.0 can be found at this wiki page, which
> organizes the work using the style used for the Geronimo 2.0 server release.
>  This is wiki page also contains more detailed information about the state
> of the components Geronimo is dependent on and the work needed to integrate
> these components into 3.0. \
>
>
> http://cwiki.apache.org/confluence/display/GMOxDEV/Road+map+for+Java+EE6+Web+Profile

#set( $parents = [ "5061", "5062", "5063", "5064", "5065", "5066", "5067",
"5068", "5069", "5070", "5071", "5072", "5073", "5074", "5075", "5076",
"5077", "5078", "5079", "5080", "5081", "5082", "5083", "5084", "5085",
"5090", "5110", "5086", "5087", "*5088*", "*5089*"] )


Seems GERONIMO-*5088 *major task appears twice in the page while GERONIMO-*5089
*does not get pulled into this page.



>
>
> There are steps that individual contributors can take to ensure this
>
> 1)  Try to create new Jiras as subtasks of one of the major tasks so that
> new work gets categorized appropriately.
> 2)  The major tasks were my best-guess first attempt at organizing this.
>  If you feel additional major categories are required, go ahead and create
> them.  New major tasks need to be added to the script for the summary page.
>  I'll volunteer to maintain that, so nudge me when new tasks are created in
> case I happen to miss it.
> 3)  I've tried to create links between the Geronimo tasks and Jiras in
> other projects where the dependencies are known.  It is a good idea to
> create new links if you open Jiras in other projects to help fix Geronimo
> problems.
> 4)  If you start working on a Jira item, please assign to yourself so that
> others know the item is being worked on.
>
> I hope this proves useful.  I've already spotted some missing work areas by
> using this page.
>
>
> Rick
>
>


-- 
Shawn

Re: Tracking Geronimo 3.0 status.

[David Blevins <da...@visi.com>]

On Feb 11, 2010, at 10:48 AM, Rick McGuire wrote:

> David Blevins made an excellent suggestion a couple weeks ago that  
> we use something like the system that OpenEJB is using to track  
> everything via Jiras and use swizzle scripts to generate a wiki page  
> to generate an at-a-glance summary of work status.  I've spent a bit  
> of time over the last couple of weeks creating top-level task Jiras  
> for the Geronimo 3.0 work and organizing the currently open 3.0  
> Jiras as subtasks under these items

> http://cwiki.apache.org/GMOxDEV/java-ee-6-roadmap.html
>
> It will be updated once a week or so...more frequently if there  
> appears to be a lot of Jira activity.

I finally got sick of hitting the export button in Confluence and  
spent some time this afternoon creating a little perl script to log in  
and do the export.  I've got it setup to export the OPENEJB,  
OPENEJBx30, GMOxDEV and GMOxSITE spaces on a nightly basis.

So Rick, the pellets come automatically now and we don't have to push  
the button anymore to get them.

-David