[
https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-22619:
----------------------------------------
{quote}And for JBDS issues, we also have a Target version (the GA release in which the
JIRA will be done, even if fixed in an earlier milestone). So that's THREE places
we're setting the same information.{quote}
Is it really the same information? As far as I understood, sprints are internal
information, Alpha/Beta are public and user facing ones.
{quote}So now the parent pom doesn't have to contain an Alpha/Beta quality-descriptor
- {quote}
Step by step, let's just first have the jgit build timestamps, then we'll consider
removing versions from parent pom. IMO discussing about parent pom release and so on
should be postponed after we move to jgit timestamps as it's going to be a major
change.
{quote}we only care about WHEN it's being built, not HOW GOOD it is.{quote}
I rather see the Alpha/Beta/CR... as an indicator of when it's shipped, not about
quality.
Decide strategy for fixversion targets in JIRA
----------------------------------------------
Key: JBIDE-22619
URL:
https://issues.jboss.org/browse/JBIDE-22619
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Affects Versions: 4.4.1.S116
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Fix For: 4.4.1.S116
We need to decide the strategy for milestones / fixversions in JIRA.
One suggestion has been to align fixversions w/ sprint numbers, thus:
* 4.4.1.S116, 4.4.1.S117, 4.4.1.S118, 4.4.1.S119, ...?
instead of
* 4.4.1.Alpha1, 4.4.1.Alpha2, 4.4.1.Alpha3, 4.4.1.Beta1, ... ?
Questions/concerns:
* what do we do for unscheduled milestones (4.5.0.Alpha1, 11.0.0.Alpha1) and placeholders
(4.4.1.Final, 10.0.1.GA) ? Should we just use Alpha1 or Final/GA until we know which
sprint applies?
* whatever schema we adopt has to work with bzira and jiralint
* any other systems that parse JIRA for integration purposes?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)