You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by Aled Sage <al...@gmail.com> on 2015/06/16 11:00:53 UTC
Plan for releasing Brooklyn 0.7.0?
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
Re: Plan for releasing Brooklyn 0.7.0?
Posted by Alasdair Hodge <al...@cloudsoftcorp.com>.
Existing hashes will (almost certainly) break, and will need to be
regenerated; I warned about this in a previous email to this list:
12-Jun, "Re: [GitHub] incubator-brooklyn pull request: Tweak
PasswordHasher".
Alex has suggested a potential mitigation (implementing *both* schemes),
which although super-ugly would provide users with a transition period
during which logins are permitted via the old hashes. I'm not in favour
of this, but I could be persuaded if it would benefit a large number of
users.
A.
--
Alasdair Hodge
Principal Engineer,
Cloudsoft Corporation
On 22/06/2015 00:46, Andrew Kennedy wrote:
> Hi, Sam.
>
> An important thing to note in the release notes is the effect of
> https://github.com/apache/incubator-brooklyn/pull/687
>
> This seems to mean hashed passwords in brooklyn.properties need to be
> re-generated, for example I am no longer able to log in as users that have
> hashed passwords, even though these worked previously. Please feel free to
> test, though, in case I am mistaken... See my comment about providing an
> upgrade tool, although I am unsure if this is even possible, now that I
> think about it, because hash functions.
>
> Andrew.
>
> On Tue, 16 Jun 2015 at 02:54 Sam Corbett <sa...@cloudsoftcorp.com>
> wrote:
>
>> I am happy to take care of writing release notes.
>>
>>
>> On 16/06/2015 10:10, Richard Downer 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 <al...@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.
Re: Plan for releasing Brooklyn 0.7.0?
Posted by Andrew Kennedy <an...@cloudsoftcorp.com>.
Hi, Sam.
An important thing to note in the release notes is the effect of
https://github.com/apache/incubator-brooklyn/pull/687
This seems to mean hashed passwords in brooklyn.properties need to be
re-generated, for example I am no longer able to log in as users that have
hashed passwords, even though these worked previously. Please feel free to
test, though, in case I am mistaken... See my comment about providing an
upgrade tool, although I am unsure if this is even possible, now that I
think about it, because hash functions.
Andrew.
On Tue, 16 Jun 2015 at 02:54 Sam Corbett <sa...@cloudsoftcorp.com>
wrote:
> I am happy to take care of writing release notes.
>
>
> On 16/06/2015 10:10, Richard Downer 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 <al...@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.
Re: Plan for releasing Brooklyn 0.7.0?
Posted by Sam Corbett <sa...@cloudsoftcorp.com>.
I am happy to take care of writing release notes.
On 16/06/2015 10:10, Richard Downer 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 <al...@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.
Re: Plan for releasing Brooklyn 0.7.0?
Posted by Aled Sage <al...@gmail.com>.
Hi all,
First, thanks to the various folk fixing the test failures!
---
Looking at [1], and looking at the VM, it ran out of disk space. That
might well explain some of the later failures (and why it stalled!).
---
It also failed to `curl` the MySql install artifact. It doesn't report
out of disk space in stdout/stderr, so that might be another error. This
would most likely explain a number of the other test failures as well (?).
2015-06-17 17:54:56,136 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] % Total % Received %
Xferd Average Speed Time Time Time Current
2015-06-17 17:54:56,136 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] Dload Upload Total
Spent Left Speed
2015-06-17 17:54:56,136 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] 0 0 0 0 0
0 0 0 --:--:-- --:--:-- --:--:-- 0
2015-06-17 17:54:56,136 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] 0 0 0 0 0
0 0 0 --:--:-- --:--:-- --:--:-- 0
2015-06-17 17:54:56,136 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] 100 185 100 185 0
0 656 0 --:--:-- --:--:-- --:--:-- 656
2015-06-17 17:54:56,136 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] 0 175M 0 1374k 0
0 3992k 0 0:00:45 --:--:-- 0:00:45 3992k
2015-06-17 17:54:56,136 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] curl: (23) Failed writing
body (632 != 11584)
2015-06-17 17:54:56,136 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] % Total % Received %
Xferd Average Speed Time Time Time Current
2015-06-17 17:54:56,137 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] Dload Upload Total
Spent Left Speed
2015-06-17 17:54:57,137 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] 0 0 0 0 0
0 0 0 --:--:-- --:--:-- --:--:-- 0
2015-06-17 17:54:57,568 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] 0 175M 0 430k 0
0 596k 0 0:05:02 --:--:-- 0:05:02 596k
2015-06-17 17:54:57,568 DEBUG brooklyn.SSH [Thread-3]:
[rPtjs01p@LocalhostMachine:qvhX:stdout] Could not retrieve
mysql-5.5.37-linux2.6-x86_64.tar.gz. Tried:
file://$HOME/.brooklyn/repository/MySqlNode/5.5.37/mysql-5.5.37-linux2.6-x86_64.tar.gz,
http://dev.mysql.com/get/Downloads/MySQL-5.5/mysql-5.5.37-linux2.6-x86_64.tar.gz/from/http://www.mirrorservice.org/sites/ftp.mysql.com/,
http://downloads.cloudsoftcorp.com/brooklyn/repository/MySqlNode/5.5.37/mysql-5.5.37-linux2.6-x86_64.tar.gz
2015-06-17 17:54:57,568 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] 0 175M 0 1370k 0
0 902k 0 0:03:19 0:00:01 0:03:18 903k
2015-06-17 17:54:57,568 DEBUG brooklyn.SSH [Thread-3]:
[rPtjs01p@LocalhostMachine:qvhX:stdout] Executed
/tmp/brooklyn-20150617-175418439-VOCb-installing_MySqlNodeImpl_id_rP.sh,
result 9
2015-06-17 17:54:57,568 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] curl: (23) Failed writing
body (5773 != 16384)
2015-06-17 17:54:57,569 DEBUG brooklyn.SSH [Thread-4]:
[rPtjs01p@LocalhostMachine:qvhX:stderr] Could not retrieve
mysql-5.5.37-linux2.6-x86_64.tar.gz. Tried:
file://$HOME/.brooklyn/repository/MySqlNode/5.5.37/mysql-5.5.37-linux2.6-x86_64.tar.gz,
http://dev.mysql.com/get/Downloads/MySQL-5.5/mysql-5.5.37-linux2.6-x86_64.tar.gz/from/http://www.mirrorservice.org/sites/ftp.mysql.com/,
http://downloads.cloudsoftcorp.com/brooklyn/repository/MySqlNode/5.5.37/mysql-5.5.37-linux2.6-x86_64.tar.gz
2015-06-17 17:54:57,569 DEBUG brooklyn.SSH
[brooklyn-execmanager-e0aCviYo-9]: installing
MySqlNodeImpl{id=rPtjs01p}, on machine
SshMachineLocation[LocalhostMachine:qvhX:ip-10-89-25-183/10.89.25.183:22@qvhXout7],
completed: return status 9
Here is an example of one of the curl commands we ran:
curl -f -L -k --retry 10 --keepalive-time 30 --speed-time 30
"http://downloads.cloudsoftcorp.com/brooklyn/repository/MySqlNode/5.5.37/mysql-5.5.37-linux2.6-x86_64.tar.gz"
-o mysql-5.5.37-linux2.6-x86_64.tar.gz
Aled
[1]
http://brooklyn.builds.cloudsoftcorp.com/job/Brooklyn-Master-Integration/399/
On 18/06/2015 13:19, Aled Sage wrote:
> Hi all,
>
> Initial results from running our integration tests is at [1].
>
> I've added the failures, to track status of each and who is fixing
> them, in:
> https://docs.google.com/spreadsheets/d/19HZeXQATey1tMWC-Lahg9PPhjborEeHS7L0VzlvS_Wk/edit?usp=sharing
>
>
> Aled
>
> p.s. if you want write-access to the doc, please send me the e-mail
> address at which you'd like an invite to access it.
>
> [1]
> http://brooklyn.builds.cloudsoftcorp.com/job/Brooklyn-Master-Integration/399/
>
>
> On 16/06/2015 17:43, Yavor Yanchev wrote:
>> PR #642 is regarding the work in progress for Hazelcast support. Last
>> push was made 5 days ago.
>> It only adds/changes sandbox files and nothing outside of the sandbox
>> module.
>>
>>
>> On 06/16/2015 07:17 PM, Mike Zaccardo wrote:
>>> 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 <ri...@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 <al...@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.
>>>>>
>>
>>
>
Re: Plan for releasing Brooklyn 0.7.0?
Posted by Aled Sage <al...@gmail.com>.
Hi all,
Initial results from running our integration tests is at [1].
I've added the failures, to track status of each and who is fixing them, in:
https://docs.google.com/spreadsheets/d/19HZeXQATey1tMWC-Lahg9PPhjborEeHS7L0VzlvS_Wk/edit?usp=sharing
Aled
p.s. if you want write-access to the doc, please send me the e-mail
address at which you'd like an invite to access it.
[1]
http://brooklyn.builds.cloudsoftcorp.com/job/Brooklyn-Master-Integration/399/
On 16/06/2015 17:43, Yavor Yanchev wrote:
> PR #642 is regarding the work in progress for Hazelcast support. Last
> push was made 5 days ago.
> It only adds/changes sandbox files and nothing outside of the sandbox
> module.
>
>
> On 06/16/2015 07:17 PM, Mike Zaccardo wrote:
>> 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 <ri...@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 <al...@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.
>>>>
>
>
Re: Plan for releasing Brooklyn 0.7.0?
Posted by Yavor Yanchev <ya...@yanchev.com>.
PR #642 is regarding the work in progress for Hazelcast support. Last
push was made 5 days ago.
It only adds/changes sandbox files and nothing outside of the sandbox
module.
On 06/16/2015 07:17 PM, Mike Zaccardo wrote:
> 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 <ri...@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 <al...@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.
>>>
Re: Plan for releasing Brooklyn 0.7.0?
Posted by Mike Zaccardo <mi...@cloudsoftcorp.com>.
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 <ri...@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 <al...@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.
Re: Plan for releasing Brooklyn 0.7.0?
Posted by Mike Zaccardo <mi...@cloudsoftcorp.com>.
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 <ri...@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 <al...@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.
Re: Plan for releasing Brooklyn 0.7.0?
Posted by Svetoslav Neykov <sv...@cloudsoftcorp.com>.
I can work on getting failing tests back in order.
Svet.
> On 16.06.2015 г., at 12:10, Richard Downer <ri...@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 <al...@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.
Re: Plan for releasing Brooklyn 0.7.0?
Posted by Richard Downer <ri...@apache.org>.
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 <al...@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
>
>
Re: Plan for releasing Brooklyn 0.7.0?
Posted by Alex Heneveld <al...@cloudsoftcorp.com>.
+1
Best
Alex
On 16/06/2015 10:00, Aled Sage 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.