I _think_ we put ourselves in hot-water too if that becomes a norm, but I understand the point. I just saw that as a assumption a user could do. Specifically, the user who asked for this release, James, had asked for a release which is why I was confused at your comment.

[email protected] wrote:
  Not suggesting encouragement to use the release. But if someone is stuck on 
1.5, and needs the fix, there is an alternative. I speak from experience on 
this issue w/r/t a different Apache project.

-----Original Message-----
From: Christopher [mailto:[email protected]]
Sent: Thursday, September 10, 2015 5:30 PM
To: [email protected]
Subject: Re: [VOTE] Accumulo 1.5.4-rc1

Not releasing is a viable option, but we can't encourage users to use an
unreleased version of our code. That's not an appropriate substitute for
releasing.

On Thu, Sep 10, 2015 at 4:19 PM<[email protected]>  wrote:

If the critical issues are fixed in 1.5.x, and someone needs them,
can't they check out the source and build it themselves? Is that a viable
option?
----- Original Message -----

From: "Christopher"<[email protected]>
To: [email protected]
Sent: Thursday, September 10, 2015 3:44:20 PM
Subject: Re: [VOTE] Accumulo 1.5.4-rc1

The larger concern I have is that expecting it to be fixed prior to
1.5.4 might mean loss of willingness to create an RC2 for 1.5.4 and
release it at all. Recall, the 1.5 branch was only revived at all to
fix some critical issues and move on. It's still a viable alternative
to abandon 1.5.x and focus on fixing these issues in 1.6, and later,
where we've made dramatic improvements to the build. Fixing these
newly identified issues is going to take some time and effort. It's
not that it can't be done for 1.5.4... but the question is... who is going to do
it? Is anybody who issued a "-1"
willing to step up and resolve these issues? Or will it rely on Josh?
I'm currently looking at some of the issues to try to help out if I
can, but I also have other obligations.

On Thu, Sep 10, 2015 at 3:33 PM Alex Moundalexis<[email protected]>
wrote:

-1 (non-binding)

Fix now and it'll be fixed here and in 1.6.x.

On Thu, Sep 10, 2015 at 2:46 AM, Sean Busbey<[email protected]>
wrote:
-1

* signatures check out
* checksums match
* licensing errors noted in ACCUMULO-3988

On Sat, Sep 5, 2015 at 4:27 PM, Josh Elser<[email protected]>  wrote:

Accumulo Developers,

Please consider the following candidate for Accumulo 1.5.4.

Git Commit:
12a1041dcbb7f3b10543c305f27ece4b0d65ab9c
Branch:
1.5.4-rc1

If this vote passes, a gpg-signed tag will be created using:
git tag -f -m 'Apache Accumulo 1.5.4' -s 1.5.4
12a1041dcbb7f3b10543c305f27ece4b0d65ab9c

Staging repo:

https://repository.apache.org/content/repositories/orgapacheaccumulo-1
039
Source (official release artifact):

https://repository.apache.org/content/repositories/orgapacheaccumulo-1
039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-src.tar.gz
Binary:

https://repository.apache.org/content/repositories/orgapacheaccumulo-1
039/org/apache/accumulo/accumulo/1.5.4/accumulo-1.5.4-bin.tar.gz
(Append ".sha1", ".md5", or ".asc" to download the
signature/hash
for a
given artifact.)

All artifacts were built and staged with:
mvn release:prepare&&  mvn release:perform

Signing keys are available at
https://www.apache.org/dist/accumulo/KEYS
(Expected fingerprint:
ABC8914C675FAD3FA74F39B2D146D62CAB471AE9)
Release notes (in progress) can be found at
https://accumulo.apache.org/release_notes/1.5.4

Please vote one of:
[ ] +1 - I have verified and accept...
[ ] +0 - I have reservations, but not strong enough to vote
against...
[ ] -1 - Because..., I do not accept...
... these artifacts as the 1.5.4 release of Apache Accumulo.

This vote will end on Thurs Sep 10 23:00:00 UTC 2015 (Thurs Sep
10 20:00:00 EDT 2015 / Thurs Sep 10 17:00:00 PDT 2015)

Thanks!

P.S. Hint: download the whole staging repo with wget
-erobots=off -r -l inf -np -nH \


https://repository.apache.org/content/repositories/orgapacheaccumulo-1
039/
# note the trailing slash is needed



--
Sean



Reply via email to