Ah, I didn’t notice the artifacts because they weren’t listed in the email. The
vote thread needs to list the URLs of the artifacts and include (in the body of
the email) the checksums. (Why? Because people voting on the release must
download those artifacts and check them against the
We have been publishing to the dev/ svn
https://dist.apache.org/repos/dist/dev/incubator/quickstep/0.1.0/RC5/
Maybe we missed something. Is there a better way to announce this?
On Thu, Mar 2, 2017 at 2:49 PM, Julian Hyde wrote:
> I haven’t been voting on the RCs because I
I haven’t been voting on the RCs because I haven’t yet seen a “release
candidate” — a signed artifact (tarball) and its checksums. It seems that while
the code is in good shape, release packaging needs some work. I’ll weigh in on
the latest RC vote thread.
Julian
> On Mar 2, 2017, at 12:33
Hi Julian,
Thanks for your inputs. I will modify the report accordingly and send it
out for review.
Just an update on the release progress - Marc floated a vote for RC5
(yesterday evening CST) on the dev list, which has gotten more than 3
+1s so far. It appears that this release candidate
Hi Julian,
I agree that 'this week' is optimistic. Though, we have been going through
the voting process on @dev, it's likely that the current RC will not pass,
meaning that we'll need to restart the whole process, as you said.
Considering, 'this month' is probably a more realistic wording.
On
In answer to the “How does the podling rate their maturity?”. The incubator
report used to have categories "Ready to Graduate", “Some Community Growth",
"No Release" and "Still Getting Started.” Out of these, I think “No release”
fits best. You can add that the first release is well under way.
Hi Roman,
Apologies for the delay. I am not sure how to address two of these
questions, hence left them blank. Any inputs in that regard should be
helpful. Can you please review the following report?
* Your project name
Apache (incubating) Quickstep
* A brief description of your
Bueller? Bueller? Bueller?