Okay, let's see, I followed the release procedure on our site to the
letter on this one, that does not mention anything about LICENSE or
NOTICE files. Where should I copy them from (and why does maven not do
that for you when preparing a release)?
For the signing process, I also followed the procedure. Can anyone
tell me what went wrong there? Karl?
Greetings, Marcel
On Jan 31, 2009, at 1:54 , Richard S. Hall wrote:
Yes, I +1 the -1...
I know the release process is a pain, but we need to re-do this one.
Luckily, the fixes are easy.
-> richard
Karl Pauls wrote:
-1
None of the artifacts (.jar, -project, -bin) contain any LICENSE nor
NOTICE files. Furthermore, as mentioned by Felix Meschberger at least
two files have missing license headers (which I consider a blocker as
well).
regards,
Karl
p.s.: Additionally, I don't think the key that was used for signing
is
in the KEYS file.
On Fri, Jan 30, 2009 at 7:42 PM, Marcel Offermans
<[email protected]> wrote:
Hello all,
I'm opening a new vote for the first release candidate for the
dependency
manager and its optional shell command bundle. I've compiled
everything and
put it up for testing and checking here:
http://people.apache.org/~marrs/dependencymanager-2.0.0/
The KEYS file for verifying the signature is also in this
directory and the
checksum files should have the correct format.
The main reason for naming this release 2.0.0 is that there have
been many
1.x versions and snapshots out there, so to avoid any confusion
I'm starting
with 2.0.0.
Please check the release and cast your votes, the vote will be
open for at
least 72 hours:
[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)
Greetings, Marcel
