As I said, you're within the guidelines to not extend the vote period, I
was just trying to make sure I had time to do the testing I know I
wanted to do given my expected load the next two days. If my schedule
doesn't line up with the release time frame you want to follow, you
don't have to hold things up just for me.
Christopher wrote:
The benefit to having several active members is that not everybody has
to set aside time for every action. Of course, your testing is greatly
appreciated, if you're able to do it, but if enough other people are
able to get sufficient testing done and votes counted, that should
also be good enough.
To be clear, I'm not opposed to extending the vote to accommodate
additional testing... I just think the existing mechanisms in place
already enable that to occur if it is the will of the majority, and
I'd prefer to let the majority decide through their action and/or
inaction, rather than take preemptive steps which may not really be
necessary. So, I suggest we let things play out and see how it goes.
Is that cool with you?
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Wed, Jun 17, 2015 at 11:28 PM, Josh Elser<[email protected]> wrote:
Christopher wrote:
That's why I put out an rc0 first last week, so people could get a
head start on testing. 1.5.3-rc1 hasn't changed since 1.5.3-rc0
(except a typo fix in build.sh for generating the above RC email).
1.6.3-rc1 has only changed since 1.6.3-rc0 with that typo change and
ACCUMULO-2388.
I missed that "go test now" bit, although, the last 4 weeks have been rather
stressful for me and eating into my Accumulo time.
There are three possibilities:
1. We get enough +1 binding votes, and the release passes (and
anything found after can go in the next release)
2. We find a problem, in which case we address it as a failed (or
canceled) vote.
3. We get an insufficient number of votes to release because an
insufficient number of binding voters complete their testing. If that
happens, we can always call another vote on the same RC artifacts. No
harm done.
I think #3 is a way to extend the vote naturally, and I'm willing to
make a follow up release if #1 occurs and somebody who finishes their
testing late finds something we need to address. So, I don't think we
should be concerned about 3 days.
Of course, all of the above are well within your power. I was just
requesting some extra time up front since, AFAIK, we're not under the gun to
get these released and I know I likely won't get time to look at them before
Saturday.
I know we likely have the ability to get 3 +1s. I was just hoping that I
could contribute some of my own effort to make sure we ship (a) good
release(s).
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
On Wed, Jun 17, 2015 at 8:11 PM, Josh Elser<[email protected]> wrote:
I'm a little worried about finding the time to appropriately review two
release candidates in only 3 days. Can we extend one of these to be 6
days,
please?
Christopher wrote:
Accumulo Developers,
Please consider the following candidate for Accumulo 1.6.3.
Git Commit:
33dd62bbedeb09f3d585cddcc672bb4392111672
Branch:
1.6.3-rc1
If this vote passes, a gpg-signed tag will be created using:
git tag -f -m 'Apache Accumulo 1.6.3' -s 1.6.3
33dd62bbedeb09f3d585cddcc672bb4392111672
Staging repo:
https://repository.apache.org/content/repositories/orgapacheaccumulo-1037
Source (official release artifact):
https://repository.apache.org/content/repositories/orgapacheaccumulo-1037/org/apache/accumulo/accumulo/1.6.3/accumulo-1.6.3-src.tar.gz
Binary:
https://repository.apache.org/content/repositories/orgapacheaccumulo-1037/org/apache/accumulo/accumulo/1.6.3/accumulo-1.6.3-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: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D)
Release notes (in progress) can be found at
https://accumulo.apache.org/release_notes/1.6.3
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.6.3 release of Apache Accumulo.
This vote will end on Sat Jun 20 23:30:00 UTC 2015
(Sat Jun 20 19:30:00 EDT 2015 / Sat Jun 20 16:30: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-1037/
# note the trailing slash is needed
--
Christopher L Tubbs II
http://gravatar.com/ctubbsii
