[jbosstools-dev] Code freeze

[Nick Boldt]

Related to this is the *target platform freeze* on Wednesday, Oct 11.
That's today... unless you're in California, in which case it's in
under 3 hrs!

If you have anything that needs to be pushed into the TP, please ask
for it ASAP by opening a JIRA assigned to me and linked to
JBIDE-22581.

For example, you might want the maven archiver updated, as in
https://issues.jboss.org/browse/JBIDE-23309

Or you might want to add something from the Neon.1 TP into the Neon.0
TP so it's available at BUILD TIME, not just at TEST TIME. Bear in
mind that there are consequences if we move up to depending on Neon.1
instead of Neon.0. See [1] for details.

[1] https://github.com/jbosstools/jbosstools-openshift/pull/1340#issuecomment-253107788



On Mon, Oct 10, 2016 at 7:41 AM, Jean-Francois Maury <jmaury at redhat.com> wrote:
> Hello,
>
> don't forget that code freeze for 4.4.2.AM2 will be this Thursday Oct 13th
> so don't forget to:
>
> submit you PRs
> review/merge existing PRs
>
>
> so that we don't got the drawback we add on the last sprint.
>
> Jeff
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev



-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com