All,
Our quarterly report to the board is due on Wednesday. I've drafted a
report below.
If there's no comments I'll submit this on Wednesday. If there are any
suggested changes then I will of course amend the report!
Thanks
Richard.
## Description:
- Apache Brooklyn Project is a software fr
Jose,
Thank you for your work on Apache Brooklyn and sharing your progress with
us. I'm not personally an expert with Cloud Foundry so I can't comment
directly on your work but you are in safe hands with Andrea :-)
There's two things that I would like to ask you (and Andrea) about. Firstly
is tha
Hi Mike,
Welcome to the Apache Brooklyn mailing list!
It does sound like something odd is happening with CloudStack and that
would be my first guess. However I'm not a CloudStack expert and I know
that CloudStack can be used in many different ways, so perhaps Brooklyn is
not setting it up in quit
All,
Our quarterly report to the board is due shortly. I've drafted a report
below.
As I'm on holiday next week I want to get this submitted before this week
is out, so please have comments ready by 16:00 UTC on Friday 4th November. If
there's no comments I'll submit as is. If there are any sugg
Hi all,
On 16 November 2016 at 11:22, Aled Sage wrote:
> Hi all,
>
> It's far past time that we did a Brooklyn 0.10.0 release! I suggest we aim
> for that soon.
>
Definitely agree - our last release was in April, so about seven months
ago. We certainly wouldn't want to wait any longer. It's not
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.
[1]
https://github.com/apache/brooklyn-dist/blob/master/release/make-release-artifacts.sh
On 17 November 2016 at 13:09, Aled Sage wrote:
> +1, sounds great - thanks A
on our committer list.
Please join me in welcoming them to the Apache Brooklyn committers group.
Richard Downer
PMC Chair, Apache Brooklyn
Svet,
There's a discussion going on elsewhere in ASF[1] about The JSON License[2]
- it was previously acceptable to ASF and was on the Category A list[3].
However, it's been realised that the decision to place it in Category A was
incorrect, and it has now been moved to Category X. This means that
Hi Jose,
This is challenging my memory somewhat, but I recall in the past that
jclouds had trouble with AWS security groups, because the AWS API would
report the security group as being "in use" and therefore undeletable, for
a considerable time after the VM using it was removed. So if there was a
Jose, all,
I'd like to thank Jose for his work developing PaaS entities for Apache
Brooklyn this last summer. For those who have not seen his work, please see
[1] for a summary and lots of links, and [2] for an example and demo video.
I'd like to consider the next steps for Jose's work, which is
Aled,
On 6 December 2016 at 11:20, Aled Sage wrote:
>
> *gpg: WARNING: This key is not certified with a trusted signature* Do we
> need to worry about that? Do I need to import more keys into my chain of
> trust?
> (Note that the script had previously executed `curl
> https://dist.apache.org/rep
+1
The host.address and host.subnet.address has always been confusing, at
least for me, and especially so for figuring out what SshMachineLocation is
going to do. Having a dedicated sensor for the management address with
unambiguous purpose for SshMachineLocation (and others!) seems obvious to
me!
+1
If there's another 0.10.0 release candidate, do we want to try and get that
"deprecated" tag in to 0.10.0?
Richard.
On 2 December 2016 at 21:16, Sam Corbett
wrote:
> I don't see much to disagree with here. The SetFromFlag annotation is an
> abstraction that might have made sense briefly bu
Geoff, all,
It's generally required that release artifacts have the LICENSE and NOTICE
files in the root. Artifacts that are machine-read like JARs and their ilk
can be excepted, but they should instead have those files in the most
appropriate place - META-INF for JARs.
So this would be a release
Hi Valentin,
That's great, but I see that you've given them a reference to 0.10.0-rc2.
We must not share release candidates outside this list. Please can you
"pause" this - if not possible then please remove it.
I'm appreciate what you're doing so I'm sorry to have to block this. Apart
from the f
Svet,
I've also just noticed that the Vagrant distribution is missing both
LICENSE and NOTICE.
Richard.
On 15 December 2016 at 10:52, Svetoslav Neykov <
svetoslav.ney...@cloudsoftcorp.com> wrote:
> The missing NOTES in some of our downloads is a release blocker so I am
> cancelling the vote.
>
Ok, I can reproduce this behaviour when trying to connect to a Brooklyn
instance on localhost.
*But...*
I've started up a new instance on AWS and I'm connecting to it on port
8081. A username and password is printed to the console on startup, and I
can use those credentials to access the web UI.
klyn is started
> for the first time.
>
> For 0.11.0, we re-visit the default Karaf configuration (which I believe
> will still require the auto-generated username + password (buried in the
> log), both for localhost and remote).
>
> Aled
>
> [1] https://lists.apache.org/thread
+1 (binding)
Downloads look good. Hashes and signatures check out.
LICENCE and NOTICE present in all artifacts.
Verified the ability to run the main Java app, and the standalone `br`
client, and deploy a moderately complex blueprint, using Ubuntu 16.04 LTS,
CentOS 6, CentOS 7.
Thanks for your wor
+1. In about a week I'll be drafting the last of our three initial
monthly reports to the board; I'd love to say that we have shed our
"incubating" repository tag!
Richard.
On 28 January 2016 at 10:09, Alex Heneveld
wrote:
>
> Brooklyners-
>
> TL;DR: *switch to new repos at the weekend, incubat
Hi Hadrian,
Just saw this (and another similar message) about removing old
releases from the download location.
Is there a reason for this? I expected that we should be keeping our
old releases for the historical record?
Thanks
Richard.
On 3 February 2016 at 04:20, wrote:
> Author: hadrian
>
To our more experienced Apache'ers:
https://github.com/apache/brooklyn-client/pull/1 adds the Brooklyn
CLI. This was developed in a non-Apache location starting last year,
with the bulk of development happening from November onwards. It has
>150 commits from 4 authors and is over 6,000 SLOC.
Give
All,
https://github.com/apache/brooklyn-client/pull/1 adds the Brooklyn
CLI. This allows a user to control and script Brooklyn from the
command line. It opens up many possibilities, including making the web
UI optional (reducing the security footprint in production
deployments), allowing admins to
+1 binding
Richard.
On 18 February 2016 at 15:25, Richard Downer wrote:
> All,
>
> https://github.com/apache/brooklyn-client/pull/1 adds the Brooklyn
> CLI. This allows a user to control and script Brooklyn from the
> command line. It opens up many possibilities, including maki
Hadrian, did you see my message from last week? [Changing subject line
in case it got lost in commit message noise]
Thanks
Richard.
On 18 February 2016 at 11:10, Richard Downer wrote:
> Hi Hadrian,
>
> Just saw this (and another similar message) about removing old
> releases from
ard,
> This issue contains the reasoning:
> https://issues.apache.org/jira/browse/BROOKLYN-220
>
> Svet.
>
>
>> On 24.02.2016 г., at 11:24, Richard Downer wrote:
>>
>> Hadrian, did you see my message from last week? [Changing subject line
>> in case it g
vote. (In fact, the vast majority
of votes were cast in the first few hours - making it probably the
most popular vote Brooklyn has ever held :-)
Richard.
-- Forwarded message ------
From: Richard Downer
Date: 18 February 2016 at 15:25
Subject: [VOTE] Accept contribution of
All,
Apologies I've not been keeping up with this. What's the status of our
CI builds on builds.apache.org?
- Are they appropriate for the new repo layout?
- Are they working properly?
- Are PRs also being built?
- Any other issues?
I believe there has been some activity but I've not seen it dis
All,
It's about time we had a new release of Apache Brooklyn - our first as
a graduated TLP. We have lots of great new features to share :-)
Is there anything that we know about that would block a release?
Are there any outstanding or imminent PRs that would be highly
desirable for a release?
I
st-090. Does anyone object to branching an 09x from which we can do a
> release and bumping master to 0.10.0-SNAPSHOT ?
>
> If no objection I will branch and bump the version tomorrow.
>
> And please ping me if I can help with a release.
>
> Best
> Alex
>
>
> On
at 13:20, Alex Heneveld
wrote:
>
> Richard-
>
> Nice. Will hang fire on that.
>
> --A
>
>
>
> On 29/03/2016 10:50, Richard Downer wrote:
>>
>> Hi Alex,
>>
>> No objection to you making branches just now, but if you could hold
>> off for a
Alex,
On 30 March 2016 at 11:33, Alex Heneveld
wrote:
> Richard, your instructions were great!
What can I say, I only want to be release manager once! ;-p
I'll spin up a release candidate now...
Richard.
This is to call for a vote for the release of Apache Brooklyn 0.9.0 [rc1].
This release comprises of a source code distribution, and a corresponding
binary distribution, RPM packages, Vagrant environment package, and
Maven artifacts.
The source and binary distributions, including signatures, dige
re
that a mistake does not ruin the experience for users.
So if you can spare an hour or more to download some of the artifacts
and try them out, then it will be *very* useful! The vote lasts for
three days so there's no need to rush to get a vote in.
Thanks!
Richard.
-- Forwarded messa
issue is resolved.
Richard.
-- Forwarded message --
From: Richard Downer
Date: 31 March 2016 at 14:16
Subject: [VOTE] Release Apache Brooklyn 0.9.0 [rc1]
To: Brooklyn dev
This is to call for a vote for the release of Apache Brooklyn 0.9.0 [rc1].
This release comprises of a
7;ve backported it -- and the improvement in #97 as suggested by @aledsage
> -- to the 0.9.0 branch.
>
> Fancy another RC?!
>
> Best
> Alex
>
>
>
> On 01/04/2016 15:26, Richard Downer wrote:
>>
>> The vote for rc1 is cancelled.
>>
>> This is due t
Great stuff. I'll kick off another release.
Richard.
On 1 April 2016 at 15:48, Alex Heneveld wrote:
>
> Yes. Good spot. Merged and backported.
>
> --A
>
>
>
> On 01/04/2016 15:31, Richard Downer wrote:
>>
>> Aled also recommended
>> https://g
This is to call for a vote for the release of Apache Brooklyn 0.9.0 [rc2].
This release comprises of a source code distribution, and a
corresponding binary distribution, RPM packages, Vagrant environment
package, and Maven artifacts.
The source and binary distributions, including signatures, dige
Hi Andrew,
You're right - failure to follow my own instructions. I've now pushed the tags.
Thanks
Richard.
On 2 April 2016 at 01:00, Andrew Kennedy
wrote:
> On Fri, 1 Apr 2016 at 16:58 Richard Downer wrote:
>
>> brooklyn: acc8ff1930d243d2a5fae1ad2f1a1ef17ca4a
pose? Can we relax this version requirement?
>>>
>>> Svet.
>>>
>>>
>>> > On 4.04.2016 г., at 13:14, Sam Corbett
>>> wrote:
>>> >
>>> > +1 binding
>>> >
>>> > I have:
>>> > * Verified releas
On 6 April 2016 at 17:17, Aled Sage wrote:
> I believe that Richard is discussing which Geoff about which brooklyn-client
> platform artifacts are required. Once that is agreed and sorted, then I
> think we are good to go.
I've checked Geoff's PR and it's nice and simple: Mac 64bit, Windows
and L
s low risk and
>> simple.
>>
>> Aled
>>
>>
>> On 06/04/2016 17:29, Sam Corbett wrote:
>>>
>>> If I've not missed the cutoff I'd like
>>> https://github.com/apache/brooklyn-server/pull/99 to be included.
>>>
>>> On
This is to call for a vote for the release of Apache Brooklyn 0.9.0 [rc3].
This release comprises of a source code distribution, and a
corresponding binary distribution, RPM packages, Vagrant environment
package, and Maven artifacts.
The source and binary distributions, including signatures, dige
This is to call for a vote for the release of Apache Brooklyn 0.9.0 [rc4].
This release comprises of a source code distribution, and a corresponding
binary distribution, RPM packages, Vagrant environment package, and Maven
artifacts.
The source and binary distributions, including signatures, dige
The vote for releasing Apache Brooklyn 0.9.0 [rc4] passed with 3 binding
+1s, 1 non-binding +1s, and no 0 or -1.
Vote thread link:
https://mail-archives.apache.org/mod_mbox/brooklyn-dev/201604.mbox/%3CCABQFKi2rBXoGSD5MoAbePJx71RD7KZZx1nbPO-sjuGk45HYvyA%40mail.gmail.com%3E
Binding +1s:
Andrea Turl
k as used elsewhere in the
> rebind manager.
>
> Sorry about this, but can we make another RC or is it too late...
>
> Andrew.
>
> On Tue, 12 Apr 2016 at 12:13 Richard Downer wrote:
>
> > The vote for releasing Apache Brooklyn 0.9.0 [rc4] passed with 3 binding
> >
cs/blob/master/guide/misc/release-notes.md
On 12 April 2016 at 12:13, Richard Downer wrote:
> The vote for releasing Apache Brooklyn 0.9.0 [rc4] passed with 3 binding
> +1s, 1 non-binding +1s, and no 0 or -1.
>
> Vote thread link:
>
> https://mail-archives.a
This will be related to a problem I had yesterday -
https://issues.apache.org/jira/browse/INFRA-11663
I've updated your ticket with a link.
Richard.
On 13 April 2016 at 12:46, Svetoslav Neykov <
svetoslav.ney...@cloudsoftcorp.com> wrote:
> Trying to merge PRs in Brooklyn's repos fails with an
The Apache Brooklyn team is proud to announce the latest release of Apache
Brooklyn 0.9.0.
Apache Brooklyn is a framework for modelling, deploying and managing
applications through autonomic blueprints. More details on Apache Brooklyn
can be found at http://brooklyn.apache.org/
Version 0.9.0 is o
Hi Aled,
What did you use as the base for the branch? The
`rel/apache-brooklyn-0.9.0` tag or something else?
Richard.
On 26 April 2016 at 13:17, Aled Sage wrote:
> Hi all,
>
> I've created a 0.9.x branch (at version 0.9.1-SNAPSHOT) for fixes that
> we'd want in a 0.9.1 release. I don't think t
All,
Below is a draft for our next board report, which needs to be submitted by
Wednesday 11th May. If you have any comments please let me know; otherwise
I'll go for passive consensus.
---
## Description:
- Apache Brooklyn Project is a software framework for modeling,
monitoring and managin
All,
If you have made a PR against brooklyn-docs which is to fix an issue in the
0.9.0 documentation - and you need it to be visible in the "/v/latest" docs
- please could you re-submit your PR against branch `0.9.0`.
Here are the PRs that may be affected - if this is yours, please could you
chec
https://www.linux.com/news/rise-six-unsung-apache-big-data-projects
Richard.
>
>
>
>
> On 10/05/2016 17:12, Richard Downer wrote:
>
>> All,
>>
>> If you have made a PR against brooklyn-docs which is to fix an issue in
>> the
>> 0.9.0 documentation - and you need it to be visible in the "/v/latest"
>> docs
>&g
tbouron]
>>>> #56 [neykov]
>>>>
>>>> --a
>>>>
>>>>
>>>>
>>>> On 13/05/2016 12:07, Svetoslav Neykov wrote:
>>>>
>>>> Same for #56 [neykov]
>>>>>
>>>>> Svet.
>>
I'm not sure I'm happy with the idea of many 3rd-party jars adding stuff
into a Brooklyn-owned package. It doesn't rule out a couple of 3rd-party
packages happening to choose the same name. I also think there might be
issues with OSGi, as OSGi requires explicit declaration of packages, but I
don't
A reminder for contributors:
If you are updating the user guide (files under the `guide` folder, as
opposed to `website`), and you would like your changes also applied to the
current published `/v/latest` guide, please make an additional PR on the
`0.9.0` branch.
Alternatively, in your `master` P
Hi all,
Catching up on this. As John mentioned I chipped in to the discussion on
Gitter before I saw this thread.
I'm "+1" on `apache-brooklyn-cli`, and -1 on *anything* that is not
prefixed `apache-brooklyn-`.
The reason for this is, with my PMC hat on, I am responsible for making
sure that our
then I do not
think that it is worth creating the package at all. I do not want our
documentation to be constantly saying things like "Type `br this-and-that`,
unless you are using Brew".
Richard.
On 23 May 2016 at 10:08, Richard Downer wrote:
> Hi all,
>
> Catching
then add it to our release process.
Richard.
On 23 May 2016 at 10:17, John McCabe wrote:
> @richard kicked it off myself at the weekend as I was installing br and
> figured I'd take a look at whats involved in getting it added to brew.
>
> re: metadata/attribution etc, what do you prop
John,
On 23 May 2016 at 10:34, John McCabe wrote:
> Naming of the package within Brew *only*, it does not impact the resulting
> binary naming at all:
>
> # brew install apache-brooklyn-cli
> # br login http://localhost:8081
Excellent - my concerns were misplaced :-)
> *Maintainers:*
> Brew
On 23 May 2016 at 10:51, Aled Sage wrote:
> +1, thanks John!
>
> Richard: it will be great to update the brooklyn docs to point people at
> `brew install apache-brooklyn-cli`. How do we officially endorse this so we
> can update the docs (once John's Homebrew PR is merged)?
I'm happy for the do
After a discussion with colleagues, it was established that they had
hipster beards and used Homebrew. I don't have a suitably hipster beard so
I can't use Homebrew - instead I use MacPorts, as appropriate for a
2000s-style stubble-beard owner. I did consider growing my beard out, but
at my age, th
Hi Martin,
This mailing list strips attachments off mails, so your attached diagram
didn't reach the list. Could you post a link to it instead?
Thanks
Richard.
On 21 June 2016 at 13:37, Martin Harris
wrote:
> Hi Folks,
>
> We've been making some additions to the Brooklyn documentation [here](
Duncan,
Do we have any data on what our users are using? That should be our driver
for change :-)
I am a bit concerned what effect making this change would have on existing
blueprints that don't specify an OS requirement. If a user writes such a
blueprint and makes it Ubuntu-dependent, would a de
Hi all,
Do we have any projects that we'd like to put forward for GSoC 2017?
Apache has the structure and processes in place for GSoC so all we need to
do is come up with ideas!
The deadline for a list of ideas is Thursday (apologies for the short
notice, due to illness I've been away and only j
CVE-2016-8744: Apache Brooklyn, SnakeYAML configuration potentially allows
remote code execution
Severity: Major
Vendor:
The Apache Software Foundation
Versions Affected:
Apache Brooklyn 0.9.0 and all prior versions
Description:
Apache Brooklyn uses the SnakeYAML library for parsing YAML inputs
CVE-2016-8737: Cross-site request forgery vulnerability in Apache Brooklyn
Severity: Major
Vendor:
The Apache Software Foundation
Versions Affected:
Apache Brooklyn 0.9.0 and all prior versions
Description:
Apache Brooklyn's REST server is vulnerable to cross-site request forgery
(CSRF), which
CVE-2017-3165: Cross-site vulnerabilities in Apache Brooklyn
Severity: Major
Vendor:
The Apache Software Foundation
Versions Affected:
Apache Brooklyn 0.9.0 and all prior versions
Description:
Apache Brooklyn's REST server is vulnerable to cross-site scripting where
one authenticated user can c
Hi Rupinder,
A few months back on an unrelated project I had a similar problem and it
was caused by a bug in Vagrant on Windows. I can't remember the details and
I'm on the road at the moment so I can't look it up, but it may be worth
searching Google for the error message. When I'm back in the of
Hi Geoff,
Unless the situation has moved on while I've not been paying attention, the
integration tests have always been a mixed bag, with several failures some
of which are nondeterministic[1], so I wouldn't worry too much about those.
I'd suggest you subscribe to the "bui...@apache.org" list wh
On 9 March 2017 at 10:39, Alasdair Hodge
wrote:
> I think we've deferred creating the .x branch until we suspect a patch
> release is on the cards, but I'd suggest we do it as a matter of course
> whenever we cut a release.
+1 - I agree with this. I think our contributors should be able open PR
Hi Aled,
I'm happy to volunteer to by RM on this one.
I'm keen to firm up our release process to make it as optimal as possible
whilst still being The Apache Way, so I'll use this as an opportunity to
draft up a wider-ranging release policy. After this release we can then
discuss how the release
All,
As suggested yesterday, a release has been started.
`master` has been bumped to 0.12.0-SNAPSHOT, where development can continue
as normal.
`0.11.x` is the release branch where 0.11.0 will be made. Please do not
make any commits to this branch without consulting the RM (me).
This applies to
This is to call for a vote for the release of Apache Brooklyn 0.11.0.
This release comprises of a source code distribution, and a corresponding
binary distribution, and Maven artifacts.
The source and binary distributions, including signatures, digests, etc. can
be found at:
https://dist.apach
Please use this thread for discussions about the 0.11.0 [rc1] release
(please keep the actual vote thread just for votes).
Thanks!
With the discovery of a release-blocking bug [1], this vote is cancelled.
RC2 will be forthcoming.
[1] https://issues.apache.org/jira/browse/BROOKLYN-473
<https://issues.apache.org/jira/browse/BROOKLYN-473>
On 12 April 2017 at 13:12, Richard Downer wrote:
> This is to call for a
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 me
n 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
>>>
>>
Please use this thread for discussions about the 0.11.0 [rc2] release
(please keep the actual vote thread just for votes).
Thanks!
This is to call for a vote for the release of Apache Brooklyn 0.11.0.
This release comprises of a source code distribution, and a corresponding
binary distribution, and Maven artifacts.
The source and binary distributions, including signatures, digests, etc. can
be found at:
https://dist.apach
Hi,
Yes there are some big improvements possible in this area.
As someone who has taken a bit of a back seat in using Apache Brooklyn for
a while and has recently restarted actively developing blueprints, I've
found that Brooklyn's features in this area have much improved over the
last year or tw
All,
There was a meeting on IRC earlier today to discuss ideas for overhauling
the website. I wasn't able to join for the whole meeting but I did leave my
IRC client running to capture the meeting. In line with the principle that
all discussions which lead to decisions must sooner or later be disc
operations
- Verified some simple-to-moderately-complex blueprints deploying to AWS
On 18 April 2017 at 17:09, Richard Downer wrote:
> This is to call for a vote for the release of Apache Brooklyn 0.11.0.
>
> This release comprises of a source code distribution, and a corresponding
is possible to
workaround the bug with a handcrafted bundle that clones the buggy code
plus a fix into a new package.
Personally I'd call this a release blocker.
What do others think?
Thanks
Richard.
On 18 April 2017 at 17:09, Richard Downer wrote:
> Please use this thread for disc
Hi all,
I'm using DynamicRegionFabric, and *within* a region I have two entities
where the first depends on the sensor of the second (web app depending on a
database). Normally I'd use an `id` field on the database entity and then
`$brooklyn:entity("otherid")` in a config key on the web app entity
> Geoff
>
> [1] https://issues.apache.org/jira/browse/BROOKLYN-493
>
>
> On Wed, 26 Apr 2017 at 09:06 Andrea Turli
> wrote:
>
> > +1 Richard,
> >
> > I personally consider any rebinding issues a release blocker.
> >
> > Sorry for not having s
I'll do a bit of digging. It seems that sometimes attachments do come
through to the list but sometimes do not, so I'm not entirely sure what is
happening with MIME type emails.
It is entirely possible that when Infra set up the JIRA mirroring to the
list they made the choice to send plain-text-on
That would appear to be specific to the Apache httpd project. That's the
project that's been around the longest and seen all the Browser wars and
the HTML incompatibilities that went on, and with the longest-running
community, so it's not surprising that they would make that request.
However I wou
Hi Thomas,
Just got confirmation from Infra that HTML is stripped for all mailing
lists, so it's not an option unfortunately.
There may be alternatives. So are you able to receive HTML emails for
Apache's JIRA direct to your own email address - it's just the ones on the
ML? If so it may be possib
Good spot. I've opened a JIRA ticket to infra: INFRA-14061.
I suspect that page is dodgy as 2 days later it's still showing 119 emails
today, when in fact we've had single-digit numbers of emails over the
weekend (a long weekend thanks to a public holiday in several countries).
Richard.
On 29 Ap
Hi all,
In my blueprint, I have a group of MariaDBs, and I want to get the host.name
of one entity in the group. The group exposes a sensor
`cluster.first.entity`, so I want to get that entity, and then get its
sensor `host.name`.
Here's a fragment of my blueprint where I try to do this (reduced
ard,
> Have you tried entity instead of component ... I had a similar blueprint a
> few weeks ago and I think that's how I solved it, but I'm nowhere near my
> laptop at the minute to verify so YMMV.
>
> M
>
> On Mon, 1 May 2017, 15:26 Richard Downer, wrote:
>
> &
f
>
>
>
>
> On Fri, 28 Apr 2017 at 09:09 Geoff Macartney <
> geoff.macart...@cloudsoftcorp.com> wrote:
>
> > Sounds good to me
> >
> >
> >
> > On Thu, 27 Apr 2017 at 21:34 Richard Downer wrote:
> >
> >> It is a tricky thing to come
All,
Due to discovery of a blocker bug in this rc - BROOKLYN-493 - the vote is
cancelled.
A new rc will be forthcoming.
Richard.
On 18 April 2017 at 17:09, Richard Downer wrote:
> This is to call for a vote for the release of Apache Brooklyn 0.11.0.
>
> This release comprises of
All,
What patches need to be added to the release branch for the 0.11.0-rc3
release?
BROOKLYN-493 is our blocker bug, so
https://github.com/apache/brooklyn-server/pull/654 at a minimum.
All there any other patches necessary?
I'd rather make it essential changes only - no "but this one would be
All,
A lot of very good points going on here - thank you to everyone who has
contributed to this conversation. It's clear that we are doing a disservice
to our contributors and things need to change. We need to be merging (or,
rarely, rejecting) PRs consistently and promptly. Obviously, difficulty
the PMC.
Please join me in welcoming Mark!
Richard Downer
Chair, Apache Brooklyn PMC
[1] PMC is the Project Management Committee. A project management committee
(PMC) is a committee of the Apache Software Foundation charged with
responsibility and governance for their top level project. The PMC
")[:500]
> > > for pr in first500PRs:
> > > print pr.title, "**", pr.additions, "**", pr.deletions
> >
> > *) I only looked at additions. There may be different results for
> > additions-subtractions (to get rid of any moved files t
+1 (binding)
On 8 May 2017 at 11:55, Richard Downer wrote:
> There have been recent discussions about how the committers assess PRs for
> merging. The discussion is summarised below and the original thread
> available at [1].
>
> The consensus of the discussion is to adopt ne
1 - 100 of 239 matches
Mail list logo
