I've updated the fixversions in JIRA as follows:
a) delete 4.5.0.AM1 and move all issues to 4.5.0.AM2; repeat for 11.0.0.AM1
-> AM2
b) rename AM2 -> AM1, set start date as May 17 (instead of Jun 7)
c) rename AM3 -> AM2
New schedules:
https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j...
https://issues.jboss.org/projects/JBDS?selectedItem=com.atlassian.jira.ji...
On Tue, Jun 6, 2017 at 9:33 AM, Pavol Srna <psrna(a)redhat.com> wrote:
Hi,
JBoss Tools 4.5.0.AM1 build doesn't meet our release criteria. There is an
unresolved blocking bug:
https://issues.jboss.org/browse/JBIDE-24530
preventing us releasing on time in the current sprint (#132).
The plan going forward is to release AM1 as part of the next sprint.
The master branch is no longer frozen.
Thanks,
Pavol.
--
Nick Boldt
Senior Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt /
http://nick.divbyzero.com
<
https://red.ht/sig>
TRIED. TESTED. TRUSTED. <
https://redhat.com/trusted>
@ @redhatnews <
https://twitter.com/redhatnews> Red Hat
<
https://www.facebook.com/RedHatInc>