One of the activities to coordinate when finalizing the release is updating the 1.2 plugin repository catalog at: http://geronimo.apache.org/plugins/geronimo-1.2/geronimo-plugins.xml to point at a repo where the 1.2 artifacts are published instead of the snapshot repo it currently points at. For testing purposes it would be ideal to build Geronimo as version "1.2" (not "1.2rc1" or "1.2.timestamp" or something like that) and publish the 1.2 artifacts to a maven2 repo during the release candidate cycle. That would allow us to test the plugin system in pretty much the exact state it will be when 1.2 is released. Is that feasible? If not then we may need to work out an alternate approach where the repository catalog gets updated after the release goes out and the artifacts get published. That makes me a little nervous though since it will be too late to make changes to the server if something doesn't work right.
Best wishes, Paul On 10/30/06, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
In a typical Geronimo release we tend to spend a significant amount of time in what I'll call the "Fit and Finish" phase. This involves tying up loose ends such as log levels, tools L&F, startup times, licenses and so on. Basically, the phase includes fixing all the nits that cause people to vote -1 for a release (BTW no vetos in a release vote). Please, take a moment and respond to this email with any items you feel should be cleaned up before we release the software. That way we can hopefully get these items out in the open and addressed while we are finishing the TCK testing. Please note that just because an item is mentioned doesn't mean it must be completed before a release. The only thing required for a release it to successfully pass a vote of the PMC, so if the item is critical to you, spend a few minutes fixing it. With any luck we should be able to have the server ready to ship about the same time we finish the TCK testing. -dain
