On 23/07/2015 5:04 AM, Omair Majid wrote:
Hi Dalibor,
Thanks for the responses! I have a few follow on questions that mostly
stem from my unfamiliarity with JIRA.
* dalibor topic <dalibor.to...@oracle.com> [2015-07-22 13:05]:
On 20.07.2015 17:36, Omair Majid wrote:
Could be there be conflicts would Open and
Proprietary bugs? If so, any tips to minimize those conflicts?
An interesting potential source of conflict is that hgupdater creates
backports entries in JBS. So you want to ensure that for jdk7u forests it's
configured in a way that lets you easily distinguish issues.
That's why we had this thread back in March:
http://mail.openjdk.java.net/pipermail/jdk7u-dev/2015-March/010279.html
What about manual OpenJDK7-specific issues? Can we create those
manually?
For example, there is no special representation of the milestones like
Rampdown Phase 2 in the JDK JBS Project. Instead, they were tracked
separately - see https://wiki.openjdk.java.net/display/jdk7u/JDK+7u80 for an
example.
Thank you, this clarifies things. Is there a way to say "We expect this
bug to be resolved in OpenJDK 7u99" in JIRA? Bugzilla calls this "Target
Milestone" [1].
That way, when an issue X is marked as Fixed in Version OpenJDK 7, Resolved
in Build b85, you could distinguish it from one that is marked as fixed in
version 7u85, Resolved in Build b01 (as would for example be the case for
issues addressed in Oracle's JDK).
Can we mark an issue as Fixed in Version OpenJDK 7, Resolved in Build
7u85? I expect future "releases" of OpenJDK7u to continue using the 7uXY
versioning scheme that has been used in the past (I don't know if we
will use many build numbers, however).
7u85 is not a "build number" but a "version". The allowed values for
build numbers is constrained in JBS and currently only includes some
things that are not build numbers due to the way the system had to be
initialized from our internal bug systems (as I understand it).
If you want to keep track of OpenJDK7u fixes relative to their Oracle
JDK 7u counterparts then using backport issues may be the way to go.
David
Thanks,
Omair
[1] https://bugzilla.readthedocs.org/en/latest/using/understanding.html
