On Sun, 2008-09-21 at 19:24 +0200, Stefano Bagnara wrote: > Oleg Kalnichevski ha scritto: > > Folks, > > > > The 0.5 release is pretty much ready. Please do try to find a moment to > > review the release notes, packages and the web site: > > > > release notes: > > http://people.apache.org/~olegk/mime4j-preview/RELEASE_NOTES.txt > > Great! :-) > > > packages: > > http://people.apache.org/~olegk/mime4j-preview/packages/ > > The src package contains a lib folder that should not be there. >
Fixed. I also fixed a whole bunch of javadoc warnings. New packages uploaded. > > site (status page): > > http://people.apache.org/~olegk/mime4j-preview/site/status.html > > > > If anything is wrong, just go ahead and fix it in the source > > I've no time now.. I'll check the above issue tomorrow. > > > ===================== > > My interpretation of the feedback given the release policies by the > > legal folks is that we no longer need to vote on binary artifacts as > > long as they are generated from the official source distribution > > > > https://issues.apache.org/jira/browse/LEGAL-34 > > My interpretation is that no one from the legal team answered, yet ;-) > And they probably won't given there is a reasonably satisfactory answer to the question. > > If anyone would still like to vote on the Maven artifacts, please let me > > know. > > If it comes for free I'd like to also review them while reviewing other > packages. What if I find that a generated maven artifact has a wrong > NOTICE? I always thought one is meant to test that the release src package builds and generates correct binary artifacts ;-) > Should I vote down the source release? In this case I think that > is a facility from the release manager to the reviewers to publish them > too otherwise each voter should build and check the generated binary > artifacts locally. > See above. > Let's say a binary generation script works differently in my machine and > in the release manager machine and in my machine it produces correct > binaries while in your machine it produces bad binaries (a pratical > example could be a java version issue: let's say we have sources with no > -target specified, and I use java 1.5 while the release manager uses > java 1.5... if we don't review binaries generated by the release manager > we'll end up with java 5 only binaries...). I don't know what is the > procedure in this cases.. maybe the binary artifacts can be fixed and > replaced without requiring a new vote? > My understanding is that only the source package is what a release vote is all about. Binary artifacts are merely byproducts. They MUST be built from the source package, though, but can be (re)published without a vote. Anyways, I'll post maven artifacts when the official vote is held to make everyone happy. Oleg > Stefano > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
