-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Since we are already trying to get 0.7-incubating released, I don't have a problem with this plan. But for future reference, how hard is it to update these small release issues? Would you need to call a new vote and get +1's from mentors again?
Marlon On 1/9/12 9:53 AM, Franklin, Matthew B. wrote: > As you can see, Sebb found an issue with the release. I didn't > commit back my changes to the CHANGELOG file for 0.6. This means > that if we go forward with the release, we will have a source > distribution with the incorrect CHANGELOG. Personally, I don't see > this as a huge issue as there aren't that many people that will > open the CHANGELOG in the source distribution, but I thought it an > important enough question to let the community decide. > > Assuming lazy consensus, I will notify the general@ list of our > intent to continue with the release of 0.6-incubating tomorrow > (January 10) afternoon. > > -Matt > >> -----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? >> >>> >>>>> -----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=12311 >> >>>>> 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: [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] >> > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPCwDCAAoJEEfVXEODPFIDj0YIAJj7N8fm3vMyHSKmYPNx/+JH atvopKaXL8K4jlDnftfI2TRpHap/5GGHRYnkjNSToJaGHU1EfqnGTpMp4Z4ZWf53 Z9LH124RTowPv3IWJmgwiFgUNlc3FHtpuCBU52yuSeDmGOUzcuU3q2f8YwtDs2hP h9nSmnB2/C+/eSUkg5V+itYvf71lcuGJG/EJAIByVAknrxPYxI8ugND+1/r1yolT pILv8IF5TlO4OBgoewZSrq3X+I9qgxeFlLGHiG+ZNn5opGGVh96zyIVvrHI4duz0 3GuDuntUG/9eC50/dlA+6ZyAbK0pXq5rUXB30ecfqvJONOs9AUqK6k5JeoO0XEY= =0oH+ -----END PGP SIGNATURE-----
