[RESULT] Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
Hi all, and with this we've got a result! With Brane repeating his IPMC binding vote from bloodhound-dev and Greg and Hyrum adding their voices here, the results are: Greg Stein (binding) +1 Hyrum Wright (binding) +1 Branko Čibej (binding) +1 With 3 +1s I understand that release of Apache Bloodhound 0.2 (incubating) is approved. I will complete the process by moving the artefacts from Bloodhound's /dist/dev area to the equivalent /dist/release area this evening. Thanks to all those who took part. Cheers, Joe On 15 November 2012 02:15, Greg Stein gst...@gmail.com wrote: I've confirmed this discrepancy is the same as what Alexander Broekhuis posted about, as noted in INFRA-5445. So 0.2 is all good to go!! On Wed, Nov 14, 2012 at 12:57 PM, Greg Stein gst...@gmail.com wrote: Oh. Forgot one item: so the below is conditional on resolving: the .md5 does not match the .tar.gz. (I did not examine the signature (.asc) to see if it matches the .tar.gz) On Wed, Nov 14, 2012 at 12:52 PM, Greg Stein gst...@gmail.com wrote: +1 to release (IPMC, binding) [ apologies for the extreme delay :-( ] On Mon, Oct 29, 2012 at 10:22 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: Hi, I would like to request the beginning of the vote for the second release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs The artefacts for the release including the source distribution and KEYS can be found here: https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ The release itself is created from: https://svn.apache.org/repos/asf/incubator/bloodhound/branches/0.2 (r1394550) Issues identified to be fixed for the next release are listed here: https://issues.apache.org/bloodhound/ticket/246 https://issues.apache.org/bloodhound/ticket/245 The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Bloodhound 0.2 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) Cheers, Joe - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Joe Dreimann UX Designer | WANdisco http://www.wandisco.com/ * * *Transform your software development department. Register for a free SVN HealthCheck http://go.wandisco.com/HealthCheck-Sig.html *
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
+1 to release (IPMC, binding) [ apologies for the extreme delay :-( ] On Mon, Oct 29, 2012 at 10:22 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: Hi, I would like to request the beginning of the vote for the second release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs The artefacts for the release including the source distribution and KEYS can be found here: https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ The release itself is created from: https://svn.apache.org/repos/asf/incubator/bloodhound/branches/0.2 (r1394550) Issues identified to be fixed for the next release are listed here: https://issues.apache.org/bloodhound/ticket/246 https://issues.apache.org/bloodhound/ticket/245 The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Bloodhound 0.2 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) Cheers, Joe - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
Oh. Forgot one item: so the below is conditional on resolving: the .md5 does not match the .tar.gz. (I did not examine the signature (.asc) to see if it matches the .tar.gz) On Wed, Nov 14, 2012 at 12:52 PM, Greg Stein gst...@gmail.com wrote: +1 to release (IPMC, binding) [ apologies for the extreme delay :-( ] On Mon, Oct 29, 2012 at 10:22 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: Hi, I would like to request the beginning of the vote for the second release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs The artefacts for the release including the source distribution and KEYS can be found here: https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ The release itself is created from: https://svn.apache.org/repos/asf/incubator/bloodhound/branches/0.2 (r1394550) Issues identified to be fixed for the next release are listed here: https://issues.apache.org/bloodhound/ticket/246 https://issues.apache.org/bloodhound/ticket/245 The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Bloodhound 0.2 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) Cheers, Joe - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
Hi, 2012/11/14 Greg Stein gst...@gmail.com Oh. Forgot one item: so the below is conditional on resolving: the .md5 does not match the .tar.gz. (I did not examine the signature (.asc) to see if it matches the .tar.gz) I haven't checked the files, but they are placed in svn, and when downloading using chrome or firefox the files are double gzipped. We (Celix) had the same problem. See [1] for more info. This sounds like a similar problem.. Did you try downloading the file using wget? [1]: https://issues.apache.org/jira/browse/INFRA-5445 -- Met vriendelijke groet, Alexander Broekhuis
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
On Nov 14, 2012 2:13 PM, Alexander Broekhuis a.broekh...@gmail.com wrote: Hi, 2012/11/14 Greg Stein gst...@gmail.com Oh. Forgot one item: so the below is conditional on resolving: the .md5 does not match the .tar.gz. (I did not examine the signature (.asc) to see if it matches the .tar.gz) I haven't checked the files, but they are placed in svn, and when downloading using chrome or firefox the files are double gzipped. We (Celix) had the same problem. See [1] for more info. This sounds like a similar problem.. Did you try downloading the file using wget? Ooh! I used Chrome. Will try wget when I get home. Thanks! -g
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
I've confirmed this discrepancy is the same as what Alexander Broekhuis posted about, as noted in INFRA-5445. So 0.2 is all good to go!! On Wed, Nov 14, 2012 at 12:57 PM, Greg Stein gst...@gmail.com wrote: Oh. Forgot one item: so the below is conditional on resolving: the .md5 does not match the .tar.gz. (I did not examine the signature (.asc) to see if it matches the .tar.gz) On Wed, Nov 14, 2012 at 12:52 PM, Greg Stein gst...@gmail.com wrote: +1 to release (IPMC, binding) [ apologies for the extreme delay :-( ] On Mon, Oct 29, 2012 at 10:22 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: Hi, I would like to request the beginning of the vote for the second release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs The artefacts for the release including the source distribution and KEYS can be found here: https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ The release itself is created from: https://svn.apache.org/repos/asf/incubator/bloodhound/branches/0.2 (r1394550) Issues identified to be fixed for the next release are listed here: https://issues.apache.org/bloodhound/ticket/246 https://issues.apache.org/bloodhound/ticket/245 The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Bloodhound 0.2 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) Cheers, Joe - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Fwd: [VOTE] Release Apache Bloodhound 0.2 (incubating)
Matt and others: Do you feel our efforts to remove minified files from future releases are sufficient for you to cast a vote confidently on this release? Ticket #255 [1] has removed all minified files from Bloodhound code and our docs area, the only remaining ones are in our copy to Trac and are being dealt with as a blocker for the next release in #256 [2]. Cheers, Joe [1] https://issues.apache.org/**bloodhound/ticket/255https://issues.apache.org/bloodhound/ticket/255 [2] https://issues.apache.org/**bloodhound/ticket/256https://issues.apache.org/bloodhound/ticket/256 [Resent to incude general@incubator] On 13 November 2012 09:57, Gary Martin gary.mar...@wandisco.com wrote: Thanks for that Joe. I closed #255 on the basis of that work and I have raised another that can be used to complete any work for our copy of Trac that turns out to be required: https://issues.apache.org/** bloodhound/ticket/256 https://issues.apache.org/bloodhound/ticket/256 Obviously if we determine here that there is nothing to do then #256 should be closed with a link to the relevant decisions. I have set it as a blocker for release 3 as we need to get this sorted quickly. Cheers, Gary On 12/11/12 18:32, Joachim Dreimann wrote: Gary has raised ticket #255 to remove all minified files before the next release: https://issues.apache.org/**bloodhound/ticket/255https://issues.apache.org/bloodhound/ticket/255 With my last commit (r1408385) we have now removed all .min. files from bloodhound code and our docs. The only remaining minified files in our repository are now part of the Trac code. - Joe On 12 November 2012 17:38, Gary Martin gary.mar...@wandisco.com wrote: On 12/11/12 13:19, Branko Čibej wrote: On 12.11.2012 13:25, Gary Martin wrote: OK, when I looked closer at the Trac files it seems that they do minify some of it after all. Are we happy to maintain this as another difference between our copy of Trac and upstream? The important question is, are the files minified in the Trac repository, or in their release tarballs? If it's in the repo, well then, my interpretation is that you're just shipping Trac with a few patches (and I expect those patches aren't in the minified code). If it's just in the release tarballs, then I expect the upstream import went awry and needs to be fixed. -- Brane It would appear that there is minified code direct in the Trac repositories. See http://trac.edgewall.org/ browser/trunk/trac/htdocs/js/http://trac.edgewall.org/**browser/trunk/trac/htdocs/js/ **jquery.jshttp://trac.**edgewall.org/browser/trunk/** trac/htdocs/js/jquery.jshttp://trac.edgewall.org/browser/trunk/trac/htdocs/js/jquery.jsfor instance. I suspect we will need a few more opinions from IPMC members to be sure that this argument is enough to make the problem go away. I don't particularly want to have to maintain more differences from upstream but I prefer to get the correct approach in place here. Cheers, Gary -- Joe Dreimann UX Designer | WANdisco http://www.wandisco.com/ * * *Transform your software development department. Register for a free SVN HealthCheck http://go.wandisco.com/HealthCheck-Sig.html * -- Joe Dreimann UX Designer | WANdisco http://www.wandisco.com/ * * *Transform your software development department. Register for a free SVN HealthCheck http://go.wandisco.com/HealthCheck-Sig.html *
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
Apologies for the delay, the conference wifi was taken down before I could send the e-mail. Unfortunately, when I ran a license header check, the report came back with some minified css js files in the source release. As far as I am aware, minified files are not considered source and therefore should not be in the distribution. -Matt On 10/29/12 10:22 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: Hi, I would like to request the beginning of the vote for the second release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs The artefacts for the release including the source distribution and KEYS can be found here: https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ The release itself is created from: https://svn.apache.org/repos/asf/incubator/bloodhound/branches/0.2 (r1394550) Issues identified to be fixed for the next release are listed here: https://issues.apache.org/bloodhound/ticket/246 https://issues.apache.org/bloodhound/ticket/245 The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Bloodhound 0.2 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) Cheers, Joe - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
On 10.11.2012 14:39, Franklin, Matthew B. wrote: Apologies for the delay, the conference wifi was taken down before I could send the e-mail. Unfortunately, when I ran a license header check, the report came back with some minified css js files in the source release. As far as I am aware, minified files are not considered source and therefore should not be in the distribution. Hm, then why doesn't that show up here: http://ci.apache.org/builders/bloodhound-trunk-rat-report Regarding the minified files you found: I agree that minification should, in future, be part of the installation process. However, once can hardly claim that minified files are not source. They are souce, not even compressed. IMO the point of having source releases is auditability. Minification makes it harder, but doesn't take it away (as, for example, compilation does). I propose this is not a release blocker. We should however recommend that the project stops shipping minified sources in some (near) future release. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
On 11/5/12 6:38 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: +1 (non-binding) Is there precedent on releasing with less than three +1s from IPMC members if there are no 0s or -1s from anyone at all? The minimum required 72 hours have also passed. Unfortunately, a release requires at least 3 IPMC members to vote +1. I am looking at it now and will cast a vote when I have properly reviewed the release. We'd really like to establish a frequent release cycle, Bloodhound 0.3 is already ready to be packaged up as soon as 0.2 has been released. Thanks, Joe On 31 October 2012 21:49, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Oct 29, 2012 at 7:22 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs This message didn't include an IPMC tally, but I see that Mentor Branko Čibej voted on the bloodhound-dev thread. That makes one IPMC member voting +1; two more are needed. The vote will be open for at least 72 hours. Less than a day left... any takers? Marvin Humphrey -- Joe Dreimann UX Designer | WANdisco http://www.wandisco.com/ * * *Transform your software development department. Register for a free SVN HealthCheck http://go.wandisco.com/HealthCheck-Sig.html * - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
Marvin: Thank you for the helpful feedback. I will discuss this with the other devs and raise tickets for us as appropriate. I believe Hyrum has not yet voted to my knowledge, only Brane. So we still need two votes at this point. Matthew: Thank you for looking at voting for (or against) this release! I will close the vote open on Sunday 18th November at the latest, or earlier if we achieve three IPMC +1s before. - Joe On 8 November 2012 14:52, Franklin, Matthew B. mfrank...@mitre.org wrote: On 11/5/12 6:38 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: +1 (non-binding) Is there precedent on releasing with less than three +1s from IPMC members if there are no 0s or -1s from anyone at all? The minimum required 72 hours have also passed. Unfortunately, a release requires at least 3 IPMC members to vote +1. I am looking at it now and will cast a vote when I have properly reviewed the release. We'd really like to establish a frequent release cycle, Bloodhound 0.3 is already ready to be packaged up as soon as 0.2 has been released. Thanks, Joe On 31 October 2012 21:49, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Oct 29, 2012 at 7:22 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs This message didn't include an IPMC tally, but I see that Mentor Branko Čibej voted on the bloodhound-dev thread. That makes one IPMC member voting +1; two more are needed. The vote will be open for at least 72 hours. Less than a day left... any takers? Marvin Humphrey
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
On Mon, Oct 29, 2012 at 7:22 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: Hi, I would like to request the beginning of the vote for the second release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. [...] [ ] +1 Release this package as Apache Bloodhound 0.2 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) (Resend with general@incubator.apache.org included) +1 Release this package as Apache Bloodhound 0.2 (non-binding).
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
+1 (non-binding) Is there precedent on releasing with less than three +1s from IPMC members if there are no 0s or -1s from anyone at all? The minimum required 72 hours have also passed. We'd really like to establish a frequent release cycle, Bloodhound 0.3 is already ready to be packaged up as soon as 0.2 has been released. Thanks, Joe On 31 October 2012 21:49, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Oct 29, 2012 at 7:22 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs This message didn't include an IPMC tally, but I see that Mentor Branko Čibej voted on the bloodhound-dev thread. That makes one IPMC member voting +1; two more are needed. The vote will be open for at least 72 hours. Less than a day left... any takers? Marvin Humphrey -- Joe Dreimann UX Designer | WANdisco http://www.wandisco.com/ * * *Transform your software development department. Register for a free SVN HealthCheck http://go.wandisco.com/HealthCheck-Sig.html *
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
On Thu, Nov 1, 2012 at 8:24 AM, Branko Čibej br...@apache.org wrote: On 29.10.2012 15:22, Joachim Dreimann wrote: Hi, I would like to request the beginning of the vote for the second release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs The artefacts for the release including the source distribution and KEYS can be found here: https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ The release itself is created from: https://svn.apache.org/repos/asf/incubator/bloodhound/branches/0.2 (r1394550) Issues identified to be fixed for the next release are listed here: https://issues.apache.org/bloodhound/ticket/246 https://issues.apache.org/bloodhound/ticket/245 The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Bloodhound 0.2 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) +1 to release Apparently my vote got mislaid on the other list. +1 to release. -Hyrum - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
On 29.10.2012 15:22, Joachim Dreimann wrote: Hi, I would like to request the beginning of the vote for the second release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs The artefacts for the release including the source distribution and KEYS can be found here: https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ The release itself is created from: https://svn.apache.org/repos/asf/incubator/bloodhound/branches/0.2 (r1394550) Issues identified to be fixed for the next release are listed here: https://issues.apache.org/bloodhound/ticket/246 https://issues.apache.org/bloodhound/ticket/245 The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Bloodhound 0.2 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) +1 to release Apparently my vote got mislaid on the other list. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
On Mon, Oct 29, 2012 at 7:22 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs This message didn't include an IPMC tally, but I see that Mentor Branko Čibej voted on the bloodhound-dev thread. That makes one IPMC member voting +1; two more are needed. The vote will be open for at least 72 hours. Less than a day left... any takers? Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
On 29/10/12 14:22, Joachim Dreimann wrote: Hi, I would like to request the beginning of the vote for the second release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs The artefacts for the release including the source distribution and KEYS can be found here: https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ The release itself is created from: https://svn.apache.org/repos/asf/incubator/bloodhound/branches/0.2 (r1394550) Issues identified to be fixed for the next release are listed here: https://issues.apache.org/bloodhound/ticket/246 https://issues.apache.org/bloodhound/ticket/245 The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Bloodhound 0.2 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) Cheers, Joe +1 (non-binding) By the way, I note that this VOTE thread appears to have been initiated by an email with reply-to set to bloodhound-dev@. Is that normal for these votes? Perhaps it is just my email client that is doing that. Cheers, Gary - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Bloodhound 0.2 (incubating)
Hi, I would like to request the beginning of the vote for the second release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs The artefacts for the release including the source distribution and KEYS can be found here: https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ The release itself is created from: https://svn.apache.org/repos/asf/incubator/bloodhound/branches/0.2 (r1394550) Issues identified to be fixed for the next release are listed here: https://issues.apache.org/bloodhound/ticket/246 https://issues.apache.org/bloodhound/ticket/245 The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Bloodhound 0.2 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) Cheers, Joe
