Release voting process is one of the legal responsibilities of Cayenne
PMC in the ASF, and we need a formal vote on each set of artifacts we
are claiming to be "an Apache Cayenne release". So we definitely need
to discard the last vote, as it is not applicable for the new
artifacts, (which is what you are basically saying below). However I
don't see why we shouldn't wait 72 hours. This is a new vote after all.
Andrus
On Dec 9, 2008, at 2:41 PM, Kevin Menard wrote:
I've put up new artifacts for 3.0M5 that should address the problems
Tore and Andrus encountered.
I refreshed on voting policy as well. Releases cannot be vetoed, so
we can push ahead with the release now. However, we are looking at
new artifacts, so I would like to see at least three +1 votes on the
new artifacts before we cut the release. The GPG sig and MD5
checksums should be rechecked as well.
I will not be restarting the 72 hour window. Three +1 will do it.
I'd expect any other blocker issues to have been uncovered.
--
Kevin
On Sun, Dec 7, 2008 at 2:36 PM, Tore Halset <[EMAIL PROTECTED]>
wrote:
Hello.
-1
as it breaks my production system as described in an email from me
5/12. I
am currently tesing this with Andrus latest fix.
- Tore.
On Dec 2, 2008, at 14:10, Kevin Menard wrote:
Hi all,
I'm raising the vote release Cayenne 3.0 M5. I've prepared and
signed
the 3.0M5 binaries and they are available here:
http://people.apache.org/~kmenard/release/3.0M5/
Here is my +1 for the release.
--
Kevin
