<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
9.1.0 is something we would want to release for Mars.2
(February/March 2016).<br>
9.0.1 is something we could release earlier if we find critical
issues in 9.0.0.GA<br>
But according to Max's statistic report users don't care much if we
call our builds Alphas/Betas/CRs or GA/Final. It means it doesn't
make much sense to release 9.0.1.Final close to 9.1.0.Beta.<br>
<br>
So, my proposal would be:<br>
1. Plan to release 9.1.0.Beta1 in Xmas and 9.1.0.GA around Eclipse
Mars.2 (February/March 2016)<br>
2. If we find any critical issue in 9.0.0.GA we want to fix earlier
we could release 9.0.1 in November.<br>
<br>
If it's OK I would move all current 9.0.1 issues to 9.1.0.Beta1. And
remove 9.0.1 not to confuse devs and QE. If we have any critical
issues and we see that we need release 9.0.1 then we will create
this version in JIRA.<br>
<br>
WDYT?<br>
<br>
<div class="moz-cite-prefix">On 10/14/2015 03:06 PM, Fred Bricon
wrote:<br>
</div>
<blockquote
cite="mid:CACvX+KhiLFn5PDMqJ4SvR9BWr77Lw4bRGgWyD_6N6cKBNXo-sg@mail.gmail.com"
type="cite">
<div dir="ltr">Can we rename 9.0.1.Beta1 to 9.1.0.Beta1 in JIRA,
if need be?</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Oct 14, 2015 at 2:29 PM, Alexey
Kazakov <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:alkazako@redhat.com" target="_blank">alkazako@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> 4.3.1.Beta1 yes.<br>
9.0.1.Beta1 probably yes too, but not sure we will release
9.0.1. It's possible that we will release 9.1.0 Only.
Anyway 9.1.0 will use 4.3.x branch so, we can have both
9.0.1.Beta1 and 9.1.0.Beta1 and if we don't release 9.0.1
we will move all 9.0.1 issues to 9.1.0.
<div>
<div class="h5"><br>
<br>
<div>On 10/14/2015 02:22 PM, Denis Golovin wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Should we create specific development
versions for 4.3.x/9.0.x streams in JIRA?
<div>Something like:</div>
<div>- 4.3.1.Beta1</div>
<div>- 9.0.1.Beta1<br>
</div>
<div><br>
</div>
<div>Then we can use it in fixed issues.</div>
<div><br>
</div>
<div>Currently I see only 4.3.1.Final and <a
moz-do-not-send="true" href="http://9.0.1.GA"
target="_blank">9.0.1.GA</a> are available.</div>
<div><br>
</div>
<div>Denis</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Oct 9, 2015 at
9:41 AM, Alexey Kazakov <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:alkazako@redhat.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:alkazako@redhat.com">alkazako@redhat.com</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">Hi all,<br>
<br>
Please make sure when you are fixing anything
in both 4.3.x and master<br>
branches, create a separate issue for every
stream. So we will have two<br>
JIRAs (the original one + a clone), one for
4.4.0 and the second one for<br>
4.3.0.<br>
It will help QE to verify the issue is fixed
in both streams. Remember<br>
we have different cycles for maintenance and
main releases.<br>
It's OK to have multiple fix versions in one
JIRA while you are working<br>
on it. It's NOT OK to resolve an issue with
the only fix version and w/o<br>
a clone while applying a PR to both streams!<br>
<br>
Thanks.<br>
_______________________________________________<br>
jbosstools-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:jbosstools-dev@lists.jboss.org"
target="_blank">jbosstools-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev"
rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br>
<span><font color="#888888"><br>
--<br>
<br>
<br>
CONFIDENTIALITY NOTICE: This email and
files attached to it are<br>
confidential. If you are not the intended
recipient you are hereby notified<br>
that using, copying, distributing or
taking any action in reliance on the<br>
contents of this information is strictly
prohibited. If you have received<br>
this email in error please notify the
sender and delete this email.<br>
</font></span></blockquote>
</div>
<br>
</div>
<br>
<div style="font-family:Arial,Helvetica,sans-serif">
<p style="margin-bottom:0.08in"><span
style="font-family:Arial,serif;background-color:rgb(255,255,255)"><font
size="1" color="#808080">CONFIDENTIALITY
NOTICE: This email and files attached to it
are confidential. If you are not the
intended recipient you are hereby notified
that using, copying, distributing or taking
any action in reliance on the contents of
this information is strictly prohibited. If
you have received this email in error please
notify the sender and delete this email.</font></span></p>
</div>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
jbosstools-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev"
rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>