You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "John Sisson (JIRA)" <de...@geronimo.apache.org> on 2005/07/13 04:57:12 UTC
[jira] Created: (GERONIMO-744) Change spec dependencies to formal versions
Change spec dependencies to formal versions
-------------------------------------------
Key: GERONIMO-744
URL: http://issues.apache.org/jira/browse/GERONIMO-744
Project: Geronimo
Type: Task
Components: specs
Versions: 1.0-M4
Reporter: John Sisson
Assigned to: Jeremy Boynes
Currently Geronimo is depending upon release candidate and snapshot versions of the specs JARs.
See mail dev list mail thread for Jeremy's proposal "Release specs as a separate distro from M4":
http://marc.theaimsgroup.com/?t=112084085400004&r=1&w=2
Dain suggested "Before we make the final spec releases, maybe we should all pick one or two spec modules to review for obvious issues. I'll take qname since it only has one class ;)"
Maybe we should create and assign a JIRA subtasks for the review of each spec, so this work can be tracked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-744) Review specs and move them from rc versions to formal versions
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-744?page=all ]
John Sisson updated GERONIMO-744:
---------------------------------
Component: dependencies
Summary: Review specs and move them from rc versions to formal versions (was: Change spec dependencies to formal versions)
Fix Version: 1.0-M5
(was: 1.0-M4)
Description:
Currently Geronimo is depending upon release candidate and snapshot versions of the specs JARs.
See mail dev list mail thread for Jeremy's proposal "Release specs as a separate distro from M4":
http://marc.theaimsgroup.com/?t=112084085400004&r=1&w=2
Dain suggested "Before we make the final spec releases, maybe we should all pick one or two spec modules to review for obvious issues. I'll take qname since it only has one class ;)"
Maybe we should create and assign a JIRA subtasks for the review of each spec, so this work can be tracked.
I have created separate issues for specs that need to be moved from SNAPSHOTS for the M4 release and I will leave this issue to deal with the review of the specs and moving them from release candidate to formal releases. Shall we aim for the formal releases in M5?
was:
Currently Geronimo is depending upon release candidate and snapshot versions of the specs JARs.
See mail dev list mail thread for Jeremy's proposal "Release specs as a separate distro from M4":
http://marc.theaimsgroup.com/?t=112084085400004&r=1&w=2
Dain suggested "Before we make the final spec releases, maybe we should all pick one or two spec modules to review for obvious issues. I'll take qname since it only has one class ;)"
Maybe we should create and assign a JIRA subtasks for the review of each spec, so this work can be tracked.
> Review specs and move them from rc versions to formal versions
> --------------------------------------------------------------
>
> Key: GERONIMO-744
> URL: http://issues.apache.org/jira/browse/GERONIMO-744
> Project: Geronimo
> Type: Task
> Components: specs, dependencies
> Versions: 1.0-M4
> Reporter: John Sisson
> Fix For: 1.0-M5
>
> Currently Geronimo is depending upon release candidate and snapshot versions of the specs JARs.
> See mail dev list mail thread for Jeremy's proposal "Release specs as a separate distro from M4":
> http://marc.theaimsgroup.com/?t=112084085400004&r=1&w=2
> Dain suggested "Before we make the final spec releases, maybe we should all pick one or two spec modules to review for obvious issues. I'll take qname since it only has one class ;)"
> Maybe we should create and assign a JIRA subtasks for the review of each spec, so this work can be tracked.
> I have created separate issues for specs that need to be moved from SNAPSHOTS for the M4 release and I will leave this issue to deal with the review of the specs and moving them from release candidate to formal releases. Shall we aim for the formal releases in M5?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-744) Change spec dependencies to formal versions
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-744?page=all ]
John Sisson updated GERONIMO-744:
---------------------------------
Fix Version: 1.0-M4
> Change spec dependencies to formal versions
> -------------------------------------------
>
> Key: GERONIMO-744
> URL: http://issues.apache.org/jira/browse/GERONIMO-744
> Project: Geronimo
> Type: Task
> Components: specs
> Versions: 1.0-M4
> Reporter: John Sisson
> Assignee: Jeremy Boynes
> Fix For: 1.0-M4
>
> Currently Geronimo is depending upon release candidate and snapshot versions of the specs JARs.
> See mail dev list mail thread for Jeremy's proposal "Release specs as a separate distro from M4":
> http://marc.theaimsgroup.com/?t=112084085400004&r=1&w=2
> Dain suggested "Before we make the final spec releases, maybe we should all pick one or two spec modules to review for obvious issues. I'll take qname since it only has one class ;)"
> Maybe we should create and assign a JIRA subtasks for the review of each spec, so this work can be tracked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-744) Review specs and move them from rc versions to formal versions
Posted by "Alan Cabrera (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-744?page=all ]
Alan Cabrera closed GERONIMO-744:
---------------------------------
Resolution: Fixed
Done
> Review specs and move them from rc versions to formal versions
> --------------------------------------------------------------
>
> Key: GERONIMO-744
> URL: http://issues.apache.org/jira/browse/GERONIMO-744
> Project: Geronimo
> Type: Task
> Components: specs, dependencies
> Versions: 1.0-M4
> Reporter: John Sisson
> Assignee: Alan Cabrera
> Fix For: 1.0
>
> Currently Geronimo is depending upon release candidate and snapshot versions of the specs JARs.
> See mail dev list mail thread for Jeremy's proposal "Release specs as a separate distro from M4":
> http://marc.theaimsgroup.com/?t=112084085400004&r=1&w=2
> Dain suggested "Before we make the final spec releases, maybe we should all pick one or two spec modules to review for obvious issues. I'll take qname since it only has one class ;)"
> Maybe we should create and assign a JIRA subtasks for the review of each spec, so this work can be tracked.
> I have created separate issues for specs that need to be moved from SNAPSHOTS for the M4 release and I will leave this issue to deal with the review of the specs and moving them from release candidate to formal releases. Shall we aim for the formal releases in M5?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-744) Review specs and move them from rc versions to formal versions
Posted by "Alan Cabrera (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-744?page=all ]
Alan Cabrera reassigned GERONIMO-744:
-------------------------------------
Assign To: Alan Cabrera
> Review specs and move them from rc versions to formal versions
> --------------------------------------------------------------
>
> Key: GERONIMO-744
> URL: http://issues.apache.org/jira/browse/GERONIMO-744
> Project: Geronimo
> Type: Task
> Components: specs, dependencies
> Versions: 1.0-M4
> Reporter: John Sisson
> Assignee: Alan Cabrera
> Fix For: 1.0
>
> Currently Geronimo is depending upon release candidate and snapshot versions of the specs JARs.
> See mail dev list mail thread for Jeremy's proposal "Release specs as a separate distro from M4":
> http://marc.theaimsgroup.com/?t=112084085400004&r=1&w=2
> Dain suggested "Before we make the final spec releases, maybe we should all pick one or two spec modules to review for obvious issues. I'll take qname since it only has one class ;)"
> Maybe we should create and assign a JIRA subtasks for the review of each spec, so this work can be tracked.
> I have created separate issues for specs that need to be moved from SNAPSHOTS for the M4 release and I will leave this issue to deal with the review of the specs and moving them from release candidate to formal releases. Shall we aim for the formal releases in M5?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-744) Change spec dependencies to formal versions
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-744?page=all ]
John Sisson reassigned GERONIMO-744:
------------------------------------
Assign To: (was: Jeremy Boynes)
> Change spec dependencies to formal versions
> -------------------------------------------
>
> Key: GERONIMO-744
> URL: http://issues.apache.org/jira/browse/GERONIMO-744
> Project: Geronimo
> Type: Task
> Components: specs
> Versions: 1.0-M4
> Reporter: John Sisson
> Fix For: 1.0-M4
>
> Currently Geronimo is depending upon release candidate and snapshot versions of the specs JARs.
> See mail dev list mail thread for Jeremy's proposal "Release specs as a separate distro from M4":
> http://marc.theaimsgroup.com/?t=112084085400004&r=1&w=2
> Dain suggested "Before we make the final spec releases, maybe we should all pick one or two spec modules to review for obvious issues. I'll take qname since it only has one class ;)"
> Maybe we should create and assign a JIRA subtasks for the review of each spec, so this work can be tracked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-744) Review specs and move them from rc versions to formal versions
Posted by "David Blevins (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-744?page=all ]
David Blevins updated GERONIMO-744:
-----------------------------------
Fix Version: 1.0
(was: 1.0-M5)
> Review specs and move them from rc versions to formal versions
> --------------------------------------------------------------
>
> Key: GERONIMO-744
> URL: http://issues.apache.org/jira/browse/GERONIMO-744
> Project: Geronimo
> Type: Task
> Components: specs, dependencies
> Versions: 1.0-M4
> Reporter: John Sisson
> Fix For: 1.0
>
> Currently Geronimo is depending upon release candidate and snapshot versions of the specs JARs.
> See mail dev list mail thread for Jeremy's proposal "Release specs as a separate distro from M4":
> http://marc.theaimsgroup.com/?t=112084085400004&r=1&w=2
> Dain suggested "Before we make the final spec releases, maybe we should all pick one or two spec modules to review for obvious issues. I'll take qname since it only has one class ;)"
> Maybe we should create and assign a JIRA subtasks for the review of each spec, so this work can be tracked.
> I have created separate issues for specs that need to be moved from SNAPSHOTS for the M4 release and I will leave this issue to deal with the review of the specs and moving them from release candidate to formal releases. Shall we aim for the formal releases in M5?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira