11:32 p.m.
Referencing this wiki:
http://community.jboss.org/wiki/JBossProjectVersioning
A Candidate Release qualifier is for releases that we anticipate can be the GA release.
The 6.0.0.CR1 release is anticipated to be *the* GA release with a few additional bug
fixes.
There are currently 32 components in jbossas/trunk/component-matrix/pom.xml that are
versioned with
the Alpha qualifier, 18 Beta.
From the same wiki:
The use of Alpha is for early releases that
are not API complete.
The use of Beta qualifier is for releases where the release is API complete, but its not
completely tested,
or there may even be questions about the API itself that may change, even though the
implementation is complete.
Is this convention being followed? If so, jbossas/trunk has 50 components that are not
API complete or may change?
Trying to get a clear roadmap of the upgrades expected. There are only 6 identified in
https://jira.jboss.org/browse/JBAS-8253.
Appreciate if the project leads can add a subtask if an upgrade is planned for 6.0.0.CR1.
2:01 a.m.
Shelly McGowan wrote:
Referencing this wiki:
http://community.jboss.org/wiki/JBossProjectVersioning
A Candidate Release qualifier is for releases that we anticipate can be the GA release.
The 6.0.0.CR1 release is anticipated to be *the* GA release with a few additional bug
fixes.
There are currently 32 components in jbossas/trunk/component-matrix/pom.xml that are
versioned with
the Alpha qualifier, 18 Beta.
>From the same wiki:
The use of Alpha is for early releases that are not API complete.
The use of Beta qualifier is for releases where the release is API complete, but its not
completely tested,
or there may even be questions about the API itself that may change, even though the
implementation is complete.
Is this convention being followed? If so, jbossas/trunk has 50 components that are not
API complete or may change?
We have tried to follow this in the past, but it is obviously not easy due to the number
of
people/subprojects involved and the strictness or not of naming their releases according
to
the standard. Nevertheless, we need to try get as many components to CR state or better.
However it's in the judgment of the individual leads in coordination with the AS lead
to
decide if a particular release is good enough for AS. In many case it'll be a matter
of
promoting an Alpha/Beta to CR, or even Final.
Trying to get a clear roadmap of the upgrades expected. There are only 6 identified in
https://jira.jboss.org/browse/JBAS-8253.
Appreciate if the project leads can add a subtask if an upgrade is planned for
6.0.0.CR1.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
10:58 a.m.
What's the deadline here?
On Sep 15, 2010, at 10:32 PM, Shelly McGowan wrote:
Referencing this wiki:
http://community.jboss.org/wiki/JBossProjectVersioning
A Candidate Release qualifier is for releases that we anticipate can be the GA release.
The 6.0.0.CR1 release is anticipated to be *the* GA release with a few additional bug
fixes.
There are currently 32 components in jbossas/trunk/component-matrix/pom.xml that are
versioned with
the Alpha qualifier, 18 Beta.
> From the same wiki:
The use of Alpha is for early releases that are not API complete.
The use of Beta qualifier is for releases where the release is API complete, but its not
completely tested,
or there may even be questions about the API itself that may change, even though the
implementation is complete.
Is this convention being followed? If so, jbossas/trunk has 50 components that are not
API complete or may change?
Trying to get a clear roadmap of the upgrades expected. There are only 6 identified in
https://jira.jboss.org/browse/JBAS-8253.
Appreciate if the project leads can add a subtask if an upgrade is planned for
6.0.0.CR1.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
- DML
11:42 a.m.
https://community.jboss.org/wiki/AS600CR1StatusExecutiveSummary
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "David M. Lloyd" <dlloyd(a)redhat.com>
To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Sent: Thursday, September 16, 2010 10:58:38 AM GMT -05:00 US/Canada Eastern
Subject: Re: [jboss-dev] Project Versions in jbossas/trunk
What's the deadline here?
On Sep 15, 2010, at 10:32 PM, Shelly McGowan wrote:
Referencing this wiki:
http://community.jboss.org/wiki/JBossProjectVersioning
A Candidate Release qualifier is for releases that we anticipate can be the GA release.
The 6.0.0.CR1 release is anticipated to be *the* GA release with a few additional bug
fixes.
There are currently 32 components in jbossas/trunk/component-matrix/pom.xml that are
versioned with
the Alpha qualifier, 18 Beta.
> From the same wiki:
The use of Alpha is for early releases that are not API complete.
The use of Beta qualifier is for releases where the release is API complete, but its not
completely tested,
or there may even be questions about the API itself that may change, even though the
implementation is complete.
Is this convention being followed? If so, jbossas/trunk has 50 components that are not
API complete or may change?
Trying to get a clear roadmap of the upgrades expected. There are only 6 identified in
https://jira.jboss.org/browse/JBAS-8253.
Appreciate if the project leads can add a subtask if an upgrade is planned for
6.0.0.CR1.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
- DML
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
10:25 a.m.
Everyone should be transitioning to this model, but it's not fully
adopted yet. Note that the community releases can still include
experimental features, or new pilot frameworks, etc. So, it's perfectly
reasonable to ship some beta/alphas of things. However, we really should
look into getting CRs where possible.
On 9/15/10 10:32 PM, Shelly McGowan wrote:
Referencing this wiki:
http://community.jboss.org/wiki/JBossProjectVersioning
A Candidate Release qualifier is for releases that we anticipate can be the GA release.
The 6.0.0.CR1 release is anticipated to be *the* GA release with a few additional bug
fixes.
There are currently 32 components in jbossas/trunk/component-matrix/pom.xml that are
versioned with
the Alpha qualifier, 18 Beta.
> From the same wiki:
The use of Alpha is for early releases that are not API complete.
The use of Beta qualifier is for releases where the release is API complete, but its not
completely tested,
or there may even be questions about the API itself that may change, even though the
implementation is complete.
Is this convention being followed? If so, jbossas/trunk has 50 components that are not
API complete or may change?
Trying to get a clear roadmap of the upgrades expected. There are only 6 identified in
https://jira.jboss.org/browse/JBAS-8253.
Appreciate if the project leads can add a subtask if an upgrade is planned for
6.0.0.CR1.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Jason T. Greene
JBoss, a division of Red Hat
4963
days inactive
4968
days old
jboss-development@lists.jboss.org
4 comments
4 participants
participants (4)
-
David M. Lloyd -
Dimitris Andreadis -
Jason T. Greene -
Shelly McGowan