On Dec 7, 2006, at 2:47 PM, David Blevins wrote:

It looks like the time for release is at hand as Geronimo is on the cusp of 1.2 beta.

From an Incubator status we cleared up what was posted by Kevan and me. Anyone want to double check that we are good to go in that area?

From a technical perspective when are we good to ship? Could we cut today, tomorrow, next week? Any outstanding technical items we'd need to get done for Geronimo's 1.2 beta?

Hi David,
I started looking at branches/v2_2/openejb2 last night.

There were a few files missing license headers. All of the NOTICE files did not meet current Apache requirements, and there was no DISCLAIMER file. I can commit these changes soon to branches/2_2 and trunk/openejb2, soon.

There's a bit of work needed to identify any 3rd party license/notice information that needs to be included in the OpenEJB license/notice files.

Release notes/readme files need to be created. These should mention that openejb is in incubator.

I have not run RAT against a binary distribution. So, there may be some additional issues...

To make sure we're all thinking alike, here are the releases that I see coming up in the very-near future:

2.2-m1 (corresponds to Geronimo 1.2 beta)
2.3-m1 (corresponds to Geronimo 2.0 M1)

I'm not aware of any technical problems which would prevent a release of the above.

As soon as G 1.2 and OEJB 2.2 are passing TCK, there would be a 2.2 release. Agreed?

2.3 is kind of a dead-end version. I don't think we really see it being a full release. Is there someway that 2.2-m1 could be shared between the two Geronimo beta/milestone releases?

Later on, I assume we'll be generating a 3.0-m1. But that's a future discussion...

--kevan

Reply via email to