brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Downer <rich...@apache.org>
Subject Re: Next release candidate
Date Tue, 18 Apr 2017 12:58:50 GMT
All in. Thanks all! New release candidate being built.

Richard.


On 18 April 2017 at 11:43, Aled Sage <aled.sage@gmail.com> wrote:

> I'd also like us to include:
>
>     https://github.com/apache/brooklyn-server/pull/639
>
> which fixes:
>
>     https://issues.apache.org/jira/browse/BROOKLYN-475
>
> Aled
>
>
>
> On 18/04/2017 09:54, Graeme Miller wrote:
>
>> Hi Richard,
>>
>> Duncan Grant, should this PR be merged in as it fixes node.js
>> requirements:
>> https://github.com/apache/brooklyn-library/pull/98
>>
>> Also, there are two fixes here for rebind:
>> https://github.com/apache/brooklyn-server/pull/633
>> https://github.com/apache/brooklyn-server/pull/634
>>
>> Regards,
>> Graeme
>>
>>
>> On 18 April 2017 at 09:45, Duncan Godwin <duncan.godwin@cloudsoftcorp.com
>> >
>> wrote:
>>
>> Hi Richard,
>>>
>>> These PRs fix JBoss in Ubuntu 16+
>>>
>>> https://github.com/apache/brooklyn-server/pull/636
>>> https://github.com/apache/brooklyn-library/pull/100
>>>
>>> And this PR improves our password generation by ensuring we're using
>>> secure
>>> random not random:
>>>
>>> https://github.com/apache/brooklyn-library/pull/99
>>>
>>> I think having them in, especially the last one would be good.
>>>
>>> Many thanks
>>>
>>> Duncan
>>>
>>> On 18 April 2017 at 08:00, Richard Downer <richard@apache.org> wrote:
>>>
>>> All,
>>>>
>>>> What PRs should be merged into our release branch for the next 0.11.0
>>>> RC?
>>>>
>>>> Jira ticket BROOKLYN-473 was the release blocker, and it is fixed by:
>>>> https://github.com/apache/brooklyn-server/pull/634
>>>> https://github.com/apache/brooklyn-server/pull/633
>>>> so they are in.
>>>>
>>>> I've also had a request to merge
>>>> https://github.com/apache/brooklyn-library/pull/98, which fixes the
>>>> Node.js
>>>> entity on recent Ubuntu releases. I'd normally want to avoid too many
>>>> last-minute inclusions, but Node.js is popular at the moment so having a
>>>> working entity is desirable, and the PR looks low risk.
>>>>
>>>> Anything else?
>>>>
>>>> I'm planning to kick off the release at around 12:00 UTC today (1pm UK
>>>> time) so please respond ASAP.
>>>>
>>>> Thanks
>>>> Richard.
>>>>
>>>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message