You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Ryan Ollos <ry...@wandisco.com> on 2013/01/14 20:53:03 UTC
[VOTE] Release Apache Bloodhound 0.4 (incubating)
Hi everyone,
I would like to initiate the vote for releasing Apache Bloodhound 0.4
(incubating).
Please find the change log for this proposed release below:
* Replaces ticket edit form with a new 'in-place' edit and workflow control
* Added white-labeling for error messages and basic branding
* Improvements to the quick ticket creation form including ability to
specify the select fields and their order
* Various bug fixes
* Not fixed for this release:
* No major outstanding issues
The release candidate artifacts consist of source release as a tar.gz
archive along with the associated MD5 and GPG signature.
These can be found at:
https://dist.apache.org/repos/dist/dev/incubator/bloodhound/
The archive is based on the tag:
http://svn.apache.org/viewvc/incubator/bloodhound/tags/0.4-incubating
For this release, the archive differs from the tag in that the Trac
"contrib" directory has been removed from the archive. The files
in that directory currently lack license headers. We are working
with the Trac team to clarify the licenses under which the contrib files
are released:
https://issues.apache.org/bloodhound/ticket/273
Please vote:
[ ] +1 Release this package as Apache Bloodhound 0.4
[ ] +0 Don't care
[ ] -1 Do not release this package (please explain)
The vote is open for 72 hours and, if successful, will be followed by a
vote on general@incubator for a further 72 hours.
Regards,
- Ryan
Re: [VOTE] Release Apache Bloodhound 0.4 (incubating)
Posted by Jure Zitnik <ju...@digiverse.si>.
+1 for release (non-binding)
Regards,
Jure
On 1/14/13 8:53 PM, Ryan Ollos wrote:
> Hi everyone,
>
> I would like to initiate the vote for releasing Apache Bloodhound 0.4
> (incubating).
>
> Please find the change log for this proposed release below:
>
> * Replaces ticket edit form with a new 'in-place' edit and workflow control
> * Added white-labeling for error messages and basic branding
> * Improvements to the quick ticket creation form including ability to
> specify the select fields and their order
> * Various bug fixes
>
> * Not fixed for this release:
> * No major outstanding issues
>
> The release candidate artifacts consist of source release as a tar.gz
> archive along with the associated MD5 and GPG signature.
> These can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/bloodhound/
>
> The archive is based on the tag:
> http://svn.apache.org/viewvc/incubator/bloodhound/tags/0.4-incubating
>
> For this release, the archive differs from the tag in that the Trac
> "contrib" directory has been removed from the archive. The files
> in that directory currently lack license headers. We are working
> with the Trac team to clarify the licenses under which the contrib files
> are released:
> https://issues.apache.org/bloodhound/ticket/273
>
> Please vote:
> [ ] +1 Release this package as Apache Bloodhound 0.4
> [ ] +0 Don't care
> [ ] -1 Do not release this package (please explain)
>
> The vote is open for 72 hours and, if successful, will be followed by a
> vote on general@incubator for a further 72 hours.
>
> Regards,
> - Ryan
>
Re: [VOTE] Release Apache Bloodhound 0.4 (incubating)
Posted by Gary Martin <ga...@wandisco.com>.
On 16/01/13 15:48, Andrej Golcov wrote:
> +1 for release (non-binding)
>
> No problems on my Mac and Windows test environments.
>
> A few comments regarding installation process:
> - Since tar.gz format is not supported by default on Windows, I
> suggest Bloodhound packaged also as zip to be become more friendly to
> Windows environment. For example, Apache HTTP Server and Apache Solr
> have also zip packaging.
We have no obligation to do so but, equally, it is not necessarily a bad
idea. At the moment we are just keeping the load on release managers and
testing the releases a little lower as each has to be signed and
md5summed. That said, it should be as little as repeating the
instructions with s/.tar.gz/.zip/ and the command to create a zip file
and all that could be documented.
> - Installation process, described in
> https://issues.apache.org/bloodhound/wiki/BloodhoundInstall, uses svn
> trunk as installation source: "svn co
> https://svn.apache.org/repos/asf/incubator/bloodhound/trunk
> bloodhound"
> May be it is better to start from *.tar.gz file for user installation
> and use svn-based installation for BloodhoundContributing process?
>
> - requirements-dev.txt is used for pip install command. Should
> requirements.txt be used instead?
>
> - windows specific activation command is not correct. Current:
> "bloodhound\bin\activate.bat", must be (I guess)
> "bloodhound\Scripts\activate.bat"
All good points. We should get these items corrected soon. If you want
to try to correct these issues, that should be fine.
> May be it worse to provide Windows specific installation steps or even cmd file?
Noting the difference somewhere should be enough for now as long as it
is not too cumbersome or confusing.
Cheers,
Gary
Re: [VOTE] Release Apache Bloodhound 0.4 (incubating)
Posted by Andrej Golcov <an...@digiverse.si>.
> May be it worse to provide Windows specific installation steps or even cmd file?
BTW, if you think that installation .cmd/.bat file for Windows is good
idea, I'm volunteering myself for it creation.
Regards, Andrej
Re: [VOTE] Release Apache Bloodhound 0.4 (incubating)
Posted by Andrej Golcov <an...@digiverse.si>.
+1 for release (non-binding)
No problems on my Mac and Windows test environments.
A few comments regarding installation process:
- Since tar.gz format is not supported by default on Windows, I
suggest Bloodhound packaged also as zip to be become more friendly to
Windows environment. For example, Apache HTTP Server and Apache Solr
have also zip packaging.
- Installation process, described in
https://issues.apache.org/bloodhound/wiki/BloodhoundInstall, uses svn
trunk as installation source: "svn co
https://svn.apache.org/repos/asf/incubator/bloodhound/trunk
bloodhound"
May be it is better to start from *.tar.gz file for user installation
and use svn-based installation for BloodhoundContributing process?
- requirements-dev.txt is used for pip install command. Should
requirements.txt be used instead?
- windows specific activation command is not correct. Current:
"bloodhound\bin\activate.bat", must be (I guess)
"bloodhound\Scripts\activate.bat"
May be it worse to provide Windows specific installation steps or even cmd file?
Regards, Andrej
Re: [VOTE] Release Apache Bloodhound 0.4 (incubating)
Posted by John Chambers <ch...@apache.org>.
+1 (binding)
Can't see any problems with this release in my test environment.
Regards
John Chambers
On 14 January 2013 19:53, Ryan Ollos <ry...@wandisco.com> wrote:
> Hi everyone,
>
> I would like to initiate the vote for releasing Apache Bloodhound 0.4
> (incubating).
>
> Please find the change log for this proposed release below:
>
> * Replaces ticket edit form with a new 'in-place' edit and workflow
> control
> * Added white-labeling for error messages and basic branding
> * Improvements to the quick ticket creation form including ability to
> specify the select fields and their order
> * Various bug fixes
>
> * Not fixed for this release:
> * No major outstanding issues
>
> The release candidate artifacts consist of source release as a tar.gz
> archive along with the associated MD5 and GPG signature.
> These can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/bloodhound/
>
> The archive is based on the tag:
> http://svn.apache.org/viewvc/incubator/bloodhound/tags/0.4-incubating
>
> For this release, the archive differs from the tag in that the Trac
> "contrib" directory has been removed from the archive. The files
> in that directory currently lack license headers. We are working
> with the Trac team to clarify the licenses under which the contrib files
> are released:
> https://issues.apache.org/bloodhound/ticket/273
>
> Please vote:
> [ ] +1 Release this package as Apache Bloodhound 0.4
> [ ] +0 Don't care
> [ ] -1 Do not release this package (please explain)
>
> The vote is open for 72 hours and, if successful, will be followed by a
> vote on general@incubator for a further 72 hours.
>
> Regards,
> - Ryan
>
Re: [VOTE] Release Apache Bloodhound 0.4 (incubating)
Posted by Matevz Bradac <ma...@gmail.com>.
+1 for release (non-binding)
--
matevz
On Mon, Jan 14, 2013 at 8:53 PM, Ryan Ollos <ry...@wandisco.com> wrote:
> Hi everyone,
>
> I would like to initiate the vote for releasing Apache Bloodhound 0.4
> (incubating).
>
> Please find the change log for this proposed release below:
>
> * Replaces ticket edit form with a new 'in-place' edit and workflow control
> * Added white-labeling for error messages and basic branding
> * Improvements to the quick ticket creation form including ability to
> specify the select fields and their order
> * Various bug fixes
>
> * Not fixed for this release:
> * No major outstanding issues
>
> The release candidate artifacts consist of source release as a tar.gz
> archive along with the associated MD5 and GPG signature.
> These can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/bloodhound/
>
> The archive is based on the tag:
> http://svn.apache.org/viewvc/incubator/bloodhound/tags/0.4-incubating
>
> For this release, the archive differs from the tag in that the Trac
> "contrib" directory has been removed from the archive. The files
> in that directory currently lack license headers. We are working
> with the Trac team to clarify the licenses under which the contrib files
> are released:
> https://issues.apache.org/bloodhound/ticket/273
>
> Please vote:
> [ ] +1 Release this package as Apache Bloodhound 0.4
> [ ] +0 Don't care
> [ ] -1 Do not release this package (please explain)
>
> The vote is open for 72 hours and, if successful, will be followed by a
> vote on general@incubator for a further 72 hours.
>
> Regards,
> - Ryan
Re: [VOTE] Release Apache Bloodhound 0.4 (incubating)
Posted by Gary Martin <ga...@wandisco.com>.
+1 (binding)
I've checked that the md5 and pgp match the tarball and I've done a
quick basic install and all seems fine. The RAT report in
http://ci.apache.org/projects/bloodhound/rat-output.html looks good at
the moment too (I have not run RAT directly on the tarball though).
Excellent work.. and thanks for the help with improving the
documentation of the release process!
Cheers,
Gary
On 14/01/13 19:53, Ryan Ollos wrote:
> Hi everyone,
>
> I would like to initiate the vote for releasing Apache Bloodhound 0.4
> (incubating).
>
> Please find the change log for this proposed release below:
>
> * Replaces ticket edit form with a new 'in-place' edit and workflow control
> * Added white-labeling for error messages and basic branding
> * Improvements to the quick ticket creation form including ability to
> specify the select fields and their order
> * Various bug fixes
>
> * Not fixed for this release:
> * No major outstanding issues
>
> The release candidate artifacts consist of source release as a tar.gz
> archive along with the associated MD5 and GPG signature.
> These can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/bloodhound/
>
> The archive is based on the tag:
> http://svn.apache.org/viewvc/incubator/bloodhound/tags/0.4-incubating
>
> For this release, the archive differs from the tag in that the Trac
> "contrib" directory has been removed from the archive. The files
> in that directory currently lack license headers. We are working
> with the Trac team to clarify the licenses under which the contrib files
> are released:
> https://issues.apache.org/bloodhound/ticket/273
>
> Please vote:
> [ ] +1 Release this package as Apache Bloodhound 0.4
> [ ] +0 Don't care
> [ ] -1 Do not release this package (please explain)
>
> The vote is open for 72 hours and, if successful, will be followed by a
> vote on general@incubator for a further 72 hours.
>
> Regards,
> - Ryan
>
Re: [VOTE] Release Apache Bloodhound 0.4 (incubating)
Posted by Olemis Lang <ol...@gmail.com>.
On 1/14/13, Ryan Ollos <ry...@wandisco.com> wrote:
> Hi everyone,
>
:)
[...]
>
> Please vote:
> [ ] +1 Release this package as Apache Bloodhound 0.4
> [ ] +0 Don't care
> [ ] -1 Do not release this package (please explain)
>
+1 (non-binding)
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: new KEYS scheme? (Was: Re: [VOTE] Release Apache Bloodhound 0.4
(incubating))
Posted by Gary Martin <ga...@wandisco.com>.
On 15/01/13 10:56, Nick Burch wrote:
> On Tue, 15 Jan 2013, Gary Martin wrote:
>> I don't know if there is a plan to make this even less work but I
>> think we could probably keep the KEYS file up to date by:
>>
>> wget -O KEYS https://people.apache.org/keys/group/bloodhound.asc
>>
>> and committing any changes.
>>
>> Does anyone know more about all this though?
>
> There has been some discussions about this in the last few weeks (most
> on the infrastructure list, if memory serves). As long as everyone has
> their current key in LDAP, then that's a good way to keep the list
> current. However, the KEYs file should generally also contain the list
> of past keys too, so people can use it to verify old releases too. To
> that end, you probably want to use the LDAP generated keys file to
> append to your keys list, not replace it, so the old keys remain there
> too. It's a few more steps than just a wget+commit, but not many!
>
> Nick
Ah, thanks for that; good point there. It may not be hugely complicated
but I might write a script to do the job so that we don't have to worry
too much about manually working out which entries are new and which are
no longer in the bloodhound.asc file.
Cheers,
Gary
Re: new KEYS scheme? (Was: Re: [VOTE] Release Apache Bloodhound 0.4
(incubating))
Posted by Nick Burch <ap...@gagravarr.org>.
On Tue, 15 Jan 2013, Gary Martin wrote:
> I don't know if there is a plan to make this even less work but I think we
> could probably keep the KEYS file up to date by:
>
> wget -O KEYS https://people.apache.org/keys/group/bloodhound.asc
>
> and committing any changes.
>
> Does anyone know more about all this though?
There has been some discussions about this in the last few weeks (most on
the infrastructure list, if memory serves). As long as everyone has their
current key in LDAP, then that's a good way to keep the list current.
However, the KEYs file should generally also contain the list of past keys
too, so people can use it to verify old releases too. To that end, you
probably want to use the LDAP generated keys file to append to your keys
list, not replace it, so the old keys remain there too. It's a few more
steps than just a wget+commit, but not many!
Nick
new KEYS scheme? (Was: Re: [VOTE] Release Apache Bloodhound 0.4 (incubating))
Posted by Gary Martin <ga...@wandisco.com>.
On 15/01/13 06:22, Ryan Ollos wrote:
> On Mon, Jan 14, 2013 at 9:23 PM, Branko Čibej <br...@wandisco.com> wrote:
>
>> +1
>>
> Can I count you as a binding vote?
>
>
>> Very nice. I see you remove trac/contrib when creating the tarball,
>> which is good. Installed in 5 minutes on my Mac, too.
>>
>> Only one nit: the release manager's PGP key is not in KEYS. Ryan, you
>> should add it; as far as I'm concerned it's OK to just fix the KEYS file
>> in the dist tree, since that won't be changing the packages or checksums
>> in any way.
>>
> Thanks, I will add my key. Gary had mentioned this might be needed. I'll
> also add a note to the Release Process wiki page about this.
Yeah, I vaguely remembered something about a new way of listing the
keys. Presumably, that is something to do with what this file:
https://people.apache.org/keys/group/bloodhound.asc
I don't know if there is a plan to make this even less work but I think
we could probably keep the KEYS file up to date by:
wget -O KEYS https://people.apache.org/keys/group/bloodhound.asc
and committing any changes.
Does anyone know more about all this though? I didn't see any mention
about this in http://www.apache.org/dev/release-signing.html so I am not
sure it is likely that new incubator projects will pick up on this.
Cheers,
Gary
Re: [VOTE] Release Apache Bloodhound 0.4 (incubating)
Posted by Branko Čibej <br...@wandisco.com>.
On 15.01.2013 07:22, Ryan Ollos wrote:
> On Mon, Jan 14, 2013 at 9:23 PM, Branko Čibej <br...@wandisco.com> wrote:
>
>> +1
>>
> Can I count you as a binding vote?
I'm your mentor, what do you think? :)
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: [VOTE] Release Apache Bloodhound 0.4 (incubating)
Posted by Ryan Ollos <ry...@wandisco.com>.
On Mon, Jan 14, 2013 at 9:23 PM, Branko Čibej <br...@wandisco.com> wrote:
> +1
>
Can I count you as a binding vote?
> Very nice. I see you remove trac/contrib when creating the tarball,
> which is good. Installed in 5 minutes on my Mac, too.
>
> Only one nit: the release manager's PGP key is not in KEYS. Ryan, you
> should add it; as far as I'm concerned it's OK to just fix the KEYS file
> in the dist tree, since that won't be changing the packages or checksums
> in any way.
>
Thanks, I will add my key. Gary had mentioned this might be needed. I'll
also add a note to the Release Process wiki page about this.
> -- Brane
>
> On 14.01.2013 20:53, Ryan Ollos wrote:
> > Hi everyone,
> >
> > I would like to initiate the vote for releasing Apache Bloodhound 0.4
> > (incubating).
> >
> > Please find the change log for this proposed release below:
> >
> > * Replaces ticket edit form with a new 'in-place' edit and workflow
> control
> > * Added white-labeling for error messages and basic branding
> > * Improvements to the quick ticket creation form including ability to
> > specify the select fields and their order
> > * Various bug fixes
> >
> > * Not fixed for this release:
> > * No major outstanding issues
> >
> > The release candidate artifacts consist of source release as a tar.gz
> > archive along with the associated MD5 and GPG signature.
> > These can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/bloodhound/
> >
> > The archive is based on the tag:
> > http://svn.apache.org/viewvc/incubator/bloodhound/tags/0.4-incubating
> >
> > For this release, the archive differs from the tag in that the Trac
> > "contrib" directory has been removed from the archive. The files
> > in that directory currently lack license headers. We are working
> > with the Trac team to clarify the licenses under which the contrib files
> > are released:
> > https://issues.apache.org/bloodhound/ticket/273
> >
> > Please vote:
> > [ ] +1 Release this package as Apache Bloodhound 0.4
> > [ ] +0 Don't care
> > [ ] -1 Do not release this package (please explain)
> >
> > The vote is open for 72 hours and, if successful, will be followed by a
> > vote on general@incubator for a further 72 hours.
> >
> > Regards,
> > - Ryan
> >
>
>
> --
> Branko Čibej
> Director of Subversion | WANdisco | www.wandisco.com
>
>
Re: [VOTE] Release Apache Bloodhound 0.4 (incubating)
Posted by Branko Čibej <br...@wandisco.com>.
+1
Very nice. I see you remove trac/contrib when creating the tarball,
which is good. Installed in 5 minutes on my Mac, too.
Only one nit: the release manager's PGP key is not in KEYS. Ryan, you
should add it; as far as I'm concerned it's OK to just fix the KEYS file
in the dist tree, since that won't be changing the packages or checksums
in any way.
-- Brane
On 14.01.2013 20:53, Ryan Ollos wrote:
> Hi everyone,
>
> I would like to initiate the vote for releasing Apache Bloodhound 0.4
> (incubating).
>
> Please find the change log for this proposed release below:
>
> * Replaces ticket edit form with a new 'in-place' edit and workflow control
> * Added white-labeling for error messages and basic branding
> * Improvements to the quick ticket creation form including ability to
> specify the select fields and their order
> * Various bug fixes
>
> * Not fixed for this release:
> * No major outstanding issues
>
> The release candidate artifacts consist of source release as a tar.gz
> archive along with the associated MD5 and GPG signature.
> These can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/bloodhound/
>
> The archive is based on the tag:
> http://svn.apache.org/viewvc/incubator/bloodhound/tags/0.4-incubating
>
> For this release, the archive differs from the tag in that the Trac
> "contrib" directory has been removed from the archive. The files
> in that directory currently lack license headers. We are working
> with the Trac team to clarify the licenses under which the contrib files
> are released:
> https://issues.apache.org/bloodhound/ticket/273
>
> Please vote:
> [ ] +1 Release this package as Apache Bloodhound 0.4
> [ ] +0 Don't care
> [ ] -1 Do not release this package (please explain)
>
> The vote is open for 72 hours and, if successful, will be followed by a
> vote on general@incubator for a further 72 hours.
>
> Regards,
> - Ryan
>
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com