You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Rick McGuire <ri...@gmail.com> on 2010/05/26 17:32:21 UTC
The 3.0-M1 release notes need some attention.
I've done a quick pass through the 3.0-M1 release notes, but I need a
little help to get this updated for creating a release candidate. This
is the first time I've done of these, so I have a few questions on how
this gets pulled together.
1) The version in here is listed as @VERSION@. Is that something the
release plugin updates automatically when the release is prepared or
does this require a manual search-and-replace operation? I notice that
the 2.2 version of this still says @VERSION@. Was that just an
oversite, or is that convention.
2) Are there tools (or standard Jira searches) available for generating
the various lists of issues included in the release notes?
3) What enhancements should we be listing here? I took a quick first
pass, but please make additions/corrections to the list I've put
together. I know there are some things missing like the Global JNDI
enhancements and the Datasource resource bindings and I suspect the
Aries feature list is incomplete. Please help me fill this out.
4) What should we list for supported features? The wording currently
there is definitely wrong. How should we phrase this?
5) There are obviously lots of limitations here. What should we be
listing?
Rick
Re: The 3.0-M1 release notes need some attention.
Posted by David Jencks <da...@yahoo.com>.
On May 26, 2010, at 8:32 AM, Rick McGuire wrote:
> I've done a quick pass through the 3.0-M1 release notes, but I need a little help to get this updated for creating a release candidate. This is the first time I've done of these, so I have a few questions on how this gets pulled together.
>
> 1) The version in here is listed as @VERSION@. Is that something the release plugin updates automatically when the release is prepared or does this require a manual search-and-replace operation? I notice that the 2.2 version of this still says @VERSION@. Was that just an oversite, or is that convention.
That's a mistake I don't really know how to fix in a reasonable manner. I guess you have to edit it by hand before the release and restore it by hand afterwards I thought there was some filtering operation that filled it in but I was wrong.
>
> 2) Are there tools (or standard Jira searches) available for generating the various lists of issues included in the release notes?
yes.... you can look at the jiras for a release and theres a link or button to get a text output. However, I think 99% of the 3.0 jiras aren't closed even if the feature is fairly complete due to not really knowing the tck status of the area. I'd be very tempted to just have a short list of features we've partly implemented and skip the jira list.
david jencks
>
> 3) What enhancements should we be listing here? I took a quick first pass, but please make additions/corrections to the list I've put together. I know there are some things missing like the Global JNDI enhancements and the Datasource resource bindings and I suspect the Aries feature list is incomplete. Please help me fill this out.
>
> 4) What should we list for supported features? The wording currently there is definitely wrong. How should we phrase this?
>
> 5) There are obviously lots of limitations here. What should we be listing?
>
> Rick
Re: The 3.0-M1 release notes need some attention.
Posted by Donald Woods <dw...@apache.org>.
On 5/26/10 11:32 AM, Rick McGuire wrote:
> I've done a quick pass through the 3.0-M1 release notes, but I need a
> little help to get this updated for creating a release candidate. This
> is the first time I've done of these, so I have a few questions on how
> this gets pulled together.
>
> 1) The version in here is listed as @VERSION@. Is that something the
> release plugin updates automatically when the release is prepared or
> does this require a manual search-and-replace operation? I notice that
> the 2.2 version of this still says @VERSION@. Was that just an
> oversite, or is that convention.
>
The Eclipse plugin build does something like this, but with
${pom.version} instead -
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-505
http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v20.core/pom.xml?p2=/geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v20.core/pom.xml&p1=/geronimo/devtools/eclipse-plugin/trunk/plugins/org.apache.geronimo.st.v20.core/pom.xml&r1=689987&r2=689986&view=diff&pathrev=689987
> 2) Are there tools (or standard Jira searches) available for generating
> the various lists of issues included in the release notes?
>
https://issues.apache.org/jira/browse/GERONIMO
Release Notes
version=3.0
style=text
cut-n-paste section is at the bottom -
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12314206&styleName=Text&projectId=10220&Create=Create
For OpenJPA, we created releases for each milestone and beta, so we
could correctly group the jiras per release. If you wanted to do that
for Geronimo, you'd have to create a 3.0-M1 and then bulk edit all
issues that have a Fix Version of 3.0 (and resolved or closed) and
change it to 3.0-M1.
> 3) What enhancements should we be listing here? I took a quick first
> pass, but please make additions/corrections to the list I've put
> together. I know there are some things missing like the Global JNDI
> enhancements and the Datasource resource bindings and I suspect the
> Aries feature list is incomplete. Please help me fill this out.
>
Well, I wouldn't say the following until we pass the TCKs -
All programming elements of the Java EE 6.0 Specification are available.
I know the BVAL plugin that David J. was working on is not in the M1
branch. Also, not sure if we've updated our JSF 2.2 support to include
the BVAL support....
> 4) What should we list for supported features? The wording currently
> there is definitely wrong. How should we phrase this?
>
I would only list what we want users to focus on and try -
web apps - servlet 3.0, jsf 2.2, jsp
wab - rfc66 apps
eba - osgi/aries based apps (blueprint, jpa, transaction, jndi, ...)
Secondary focus - traditional Java EE apps -
jpa 2.0?
how much of EJB 3.1?
activemq 5.3.2
connector 1.6?
> 5) There are obviously lots of limitations here. What should we be
> listing?
Just a big disclaimer that this is a milestone release and should only
be used for learning about the upcoming Geronimo 3.0 release with Java
EE 6 and OSGi/Aries support and not for any type of production usage...
>
> Rick
>