You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by Richard Downer <ri...@apache.org> on 2018/09/03 12:17:50 UTC
Time to make a release?
All,
It's probably about time we made a release - shockingly, it's been nearly a
year since the last one.
We want to start the release train towards a 1.0 release, but I think we
could benefit from an interim release first, given that the paint is still
drying on the new UI. Therefore I propose a "milestone 1" release,
1.0.0-M1. I'm happy to volunteer to be release manager on this one.
Thoughts, comments, +1 or -1?
Cheers
Richard
Re: Time to make a release?
Posted by Aled Sage <al...@gmail.com>.
Thanks Richard.
Yesterday evening, I fixed a regression (in detecting recursive
references in entity config). The PR has now been merged [1]. It would
be a nice-to-have to include this in the milestone release, but it's not
a blocker.
If you haven't kicked off the build, could you cherry-pick this please
(assuming you agree).
But if you have already built it, then let's only pull in this PR if we
need to produce a second release candidate for other reasons.
Aled
[1] https://github.com/apache/brooklyn-server/pull/987
On 07/09/2018 11:18, Richard Downer wrote:
> Ok, the stars have aligned for a release - I've got a smoke test build
> passing and all the requested PRs have been merged.
>
> Here's what the first release candidate will be built from:
>
> brooklyn-server: e601350d75eb61f0056f4900eca898426348ced9
> https://github.com/apache/brooklyn-server/commits/e601350d75eb61f0056f4900eca898426348ced9
>
> brooklyn-library: a94f7d84ebcd984ec7c44d62add2f00d5e663717
> https://github.com/apache/brooklyn-library/commits/a94f7d84ebcd984ec7c44d62add2f00d5e663717
>
>
> brooklyn-docs: 2b06e9605e1ee23f27f0d81d249074a60350cff6
> https://github.com/apache/brooklyn-docs/commits/2b06e9605e1ee23f27f0d81d249074a60350cff6
>
> brooklyn-client: 05031a79d4724b867db76b7c4afe55190666c7af
> https://github.com/apache/brooklyn-client/commits/05031a79d4724b867db76b7c4afe55190666c7af
>
> brooklyn-ui: 503d74eb20bc5206daaa0cfcf1f55b2e0cd0d5c9
> https://github.com/apache/brooklyn-ui/commits/503d74eb20bc5206daaa0cfcf1f55b2e0cd0d5c9
>
> brooklyn-dist: 3a30944e22052bb7b9c406e285a73f0e9236d0f7
> https://github.com/apache/brooklyn-dist/commits/3a30944e22052bb7b9c406e285a73f0e9236d0f7
>
> More updates to follow.
>
> Richard.
>
>
> On Tue, 4 Sep 2018 at 10:25, Richard Downer <ri...@apache.org> wrote:
>
>> Looks like we have a consensus.
>>
>> **KLAXON**
>>
>> Last call for PRs before the release. Please let me know TODAY if there's
>> anything that needs to go in. Tomorrow morning I'll assess the requested
>> PRs and get a release started.
>>
>> Richard.
>>
>>
>> On Tue, 4 Sep 2018 at 09:41, Thomas Bouron <
>> thomas.bouron@cloudsoftcorp.com> wrote:
>>
>>> +1
>>>
>>> On Tue, 4 Sep 2018 at 09:34 Geoff Macartney <ge...@gmail.com>
>>> wrote:
>>>
>>>> +1 to an interim release
>>>>
>>>> On Mon, 3 Sep 2018 at 13:31 Alex Heneveld <
>>>> alex.heneveld@cloudsoftcorp.com>
>>>> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> We might want to make an effort to get these merged (but I don't think
>>>>> it's critical):
>>>>>
>>>>> * https://github.com/apache/brooklyn-server/pulls
>>>>> #982 - better type coercion
>>>>> #971 - location DSL
>>>>>
>>>>> There are a few others in library, docs, and dist, which we should take
>>>>> care of as general housekeeping but not ahead of an M1 IMO.
>>>>>
>>>>> Best
>>>>> Alex
>>>>>
>>>>>
>>>>> On 03/09/2018 13:24, Aled Sage wrote:
>>>>>> +1
>>>>>>
>>>>>> Assuming there's consensus, shall we give 24 hours for folk to get
>>>> any
>>>>>> outstanding PRs submitted/merged, before we kick an RC1 etc?
>>>>>>
>>>>>> Aled
>>>>>>
>>>>>>
>>>>>> On 03/09/2018 13:17, Richard Downer wrote:
>>>>>>> All,
>>>>>>>
>>>>>>> It's probably about time we made a release - shockingly, it's been
>>>>>>> nearly a
>>>>>>> year since the last one.
>>>>>>>
>>>>>>> We want to start the release train towards a 1.0 release, but I
>>>> think we
>>>>>>> could benefit from an interim release first, given that the paint is
>>>>>>> still
>>>>>>> drying on the new UI. Therefore I propose a "milestone 1" release,
>>>>>>> 1.0.0-M1. I'm happy to volunteer to be release manager on this one.
>>>>>>>
>>>>>>> Thoughts, comments, +1 or -1?
>>>>>>>
>>>>>>> Cheers
>>>>>>> Richard
>>>>>>>
>>>>>
>>> --
>>>
>>> Thomas Bouron
>>> Senior Software Engineer
>>>
>>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>>>
>>> GitHub: https://github.com/tbouron
>>> Twitter: https://twitter.com/eltibouron
>>>
>>> Need a hand with AWS? Get a Free Consultation.
>>>
Re: Time to make a release?
Posted by Richard Downer <ri...@apache.org>.
Ok, the stars have aligned for a release - I've got a smoke test build
passing and all the requested PRs have been merged.
Here's what the first release candidate will be built from:
brooklyn-server: e601350d75eb61f0056f4900eca898426348ced9
https://github.com/apache/brooklyn-server/commits/e601350d75eb61f0056f4900eca898426348ced9
brooklyn-library: a94f7d84ebcd984ec7c44d62add2f00d5e663717
https://github.com/apache/brooklyn-library/commits/a94f7d84ebcd984ec7c44d62add2f00d5e663717
brooklyn-docs: 2b06e9605e1ee23f27f0d81d249074a60350cff6
https://github.com/apache/brooklyn-docs/commits/2b06e9605e1ee23f27f0d81d249074a60350cff6
brooklyn-client: 05031a79d4724b867db76b7c4afe55190666c7af
https://github.com/apache/brooklyn-client/commits/05031a79d4724b867db76b7c4afe55190666c7af
brooklyn-ui: 503d74eb20bc5206daaa0cfcf1f55b2e0cd0d5c9
https://github.com/apache/brooklyn-ui/commits/503d74eb20bc5206daaa0cfcf1f55b2e0cd0d5c9
brooklyn-dist: 3a30944e22052bb7b9c406e285a73f0e9236d0f7
https://github.com/apache/brooklyn-dist/commits/3a30944e22052bb7b9c406e285a73f0e9236d0f7
More updates to follow.
Richard.
On Tue, 4 Sep 2018 at 10:25, Richard Downer <ri...@apache.org> wrote:
> Looks like we have a consensus.
>
> **KLAXON**
>
> Last call for PRs before the release. Please let me know TODAY if there's
> anything that needs to go in. Tomorrow morning I'll assess the requested
> PRs and get a release started.
>
> Richard.
>
>
> On Tue, 4 Sep 2018 at 09:41, Thomas Bouron <
> thomas.bouron@cloudsoftcorp.com> wrote:
>
>> +1
>>
>> On Tue, 4 Sep 2018 at 09:34 Geoff Macartney <ge...@gmail.com>
>> wrote:
>>
>>> +1 to an interim release
>>>
>>> On Mon, 3 Sep 2018 at 13:31 Alex Heneveld <
>>> alex.heneveld@cloudsoftcorp.com>
>>> wrote:
>>>
>>> >
>>> > +1
>>> >
>>> > We might want to make an effort to get these merged (but I don't think
>>> > it's critical):
>>> >
>>> > * https://github.com/apache/brooklyn-server/pulls
>>> > #982 - better type coercion
>>> > #971 - location DSL
>>> >
>>> > There are a few others in library, docs, and dist, which we should take
>>> > care of as general housekeeping but not ahead of an M1 IMO.
>>> >
>>> > Best
>>> > Alex
>>> >
>>> >
>>> > On 03/09/2018 13:24, Aled Sage wrote:
>>> > > +1
>>> > >
>>> > > Assuming there's consensus, shall we give 24 hours for folk to get
>>> any
>>> > > outstanding PRs submitted/merged, before we kick an RC1 etc?
>>> > >
>>> > > Aled
>>> > >
>>> > >
>>> > > On 03/09/2018 13:17, Richard Downer wrote:
>>> > >> All,
>>> > >>
>>> > >> It's probably about time we made a release - shockingly, it's been
>>> > >> nearly a
>>> > >> year since the last one.
>>> > >>
>>> > >> We want to start the release train towards a 1.0 release, but I
>>> think we
>>> > >> could benefit from an interim release first, given that the paint is
>>> > >> still
>>> > >> drying on the new UI. Therefore I propose a "milestone 1" release,
>>> > >> 1.0.0-M1. I'm happy to volunteer to be release manager on this one.
>>> > >>
>>> > >> Thoughts, comments, +1 or -1?
>>> > >>
>>> > >> Cheers
>>> > >> Richard
>>> > >>
>>> > >
>>> >
>>> >
>>>
>> --
>>
>> Thomas Bouron
>> Senior Software Engineer
>>
>> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>>
>> GitHub: https://github.com/tbouron
>> Twitter: https://twitter.com/eltibouron
>>
>> Need a hand with AWS? Get a Free Consultation.
>>
>
Re: Time to make a release?
Posted by Richard Downer <ri...@apache.org>.
Looks like we have a consensus.
**KLAXON**
Last call for PRs before the release. Please let me know TODAY if there's
anything that needs to go in. Tomorrow morning I'll assess the requested
PRs and get a release started.
Richard.
On Tue, 4 Sep 2018 at 09:41, Thomas Bouron <th...@cloudsoftcorp.com>
wrote:
> +1
>
> On Tue, 4 Sep 2018 at 09:34 Geoff Macartney <ge...@gmail.com>
> wrote:
>
>> +1 to an interim release
>>
>> On Mon, 3 Sep 2018 at 13:31 Alex Heneveld <
>> alex.heneveld@cloudsoftcorp.com>
>> wrote:
>>
>> >
>> > +1
>> >
>> > We might want to make an effort to get these merged (but I don't think
>> > it's critical):
>> >
>> > * https://github.com/apache/brooklyn-server/pulls
>> > #982 - better type coercion
>> > #971 - location DSL
>> >
>> > There are a few others in library, docs, and dist, which we should take
>> > care of as general housekeeping but not ahead of an M1 IMO.
>> >
>> > Best
>> > Alex
>> >
>> >
>> > On 03/09/2018 13:24, Aled Sage wrote:
>> > > +1
>> > >
>> > > Assuming there's consensus, shall we give 24 hours for folk to get any
>> > > outstanding PRs submitted/merged, before we kick an RC1 etc?
>> > >
>> > > Aled
>> > >
>> > >
>> > > On 03/09/2018 13:17, Richard Downer wrote:
>> > >> All,
>> > >>
>> > >> It's probably about time we made a release - shockingly, it's been
>> > >> nearly a
>> > >> year since the last one.
>> > >>
>> > >> We want to start the release train towards a 1.0 release, but I
>> think we
>> > >> could benefit from an interim release first, given that the paint is
>> > >> still
>> > >> drying on the new UI. Therefore I propose a "milestone 1" release,
>> > >> 1.0.0-M1. I'm happy to volunteer to be release manager on this one.
>> > >>
>> > >> Thoughts, comments, +1 or -1?
>> > >>
>> > >> Cheers
>> > >> Richard
>> > >>
>> > >
>> >
>> >
>>
> --
>
> Thomas Bouron
> Senior Software Engineer
>
> *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
>
> GitHub: https://github.com/tbouron
> Twitter: https://twitter.com/eltibouron
>
> Need a hand with AWS? Get a Free Consultation.
>
Re: Time to make a release?
Posted by Thomas Bouron <th...@cloudsoftcorp.com>.
+1
On Tue, 4 Sep 2018 at 09:34 Geoff Macartney <ge...@gmail.com>
wrote:
> +1 to an interim release
>
> On Mon, 3 Sep 2018 at 13:31 Alex Heneveld <alex.heneveld@cloudsoftcorp.com
> >
> wrote:
>
> >
> > +1
> >
> > We might want to make an effort to get these merged (but I don't think
> > it's critical):
> >
> > * https://github.com/apache/brooklyn-server/pulls
> > #982 - better type coercion
> > #971 - location DSL
> >
> > There are a few others in library, docs, and dist, which we should take
> > care of as general housekeeping but not ahead of an M1 IMO.
> >
> > Best
> > Alex
> >
> >
> > On 03/09/2018 13:24, Aled Sage wrote:
> > > +1
> > >
> > > Assuming there's consensus, shall we give 24 hours for folk to get any
> > > outstanding PRs submitted/merged, before we kick an RC1 etc?
> > >
> > > Aled
> > >
> > >
> > > On 03/09/2018 13:17, Richard Downer wrote:
> > >> All,
> > >>
> > >> It's probably about time we made a release - shockingly, it's been
> > >> nearly a
> > >> year since the last one.
> > >>
> > >> We want to start the release train towards a 1.0 release, but I think
> we
> > >> could benefit from an interim release first, given that the paint is
> > >> still
> > >> drying on the new UI. Therefore I propose a "milestone 1" release,
> > >> 1.0.0-M1. I'm happy to volunteer to be release manager on this one.
> > >>
> > >> Thoughts, comments, +1 or -1?
> > >>
> > >> Cheers
> > >> Richard
> > >>
> > >
> >
> >
>
--
Thomas Bouron
Senior Software Engineer
*Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud
GitHub: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
Need a hand with AWS? Get a Free Consultation.
Re: Time to make a release?
Posted by Geoff Macartney <ge...@gmail.com>.
+1 to an interim release
On Mon, 3 Sep 2018 at 13:31 Alex Heneveld <al...@cloudsoftcorp.com>
wrote:
>
> +1
>
> We might want to make an effort to get these merged (but I don't think
> it's critical):
>
> * https://github.com/apache/brooklyn-server/pulls
> #982 - better type coercion
> #971 - location DSL
>
> There are a few others in library, docs, and dist, which we should take
> care of as general housekeeping but not ahead of an M1 IMO.
>
> Best
> Alex
>
>
> On 03/09/2018 13:24, Aled Sage wrote:
> > +1
> >
> > Assuming there's consensus, shall we give 24 hours for folk to get any
> > outstanding PRs submitted/merged, before we kick an RC1 etc?
> >
> > Aled
> >
> >
> > On 03/09/2018 13:17, Richard Downer wrote:
> >> All,
> >>
> >> It's probably about time we made a release - shockingly, it's been
> >> nearly a
> >> year since the last one.
> >>
> >> We want to start the release train towards a 1.0 release, but I think we
> >> could benefit from an interim release first, given that the paint is
> >> still
> >> drying on the new UI. Therefore I propose a "milestone 1" release,
> >> 1.0.0-M1. I'm happy to volunteer to be release manager on this one.
> >>
> >> Thoughts, comments, +1 or -1?
> >>
> >> Cheers
> >> Richard
> >>
> >
>
>
Re: Time to make a release?
Posted by Alex Heneveld <al...@cloudsoftcorp.com>.
+1
We might want to make an effort to get these merged (but I don't think
it's critical):
* https://github.com/apache/brooklyn-server/pulls
#982 - better type coercion
#971 - location DSL
There are a few others in library, docs, and dist, which we should take
care of as general housekeeping but not ahead of an M1 IMO.
Best
Alex
On 03/09/2018 13:24, Aled Sage wrote:
> +1
>
> Assuming there's consensus, shall we give 24 hours for folk to get any
> outstanding PRs submitted/merged, before we kick an RC1 etc?
>
> Aled
>
>
> On 03/09/2018 13:17, Richard Downer wrote:
>> All,
>>
>> It's probably about time we made a release - shockingly, it's been
>> nearly a
>> year since the last one.
>>
>> We want to start the release train towards a 1.0 release, but I think we
>> could benefit from an interim release first, given that the paint is
>> still
>> drying on the new UI. Therefore I propose a "milestone 1" release,
>> 1.0.0-M1. I'm happy to volunteer to be release manager on this one.
>>
>> Thoughts, comments, +1 or -1?
>>
>> Cheers
>> Richard
>>
>
Re: Time to make a release?
Posted by Aled Sage <al...@gmail.com>.
+1
Assuming there's consensus, shall we give 24 hours for folk to get any
outstanding PRs submitted/merged, before we kick an RC1 etc?
Aled
On 03/09/2018 13:17, Richard Downer wrote:
> All,
>
> It's probably about time we made a release - shockingly, it's been nearly a
> year since the last one.
>
> We want to start the release train towards a 1.0 release, but I think we
> could benefit from an interim release first, given that the paint is still
> drying on the new UI. Therefore I propose a "milestone 1" release,
> 1.0.0-M1. I'm happy to volunteer to be release manager on this one.
>
> Thoughts, comments, +1 or -1?
>
> Cheers
> Richard
>