brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Zaccardo <mike.zacca...@cloudsoftcorp.com>
Subject Re: Plan for releasing Brooklyn 0.7.0?
Date Tue, 16 Jun 2015 16:17:41 GMT
Are we looking to merge PRs from #642 and earlier?  There is a large gap in
time between #642 and the next open PR.

On Tue, Jun 16, 2015 at 10:08 AM, Mike Zaccardo <
mike.zaccardo@cloudsoftcorp.com> wrote:

> I will review the PRs and can take on tasks that previous volunteers need
> help with.
> On Jun 16, 2015 7:15 AM, "Svetoslav Neykov" <
> svetoslav.neykov@cloudsoftcorp.com> wrote:
>
>> I can work on getting failing tests back in order.
>>
>> Svet.
>>
>>
>> > On 16.06.2015 г., at 12:10, Richard Downer <richard@apache.org> wrote:
>> >
>> > I'm happy to be RM for this release - I have notes from the last time
>> which
>> > I have been writing up to make a release process document, so this will
>> be
>> > a good opportunity for me to get those docs up to a good standard and
>> > published. (For the following release I'd then propose that someone
>> else is
>> > RM and attempts to follow what I've documented.)
>> >
>> > I would however like to delegate the task of writing the release notes.
>> Any
>> > volunteers?
>> >
>> > Richard.
>> >
>> >
>> > On Tue, 16 Jun 2015 at 10:01 Aled Sage <aled.sage@gmail.com> wrote:
>> >
>> >> Hi all,
>> >>
>> >> I propose we aim for a 0.7.0 very soon. There is a huge amount of new
>> >> material, both since 0.7.0-M2 and since 0.6.0! I see no reason to delay
>> >> for any other features.
>> >>
>> >> I suggest the following timetable:
>> >>
>> >>  * By end of day Friday 19th, all pull requests for 0.7.0 are submitted
>> >>    and merged.
>> >>    Switch master to 0.8.0-SNAPSHOT; release/fixes continue on 0.8.x
>> >> branch.
>> >>  * By end of Sunday 21st, have done QA on master (and then on 0.8.x,
>> >>    after that branch is created). Some manual, and also running +
>> >>    looking at the integration and live tests. We should fix and/or
>> >>    triage as appropriate.
>> >>  * On Monday 22nd, produce a 0.7.0 release candidate.
>> >>  * Community vote, and seek +1 from mentors (minimum 3 days, though
>> >>    longer if community/mentors report problems).
>> >>  * Vote on incubator-general (minimum 3 days, though longer if problems
>> >>    are reported).
>> >>
>> >> This will be our first Apache binary release (the 0.7.0-M2 release was
>> a
>> >> source-only release).
>> >>
>> >> ---
>> >> Volunteers please to review PRs, and to investigate any failures in
>> >> integration + live tests.
>> >>
>> >> Aled
>> >>
>> >>
>>
>>
>> --
>> Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
>>  Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
>>
>> This e-mail message is confidential and for use by the addressee only. If
>> the message is received by anyone other than the addressee, please return
>> the message to the sender by replying to it and then delete the message
>> from your computer. Internet e-mails are not necessarily secure. Cloudsoft
>> Corporation Limited does not accept responsibility for changes made to
>> this
>> message after it was sent.
>>
>> Whilst all reasonable care has been taken to avoid the transmission of
>> viruses, it is the responsibility of the recipient to ensure that the
>> onward transmission, opening or use of this message and any attachments
>> will not adversely affect its systems or data. No responsibility is
>> accepted by Cloudsoft Corporation Limited in this regard and the recipient
>> should carry out such virus and other checks as it considers appropriate.
>>
>

-- 
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230. 
 Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
 
This e-mail message is confidential and for use by the addressee only. If 
the message is received by anyone other than the addressee, please return 
the message to the sender by replying to it and then delete the message 
from your computer. Internet e-mails are not necessarily secure. Cloudsoft 
Corporation Limited does not accept responsibility for changes made to this 
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of 
viruses, it is the responsibility of the recipient to ensure that the 
onward transmission, opening or use of this message and any attachments 
will not adversely affect its systems or data. No responsibility is 
accepted by Cloudsoft Corporation Limited in this regard and the recipient 
should carry out such virus and other checks as it considers appropriate.

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