Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: Svetoslav Neykov <svetoslav.neykov@cloudsoftcorp.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Subject: Re: Call for release: Brooklyn 0.10.0
Date: Thu, 17 Nov 2016 19:15:29 +0200
References: <610b640c-977c-7a0b-4e17-1f5f8adbb475@gmail.com>
 <80AD589B-58CB-4A87-B4EF-3480DBACDFBB@cloudsoftcorp.com>
 <CANaN7bGbS77rF8VDUqCfb2h0H8QaV9imKmeUG0kiQFW7+zTXfw@mail.gmail.com>
 <CA+gmfahOhB3ZtkjRS2L0psQPQ5AdcALAZGJgex2jh3-pp8M2uw@mail.gmail.com>
 <e3b1a04a-57f2-5aa3-cc40-e2857c2671dd@gmail.com>
 <CABQFKi27bH5kS1MkiqPZwacA_tZbwkyxcKs9NR4tYctXD8Mhhw@mail.gmail.com>
 <A6C1FB52-3D41-4546-8D73-43E2B17627DB@cloudsoftcorp.com>
 <CAJT5MU9hTDxSiZuAhBmOjVMApufja=WgBjGk8cFwqvZ4eevJbg@mail.gmail.com>
To: dev@brooklyn.apache.org
In-Reply-To: <CAJT5MU9hTDxSiZuAhBmOjVMApufja=WgBjGk8cFwqvZ4eevJbg@mail.gmail.com>
Message-Id: <9701B1E5-E674-4A74-8A18-5793258FCCD9@cloudsoftcorp.com>
archived-at: Thu, 17 Nov 2016 17:15:39 -0000

Good point about the homebrew package John. Thanks.

Svet.


> On 17.11.2016 =D0=B3., at 17:53, John McCabe <john@johnmccabe.net> =
wrote:
>=20
> If there's a cli bump feel free to ping me about the homebrew release
> process if necessary (it's pretty straight forward).
> /John
>=20
> On Thu, 17 Nov 2016, 15:19 Svetoslav Neykov, <
> svetoslav.neykov@cloudsoftcorp.com> wrote:
>=20
>> Nobody else stepped up so I guess that's me. I'll give it a go.
>>=20
>> Thanks.
>> Svet.
>>=20
>>=20
>>> On 17.11.2016 =D0=B3., at 15:40, Richard Downer <richard@apache.org> =
wrote:
>>>=20
>>> The release-manager-to-be could also start running the release =
script[1]
>> a
>>> few times in dry run mode to catch any early issues.
>>>=20
>>> [1]
>>>=20
>> =
https://github.com/apache/brooklyn-dist/blob/master/release/make-release-a=
rtifacts.sh
>>>=20
>>>=20
>>> On 17 November 2016 at 13:09, Aled Sage <aled.sage@gmail.com> wrote:
>>>=20
>>>> +1, sounds great - thanks Andrea!
>>>>=20
>>>> There are some really import jclouds fixes in 1.9.3-SNAPSHOT (or =
2.0.0)
>>>> that we want, such as an OutOfMemoryError deploying to Softlayer =
[1].
>>>>=20
>>>> It's worth hanging fire on Brooklyn 0.10.0 until we have a jclouds =
1.9.3
>>>> release.
>>>>=20
>>>> In the meantime, we should still get our own house in order by =
doing the
>>>> first of the steps below (i.e. dealing with open PRs; ensuring =
no-one
>> has
>>>> any imminent important contributions to make for 0.10.0, etc).
>>>>=20
>>>> Aled
>>>>=20
>>>> [1] https://issues.apache.org/jira/browse/BROOKLYN-364
>>>>=20
>>>>=20
>>>>=20
>>>> On 17/11/2016 11:37, Alex Heneveld wrote:
>>>>=20
>>>>> That would be a great solution Andrea!
>>>>>=20
>>>>> Best
>>>>> Alex
>>>>>=20
>>>>> On 17 Nov 2016 08:18, "Andrea Turli" =
<andrea.turli@cloudsoftcorp.com>
>>>>> wrote:
>>>>>=20
>>>>> I'm happy to volunteer for releasing an official jclouds 1.9.3 =
which
>> may
>>>>>> be
>>>>>> the half-house solution here.
>>>>>>=20
>>>>>> wdyt?
>>>>>>=20
>>>>>> Andrea
>>>>>>=20
>>>>>> On 17 November 2016 at 08:25, Svetoslav Neykov <
>>>>>> svetoslav.neykov@cloudsoftcorp.com> wrote:
>>>>>>=20
>>>>>> This is going to be the first release that actually works in =
Karaf.
>> The
>>>>>>> docs are still assuming classic though so I suggest we keep
>> recommending
>>>>>>> the classic distribution for 0.10.0.
>>>>>>> For next release let's plan on updating the docs and switching =
the
>>>>>>> recommended distribution to the Karaf based one.
>>>>>>>=20
>>>>>>> Svet.
>>>>>>>=20
>>>>>>>=20
>>>>>>> On 16.11.2016 =D0=B3., at 13:22, Aled Sage <aled.sage@gmail.com> =
wrote:
>>>>>>>>=20
>>>>>>>> Hi all,
>>>>>>>>=20
>>>>>>>> It's far past time that we did a Brooklyn 0.10.0 release! I =
suggest
>> we
>>>>>>>>=20
>>>>>>> aim for that soon.
>>>>>>>=20
>>>>>>>> To that end, I suggest the following steps:
>>>>>>>>=20
>>>>>>>> * Deal with open PRs:
>>>>>>>>    o People shout out about any PRs you think are very =
important to
>>>>>>>>      be merged, before that release.
>>>>>>>>    o Review open PRs
>>>>>>>>      (for any that won't get merged into 0.10.0, clearly mark =
them
>> as
>>>>>>>>      such and say why).
>>>>>>>> * Any pending/remaining work:
>>>>>>>>    o Give people until Friday evening (uk time) to submit any =
other
>>>>>>>>      very important PRs that are being working on.
>>>>>>>>    o People shout out about any known issues that they see as
>>>>>>>>      blockers for a release.
>>>>>>>> * Do some initial testing, using master (before Friday).
>>>>>>>> * Aim to produce a first release candidate on Friday evening =
(uk
>> time).
>>>>>>>> * Do the usual QA/fix cycle until the release is ready.
>>>>>>>> * Write release notes, etc.
>>>>>>>>=20
>>>>>>>> Of the first steps, reviewing the PRs is a big piece of work! =
If you
>>>>>>>>=20
>>>>>>> have time to help, then please lend a hand by reviewing and/or
>> testing
>>>>>>>=20
>>>>>> the
>>>>>>=20
>>>>>>> PRs, and commenting on them.
>>>>>>>=20
>>>>>>>> I don't think we should try to squeeze lots of additional PRs =
into
>>>>>>>>=20
>>>>>>> 0.10.0 - there is already a huge amount in there compared to =
0.9.0!
>>>>>>>=20
>>>>>>>> Richard, are our release process docs up-to-date at [1]?
>>>>>>>>=20
>>>>>>>> Aled
>>>>>>>>=20
>>>>>>>> [1] http://brooklyn.apache.org/developers/committers/release-
>>>>>>>>=20
>>>>>>> process/index.html
>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>=20
>>>>=20
>>=20
>>=20