On 01/16/2012 07:15 PM, Franklin, Matthew B. wrote:
On 1/16/12 12:42 PM, "Ate Douma"<[email protected]> wrote:
On 01/16/2012 04:30 PM, Franklin, Matthew B. wrote:
On 1/13/12 9:13 AM, "Franklin, Matthew B."<[email protected]> wrote:
Ant brought up that our NOTICE file looks like it has extraneous
attributions in it. According to discussions on the general list held
in
the last few months, we only need to put an attribution in the NOTICE
file IFF there is a provision in the license that you must do so.
Unless
our mentors disagree that this is the case (or someone has
independently
verified that all of our current attributions are required), I will
create a JIRA ticket to clean this up for 0.8-incubating.
Ate, I saw that you responded to Ant on the incubator list. Do you
think
that we need to review the NOTICE file for the binary releases or are we
all set?
I haven't gotten a response back on that from ant elder.
As I've been missing out on some of these discussions on the
general@incubator
I'll try to scan the mail archive and find out myself what he might be
indicating.
Although we might have notices for 3rd party projects who do not require
to be
mentioned in the NOTICE file (which I get from your interpretation, not
ant
email), even if that is the case, I can't see why that would be 'bad',
except
maybe more than needed. It definitely doesn't look to me as a 'blocker'
for a
release. But maybe there is more to it, which I still have to determine
though.
It surely is (even) more work to determine but doable of course.
If you have concrete pointers to what ant is indicating, let me know!
I dug through the incubator e-mail archives looking for the discussions
around this topic, but did not keep my results. The discussions came
about during the first Kafka release. The closest thing I could find to a
consensus was a couple of e-mails where a individuals indicated a
preference for adding attributions only for software where the license or
copyright notice requires it.
I found those myself too. I think its more than (just) individuals with
preferences though. I think I kind of understand the argument now (see also my
forwarded email from general@ on the response from ant elder).
Whether this is the policy of Apache is unclear in the research I did, but
I am no lawyer.
That part is still a bit unclear, and getting the exact or at least concrete and
practical rules 'codified' always is tricky.
But I think I agree we need to recheck our NOTICE file to determine if it can
and need further cleanup.
So for that I will create a new JIRA ticket and get it resolved before the next
0.8 release candidate
Ate
Otherwise, I'll come back on this as soon as I find out more, but I'm
currently
out of office in Berlin until Thursday, so with limited time.
Until then I wouldn't worry about this yet or create a JIRA ticket for it
until
we know what exactly should be cleaned up in the first place.
Ate
-Matt
-----Original Message-----
From: ant elder [mailto:[email protected]]
Sent: Friday, January 13, 2012 3:53 AM
To: [email protected]
Subject: Re: [1 IPMC VOTE NEEDED] [VOTE] Release Apache Rave 0.6-
incubating
I've had a look, the only issue i see is I don't think the NOTICE file
in the binary distribution is correct as it has many things which i
expect are not required. When we last discussed this on general@ we
said this is not strictly a blocking problem, so
+1
but i think you should do a complete review of whats in the NOTICE
file with your mentors and remove everything which doesn't need to be
there.
...ant
On Thu, Jan 12, 2012 at 2:16 PM, Franklin, Matthew B.
<[email protected]> wrote:
We still need to get one more IPMC vote to close this vote. If
someone
could take a look, it would be greatly appreciated.
-Matt
-----Original Message-----
From: Franklin, Matthew B. [mailto:[email protected]]
Sent: Wednesday, January 11, 2012 8:03 AM
To: [email protected]
Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
-----Original Message-----
From: Franklin, Matthew B. [mailto:[email protected]]
Sent: Monday, January 09, 2012 8:45 AM
To: [email protected]
Cc: [email protected]
Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
-----Original Message-----
From: sebb [mailto:[email protected]]
Sent: Monday, January 09, 2012 8:21 AM
To: [email protected]
Subject: Re: [VOTE] Release Apache Rave 0.6-incubating
On 9 January 2012 13:09, Franklin, Matthew B.<[email protected]>
wrote:
Does my answer below suffice? It would be nice to close this
vote out
one
way or another....
The answer describes what happened.
However, it does not fix the problem, which is that the end-user
sees
a file with conflicting information.
Thanks. This is what I was looking for, so that we can have the
discussion
as
to
whether or not to cancel the release (we won't do a re-release).
Not a blocker, but you may find it takes less time overall to fix
the
issue before release rather than dealing with user queries
afterwards.
It may also lessen confidence in the release: if there is such an
obvious error, what other errors are lurking?
While I agree that it doesn't look great, the CHANGELOG is
distributed
with
the source release and is probably not viewed as much as the
release
notes
sent out with the announcement (which will be the JIRA list I
linked). I will
take this back to our dev list, but if they don't see it as a
blocker, would
you
be
comfortable voting +1?
The community was presented with the issue and via lazy consensus
agreed
to move forward with the release, even though the CHANGELOG file is
incorrect. We still need 1 final IPMC vote to release.
[ Community discussion on proceeding:
http://markmail.org/message/tp5nyqh24tdpybw6 ]
-----Original Message-----
From: Franklin, Matthew B. [mailto:[email protected]]
Sent: Tuesday, January 03, 2012 12:19 PM
To: [email protected]
Subject: RE: [VOTE] Release Apache Rave 0.6-incubating
-----Original Message-----
From: sebb [mailto:[email protected]]
Sent: Tuesday, January 03, 2012 7:06 AM
To: [email protected]
Subject: Re: [VOTE] Release Apache Rave 0.6-incubating
On 28 December 2011 19:15, Franklin, Matthew B.
<[email protected]>
wrote:
This is the fifth incubator release for Apache Rave, with the
artifacts
being
versioned as 0.6-incubating.
We are requesting at least one additional IPMC member vote, as
we
have
received 2 binding IPMC +1 votes during the release voting on
rave-
dev
-
VOTE: http://s.apache.org/Czr
RESULT: http://s.apache.org/yIQ
IPMC member votes from the rave-dev list:
Ate Douma: +1
Ross Gardler: +1
Release notes:
http://svn.apache.org/repos/asf/incubator/rave/tags/0.6-
incubating/CHANGELOG
Apparently, I didn't commit back the CHANGELOG for 0.6 . Here
is
the
issue
list from JIRA
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=
12
31
1
2
90
&version=12317563
which says:
Release Notes - Rave - Version 0.5-INCUBATING
So what was changed for 0.6?
SVN source tag (r1208867):
https://svn.apache.org/repos/asf/incubator/rave/tags/0.6-
incubating/
Maven staging repos:
https://repository.apache.org/content/repositories/orgapacherave-
278/
https://repository.apache.org/content/repositories/orgapacherave-
279/
Source release:
https://repository.apache.org/content/repositories/orgapacherave-
278/org/apache/rave/rave-project/0.6-incubating/rave-project-0.6
-
incubating-source-release.zip
Binary releases
http://people.apache.org/builds/incubator/rave/0.6-
incubating/apache-
rave-0.6-incubating-bin.tar.gz
http://people.apache.org/builds/incubator/rave/0.6-
incubating/apache-
rave-0.6-incubating-bin.zip
PGP release keys:
https://svn.apache.org/repos/asf/incubator/rave/KEYS
Vote open for 72 hours.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)
---------------------------------------------------------------
--
----
To unsubscribe, e-mail: general-
[email protected]
For additional commands, e-mail: general-
[email protected]
----------------------------------------------------------------
--
---
To unsubscribe, e-mail:
[email protected]
For additional commands, e-mail: general-
[email protected]
-----------------------------------------------------------------
--
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail:
[email protected]
------------------------------------------------------------------
--
-
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail:
[email protected]
-------------------------------------------------------------------
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
