[jbosstools-dev] ACTION REQUIRED: JBoss Tools 4.2.3.Beta1 / JBDS 8.1.0.Beta1 Code Freeze is Thursday Feb 25

[Nick Boldt]

Current status:

All builds are blue EXCEPT the following:

JavaEE - build timeout after 2hrs (last time it was blue it only took 
1hr 24 min) and 1 test failure due to NPE: 
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-javaee_4.2.luna/87/testReport/junit/org.jboss.tools.jsf.vpe.jsf.test.jbide/JBIDE1805Test/testJBIDE1805/

Arquillian, Birt, Central, Freemarker, LiveReload, Portlet, Webservices 
- disabled: no changes for 4.2.3.Beta1

Warnings (yellow builds) for Versionwatch [bootstrapping problem I think 
I've fixed] and p2director-install-tests [was using Luna SR1 to do the 
install so getting version conflicts]. Both are respinning now.

If everyone is already done for Beta1, I can stage the bits for QE earlier.

Are there outstanding issues you're working on for Beta1? If so, please 
speak up and let me know the JIRA #s so I can monitor when they're done 
and ensure they get built.

Nick

On 02/26/2015 12:23 PM, Alexey Kazakov wrote:
> On 02/25/2015 06:50 PM, Nick Boldt wrote:
>> Just a reminder, today (Europe time) / tomorrow (US/Canada time) is the
>> JBoss Tools 4.2.3.Beta1 / JBDS 8.1.0.Beta1 Code Freeze.
>>
>> ---
>>
>> Since we're already building from the 4.2.x branch, we *could* create
>> 4.2.3.Beta1x branches if we wanted that extra overhead, but I think it's
>> much simpler to simply code freeze in the 4.2.x branch by EOD Thursday
>> Feb 25.
> +1. We are not going to make any respins for Beta1 so let's freeze the
> 4.2.x branch and don't create 4.2.3.Beta1x branches.
>
>>
>> We can then spin up the builds Friday & have bits for QE by Monday.
>>
>> Once that's announced, you can tag your sources, and the 4.2.x branch
>> will re-open for urgent, blocker/critical fixes aimed at JBT 4.2.3.CR1 /
>> JBDS 8.1.0.CR1.
>>
>> ---
>>
>> As a reminder, if you haven't already updated your root pom to use the
>> 4.2.3.Beta1 parent pom, or you haven't bumped your versions to a version
>> greater than what was released in JBoss Tools 4.2.2, please do so. If
>> you need instructions on how to do so, see the child tasks under this JIRA:
>>
>> https://issues.jboss.org/browse/JBIDE-19124
>>
>> If your component DOES NOT have a JIRA under there, but you have changes
>> in the 4.2.x branch planned to be included in 4.2.3, please create a
>> child task so I know that you have things to build.
>>
>> ---
>>
>> Any questions, please don't hesitate to ask me, Alexey, Denis, Fred,
>> Max, or Mickael.
>>
>
> _______________________________________________
> 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