[rules-dev] [jbpm-dev] Release - 5.5.0.Final (Drools) \ 5.4.0.Final (jBPM)

[Michael Anstis]

Release of 5.5.0.Final is delayed.

I am waiting on a pull request from a community member for Guvnor User
Guide additions.

Please be sure to update the Release
Notes<https://github.com/droolsjbpm/droolsjbpm-knowledge/blob/5.5.x/droolsjbpm-introduction-docs/src/main/docbook/en-US/Chapter-Release_Notes/Section-What_is_new_Drools_5.5.0.xml>and
applicable User Guide(s) if not already done so...

I will keep you all advised.

With kind regards,

Mike

On 6 November 2012 21:22, Kris Verlaenen <kverlaen at redhat.com> wrote:

>  You can just download the distribution artefacts from nexus, and test
> them out, which is what I typically do.
> You could also configure the staging repository as a maven repo if you
> want.
>
> Some related info can be found here:
> https://community.jboss.org/wiki/MavenDeployingARelease
>
> Kris
>
>
> On 11/06/2012 07:46 PM, Michael Anstis wrote:
>
> Hi Kris,
>
> I was hoping to start Wednesday morning, GMT time. Jenkins would need to
> be blue.
>
> Tags are created locally and pushed when the release process completes.
> Consequentially there are no tags on github until after the release goes
> live.
>
> I believe however that there is possibly an opportunity for the artifacts
> on Nexus to be reviewed by a wider audience before their release.
>
> I will happily shout their availability from the roof tops - I for one
> don't want to be doing a 5.5.1/5.4.1.
>
> Unfortunately I don't know if unreleased artifacts on Nexus can be
> downloaded by others (I presume they can provided you can login to Nexus).
> Anyone know?
>
> With kind regards,
>
> Mike
>
> sent on the move
>
> On 6 Nov 2012 16:00, "Kris Verlaenen" <kverlaen at redhat.com> wrote:
>
>>  Michael,
>>
>> We should make sure that we notify everyone if all artefacts are in
>> staging on nexus, so we have the possibility to do one last sanity check
>> before pushing everything out (as there's no way back then, other than
>> doing 5.5.1/5.4.0 release.  If all teams give the go ahead, we can then
>> publish them.  This to avoid any last minute issues that might show up.
>>
>> When exactly is the tagging process going to start?  So we all know by
>> what time all fixes need to be in.
>>
>> Kris
>>
>> On 11/06/2012 11:02 AM, Michael Anstis wrote:
>>
>> Hi,
>>
>> 5.5.0.Final will be released this week.
>>
>> Jenkins is not however completely blue:-
>>
>>    - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/drools-5.5.x/
>>
>>
>>    - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbpm-5.4.x/
>>
>>
>>    - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/guvnor-5.5.x/(Jervis, the failing tests appear to be as a result of the JCR\Repository
>>    start-up fix)
>>
>>
>> Please check and fix any applicable failing tests or advise accordingly.
>>
>> Please also check you have included everything in the Release Notes<https://github.com/droolsjbpm/droolsjbpm-knowledge/blob/5.5.x/droolsjbpm-introduction-docs/src/main/docbook/en-US/Chapter-Release_Notes/Section-What_is_new_Drools_5.5.0.xml>and applicable User Guides.
>>
>> This will be the last release before 6.0 next year...
>>
>> With kind regards,
>>
>> Mike
>>
>>
>> _______________________________________________
>> jbpm-dev mailing listjbpm-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbpm-dev
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20121108/d14d4d31/attachment.html