The Beta release is just a glorified snapshot, because AS doesn't have
any facilities for continuous integration runs on the latest stable
release of sub-components. So I want to see a release at least
bi-weekly, regardless of the roadmap.
Even if there was a checkbox in that workflow, I would not enable it.
There are changes going on and these are valid for whatever reason. If
you don't want to see the changes, unsubscribe. :-P
But I do agree that the current roadmap does need cleaning up. There are
some blockers/criticals in there, that are obviously not
blockers/criticals. And most issues should be against CR1.
Still issues are never committed to a fix version, unless they are
(really) of priority critical or higher. The fact is that we're required
to switch to a time boxing approach, so any unresolved issue will (/can)
be bumped. If you really want to be sure that something is in a given
release, do it yourself. :-)
Carlo
Adrian Brock wrote:
If you're going to do bulk updates in JIRA can you remember
to uncheck the box so it doesn't send e-mail.
That way we don't all get mail bombed and
the e-mail servers don't grind to halt. :-)
I personally think bumping issues from release to release
is pointless. It gives a false impression to users
of what your roadmap is.
If you commit to a fix version, then you should deliver! ;-)
-------- Forwarded Message --------
From: Carlo de Wolf (JIRA) <jira-events(a)lists.jboss.org>
To: jira-notifications(a)jboss.com
Subject: [JBoss JIRA] Updated: (EJBTHREE-1328) Fixes for build-test.xml
Date: Fri, 3 Oct 2008 11:06:28 -0400 (EDT)
[
https://jira.jboss.org/jira/browse/EJBTHREE-1328?page=com.atlassian.jira....
]
Carlo de Wolf updated EJBTHREE-1328:
------------------------------------
Fix Version/s: 1.0.0-Beta5
(was: 1.0.0-Beta4)
<snip/>