On 09/03/15 10:39, Stian Soiland-Reyes wrote:
-1: Release notes not updated. Everything else fine.
Thank you for the checking.
WARNING: Release notes are missing for 2.13.0
source/jena-2.13.0/jena-core/ReleaseNotes.txt
binaries/apache-jena-2.13.0/ReleaseNotes-Jena.txt
does NOT mention 2.12.1 or 2.13.0
Could you explain why that is a "-1", not "0" or even a conditional "+1"?
Release notes are useful to some people but it does not affect the
question of whether the release process has been executed correctly.
See 81 items:
http://s.apache.org/jena-2.13.0-jira
(Because of the bulk update of JIRA recently, I had to approximate by
limiting the creation date - 81 is an underestimate but close.)
We have two significant new modules. People are using them from
development. Creating this release has been a significant amount of
work with several "last minute" things delaying the release. Would
having an action plan to deal with the issue be sufficient for you?
Proposal:
If they are not going to be maintained, and we have JIRA which we do
use, I propose we retire all the ReleaseNotes*. They are not universal
across the modules anyway.
I hope that with that proposal and the VOTE with hashes, you can vote +1
on the next VOTE.
+ does everything work on Linux?
Tested on Ubuntu 14.10 x64
with
stain@biggie-utopic:/tmp/jena/people.apache.org/~andy/jena-2.13.0-rc1/source$
java -version
java version "1.7.0_75"
OpenJDK Runtime Environment (IcedTea 2.5.4) (7u75-2.5.4-1~utopic1)
OpenJDK 64-Bit Server VM (build 24.75-b04, mixed mode)
Not sure which 'everything' to test.. so I tested Fuseki 2 binary distribution.
The source-release and the build. AKA can it run the test suites.
Everything is is a convenience.
There is no ASF requirement for code to work perfectly - we, here at
Jena, do run the tests in the release process and I'd almost certainly
pull a release I was doing if it didn't pass tests but I can imagine a
situation where an urgent, specific matter needs addressing in a
release. We, project style, make sure that "master" green lines. It's
not the only possible style of project.
Defining prescriptively the acceptable levels is impossible, especially
as the scale of the project grows.
Anyone can do a release at any time (Apache culture) so in any project,
a release can conceivable have things that work and things that don't.
Someone may want a release to get specific bug fixes out. It is a
little harder, but not impossible, for a non-commiter to do a release.
The PMC's role is to verify the process has been executed correctly.
Andy
