[jbosstools-dev] ACTION REQUIRED: Alpha2 Code Freeze is TODAY (April 16, 2015)

Max Rydahl Andersen manderse at redhat.com
Thu Apr 16 16:44:25 EDT 2015


yeah - the refactoring of build structure makes it fail.

we can't verify the build before branch.

branched for web services since xcoulon is not awake now.

> On 04/16/2015 01:13 PM, Nick Boldt wrote:
>> Open to suggestions for how to make the upstream components already
>> built before they're branched. Do you want me to bootstrap with the
>> previous milestone so you're building against Alpha1 bits instead of
>> Alpha2 ones?
>>
>> Also wondering why, if your sources in master are building blue, 
>> you're
>> worried they'll suddenly be red when all you've done is create a 
>> branch
>> point. Surely if your master job is blue you can branch safely?
> Then our Jira descriptions for code freezes are not correct since they 
> tell component leads to verify the build is working/no test failures 
> BEFORE brahcning:
> 3. Ensure you've built & run your plugin tests using the latest target 
> platform version 4.50.0.Alpha2;
>
> mvn clean verify -Dtpc.version=4.50.0.Alpha2
>
> from https://issues.jboss.org/browse/JBIDE-19608
> Anyway, if I need to test any last minute changes or the new target 
> platform, whatever. I cannot do it for the upcoming version which we 
> are code freezing. I can do it for master only.
>
> And BTW I have never faced this problem before. Did we change 
> anything?
>
>
>
>> N
>>
>> On 04/16/2015 04:09 PM, Alexey Kazakov wrote:
>>> Done for base, jst, javaee.
>>> But I had to branch jst and javaee blindly because Aplha1 build is
>>> failing for them right now:
>>> https://issues.jboss.org/browse/JBIDE-19618?focusedCommentId=13059851&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13059851
>>>
>>> There is something wrong that we can't build the code freeze branch 
>>> (I
>>> need to test it locally before pushing to master) on the day of code
>>> freeze and have to wait until all components which you depend on are
>>> branched/built and published on our jenkins.
>>>
>>>
>>> On 04/16/2015 09:32 AM, Nick Boldt wrote:
>>>> Please perform the steps in these task jiras to prepare yourself 
>>>> for
>>>> code freeze.
>>>>
>>>> If you need more time (eg., another day) before you can branch, 
>>>> please
>>>> let me know.
>>>>
>>>> JBoss Tools       : https://issues.jboss.org/browse/JBIDE-19608
>>>> Aerogear          : https://issues.jboss.org/browse/JBIDE-19609
>>>> JBT Update Sites  : https://issues.jboss.org/browse/JBIDE-19610
>>>> VPE               : https://issues.jboss.org/browse/JBIDE-19611
>>>> Central Discovery : https://issues.jboss.org/browse/JBIDE-19612
>>>> Server            : https://issues.jboss.org/browse/JBIDE-19613
>>>> Hibernate         : https://issues.jboss.org/browse/JBIDE-19614
>>>> Base              : https://issues.jboss.org/browse/JBIDE-19615
>>>> OpenShift         : https://issues.jboss.org/browse/JBIDE-19616
>>>> JavaEE            : https://issues.jboss.org/browse/JBIDE-19617
>>>> JST               : https://issues.jboss.org/browse/JBIDE-19618
>>>> Forge             : https://issues.jboss.org/browse/JBIDE-19619
>>>> Birt              : https://issues.jboss.org/browse/JBIDE-19620
>>>> BrowserSim        : https://issues.jboss.org/browse/JBIDE-19621
>>>> Webservices       : https://issues.jboss.org/browse/JBIDE-19622
>>>> Arquillian        : https://issues.jboss.org/browse/JBIDE-19623
>>>> Central           : https://issues.jboss.org/browse/JBIDE-19624
>>>> LiveReload        : https://issues.jboss.org/browse/JBIDE-19625
>>>>
>>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen



More information about the jbosstools-dev mailing list