[jbosstools-dev] ACTION REQUIRED: Prepare for 4.2.1.Final / 8.0.1.GA (release is next week Dec 15 2014)

[Alexey Kazakov]

Thanks to all component leads who updated their root poms (and I updated 
the rest of components: forge, aerogear, central, freemarker).
So all components that have been changed since 4.2.0 are using 
4.2.1.Final-SNAPSHOT root pom now.
However, two components, Birt and Portlet don't have any changes besides 
updated root poms. As I understand we should change the root pom versio 
ONLY if the component has been changed since 4.2.0.Final.
I reopened the corresponding issues for Birt and Portlet for clarification:
https://issues.jboss.org/browse/JBIDE-18890
https://issues.jboss.org/browse/JBIDE-18896
Should we ignore these changes and not to rebuild Birt & Portlet for 4.2.1?

On 12/08/2014 12:54 PM, Nick Boldt wrote:
> TL;DR: Yes.
>
>> I did not create task JIRAs for Hibernate and Livereload, because
>> neither of those have commits in the 4.2.x branch since 4.2.0.Final and
>> therefore need not have their root poms adjusted.
>
> On 12/08/2014 02:01 AM, Max Rydahl Andersen wrote:
>>
>>> On 08 Dec 2014, at 04:19, Nick Boldt <nboldt at redhat.com> wrote:
>>>
>>> his week is the "quiet period" in prep for 4.2.1.Final / 8.0.1.GA.
>>>
>>> You are required to update your root poms to point at the latest parent
>>> pom,
>> I assume you mean "If and only if the build your component is in has changed since 4.2.0.Final", correct ?
>>
>> As otherwise we are going to have updates to *everything* which is what we don't want for our maintanence builds.
>>
>> Just want to make sure the above is what you meant or to know if you found something in our build that requires *every* component to update parent Pom?
>>
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20141208/329f4cbc/attachment.html