Hello all
Thanks Adam and Suresh :-)
I did one minor change after the call for release vote. I realized that
the Javadoc contained broken links in the "Defined in the <foo> module"
text inserted after class description. I removed the broken links,
regenerated the javadoc and re-pushed the "apache-sis-0.3-doc.zip" files
on "dist/dev". I did not touched the "apache-sis-0.3-src.zip" file,
neither redeployed the Maven artifacts (consequently the Javadoc on
Maven repository have the broken links, but it may be in a corner small
enough that few peoples would notice it). Should I do a RC2?
Second question: I just realized that the CHANGES file is incomplete, as
it describes a small fraction of the work done in the last year
(basically only the simplest tasks). Writing an accurate CHANGES file
would be tedious. What should we do? provide a pointer to JIRA or
release notes (but even those are incomplete), omit that file or leave
as-is? If we touch the CHANGES file, added to the previous item (javadoc
link fix), I guess that would be a case for a RC2?
Third question: in order to test the release, I wrote a trivial
separated Maven project which just download the SIS jars from the
staging repository and execute the SIS tests using the downloaded
artifacts. The intend is to verify that the JAR files in the staging
repository are not corrupted. Should I commit this test tool on SVN? If
so, would the following location be okay?
https://svn.apache.org/repos/asf/sis/release-test/maven
Martin
Le 09/08/13 01:31, Suresh Marru a écrit :
You rock Martin!!, This is a fine release, thank you for being patient to get
through all the release steps and document everything you did. Next time it
should be very trivial.
Once you also stage the binaries, i will verify the release and vote.
Suresh
On Aug 8, 2013, at 6:26 PM, Martin Desruisseaux
<[email protected]> wrote:
Discussion thread for vote on Apache SIS 0.3 release candidate.
If you have any questions or feedback or to post results of validating the
release, please reply to this thread. Once you verify the release, please post
your vote to the VOTE thread.
For reference, the Apache release guide -
http://www.apache.org/dev/release.html
Some tips to validate the release before you vote:
* Download the source files from compressed files and release tag and build
(which includes tests).
* Verify the distribution for the required LICENSE and NOTICE files
* Verify if all the staged files are signed and the signature is verifiable.
* Verify if the signing key in the project's KEYS file is hosted on a public
server
Thanks for your time in validating the release and voting,
Martin Desruisseaux
(On Behalf of SIS PMC)
