+1: 9.0.1.* issues move/rename to 9.1.0.Beta1 (Xmas), with 9.1.0.GA in March.
---
If we decide we need a 9.0.1 release in November, here's how that will
align JBT/JBDS:
* 4.3.1.Final as input to 9.0.1.GA,
* 4.3.2.Beta1 as input to 9.1.0.Beta1, and
* 4.3.2.Final as input to 9.1.0.GA.
So it's doable, but would result in having to backlevel JBDS from its
current 9.1.0 versioning.
Is this a likely scenario? Should I call what's in 4.3.x branch
9.0.1.CR1 instead of 9.1.0?
On Wed, Oct 14, 2015 at 3:39 PM, Alexey Kazakov <alkazako(a)redhat.com> wrote:
9.1.0 is something we would want to release for Mars.2
(February/March
2016).
9.0.1 is something we could release earlier if we find critical issues in
9.0.0.GA
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.
So, my proposal would be:
1. Plan to release 9.1.0.Beta1 in Xmas and 9.1.0.GA around Eclipse Mars.2
(February/March 2016)
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.
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.
WDYT?
On 10/14/2015 03:06 PM, Fred Bricon wrote:
Can we rename 9.0.1.Beta1 to 9.1.0.Beta1 in JIRA, if need be?
On Wed, Oct 14, 2015 at 2:29 PM, Alexey Kazakov <alkazako(a)redhat.com> wrote:
>
> 4.3.1.Beta1 yes.
> 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.
>
>
> On 10/14/2015 02:22 PM, Denis Golovin wrote:
>
> Should we create specific development versions for 4.3.x/9.0.x streams in
> JIRA?
> Something like:
> - 4.3.1.Beta1
> - 9.0.1.Beta1
>
> Then we can use it in fixed issues.
>
> Currently I see only 4.3.1.Final and 9.0.1.GA are available.
>
> Denis
>
>
> On Fri, Oct 9, 2015 at 9:41 AM, Alexey Kazakov <alkazako(a)redhat.com>
> wrote:
>>
>> Hi all,
>>
>> Please make sure when you are fixing anything in both 4.3.x and master
>> branches, create a separate issue for every stream. So we will have two
>> JIRAs (the original one + a clone), one for 4.4.0 and the second one for
>> 4.3.0.
>> It will help QE to verify the issue is fixed in both streams. Remember
>> we have different cycles for maintenance and main releases.
>> It's OK to have multiple fix versions in one JIRA while you are working
>> on it. It's NOT OK to resolve an issue with the only fix version and w/o
>> a clone while applying a PR to both streams!
>>
>> Thanks.
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> --
>>
>>
>> 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.
>
>
>
> 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.
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio