You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by kelvin goodson <ke...@gmail.com> on 2007/03/02 11:59:19 UTC
SDO Java M3 content
I did some work yesterday to get the SDO Java JIRAs reflecting the true
history of releases to date, so now all the JIRAs that I could edit (not
closed) that contributed to SDO Java M2 have a fix version of JAVA-SDO-M2 (I
then closed all these), and anything that has been fixed since has a fix
version of JAVA-SDO-M3. So with a view to getting an M3 release together we
should discuss the content of that release and set the fix version of any
unresolved JIRAs that we really want to have in that release to JAVA-SDO-M3.
Also, unless anyone has a burning desire to do so, I'm happy to take on
the release management role for this milestone.
Regards, Kelvin.
Re: SDO Java M3 content
Posted by kelvin goodson <ke...@gmail.com>.
I opened JIRA Task http://issues.apache.org/jira/browse/TUSCANY-1171 to
cover work done for the SDO Java M3 release, and have just attached an
initial rat report. If anyone feels the urge to check this through before I
get to it that would be great ;-)
Kelvin.
On 13/03/07, kelvin goodson <ke...@gmail.com> wrote:
>
> Just trying to pick this up again having been unwell for most of last
> week. I've just made a few no-brainer updates to the JIRAs with respect to
> correct settings for version labels, but I'd like to pin down the content
> for the next release.
>
> In my tidying up of the website content I posted about earlier, I put up a
> wiki page showing all JIRAs that have been fixed between M2 and now ...
> http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+M3
> So clearly they would all be part of the content.
>
> I hope these permalinks I copied from the JIRA interface display the same
> for you as they do for me
>
> Here's what's currently marked by the JIRA system as deferred (i.e.
> unresolved and not marked as SDO-M3)
> http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310210&component=12310660&component=12310973&component=12310802&fixfor=12311030&fixfor=12312345&fixfor=12312232&fixfor=12312304&fixfor=12312265&fixfor=12311062&fixfor=12311958&fixfor=12312266&fixfor=12312094&fixfor=12312261&fixfor=12312262&fixfor=12312038&fixfor=12312349&fixfor=12312352&fixfor=12312353&fixfor=12312354&fixfor=12312355&fixfor=12312356&fixfor=12312357&fixfor=12312358&fixfor=12311926&resolution=-1&sorter/field=issuekey&sorter/order=DESC&sorter/field=customfield_12310041&sorter/order=ASC
>
>
> And here's what's unresolved and marked for inclusion in M3 ...
>
> http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310210&fixfor=12312317&resolution=-1&sorter/field=issuekey&sorter/order=DESC
>
> Please comment on this state and volunteer to pick up any of the issues if
> you possible can.
>
> Regards, Kelvin.
>
>
>
> On 02/03/07, kelvin goodson <ke...@gmail.com> wrote:
> >
> > I did some work yesterday to get the SDO Java JIRAs reflecting the true
> > history of releases to date, so now all the JIRAs that I could edit (not
> > closed) that contributed to SDO Java M2 have a fix version of JAVA-SDO-M2 (I
> > then closed all these), and anything that has been fixed since has a fix
> > version of JAVA-SDO-M3. So with a view to getting an M3 release together we
> > should discuss the content of that release and set the fix version of any
> > unresolved JIRAs that we really want to have in that release to JAVA-SDO-M3.
> >
> >
> > Also, unless anyone has a burning desire to do so, I'm happy to take
> > on the release management role for this milestone.
> >
> > Regards, Kelvin.
> >
>
>
Re: SDO Java M3 content
Posted by kelvin goodson <ke...@gmail.com>.
Just trying to pick this up again having been unwell for most of last week.
I've just made a few no-brainer updates to the JIRAs with respect to correct
settings for version labels, but I'd like to pin down the content for the
next release.
In my tidying up of the website content I posted about earlier, I put up a
wiki page showing all JIRAs that have been fixed between M2 and now ...
http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+M3
So clearly they would all be part of the content.
I hope these permalinks I copied from the JIRA interface display the same
for you as they do for me
Here's what's currently marked by the JIRA system as deferred (i.e.
unresolved and not marked as SDO-M3)
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310210&component=12310660&component=12310973&component=12310802&fixfor=12311030&fixfor=12312345&fixfor=12312232&fixfor=12312304&fixfor=12312265&fixfor=12311062&fixfor=12311958&fixfor=12312266&fixfor=12312094&fixfor=12312261&fixfor=12312262&fixfor=12312038&fixfor=12312349&fixfor=12312352&fixfor=12312353&fixfor=12312354&fixfor=12312355&fixfor=12312356&fixfor=12312357&fixfor=12312358&fixfor=12311926&resolution=-1&sorter/field=issuekey&sorter/order=DESC&sorter/field=customfield_12310041&sorter/order=ASC
And here's what's unresolved and marked for inclusion in M3 ...
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310210&fixfor=12312317&resolution=-1&sorter/field=issuekey&sorter/order=DESC
Please comment on this state and volunteer to pick up any of the issues if
you possible can.
Regards, Kelvin.
On 02/03/07, kelvin goodson <ke...@gmail.com> wrote:
>
> I did some work yesterday to get the SDO Java JIRAs reflecting the true
> history of releases to date, so now all the JIRAs that I could edit (not
> closed) that contributed to SDO Java M2 have a fix version of JAVA-SDO-M2 (I
> then closed all these), and anything that has been fixed since has a fix
> version of JAVA-SDO-M3. So with a view to getting an M3 release together we
> should discuss the content of that release and set the fix version of any
> unresolved JIRAs that we really want to have in that release to JAVA-SDO-M3.
>
>
> Also, unless anyone has a burning desire to do so, I'm happy to take on
> the release management role for this milestone.
>
> Regards, Kelvin.
>