Hi Jens, I think there are four main areas to check for a vote:
1) license, copyright, and attribution: are all the NOTICE and LICENSE files ok? 2) documentation, README, fixed issues: is all that ok, updated, resolved? 3) package integrity: do the release packages/artifacts match the svn status, are they correctly signed? 4) build and compatibility: does it build on your system, does a product you might own still work with the new version? If all is ok for you, then a +1 is a good idea :) Cheers, -- Richard > On 30.03.2017, at 17:23, Jens Grivolla <[email protected]> wrote: > > Hi Marshall, > > I have never voted on a release so far. There's a page ( > http://uima.apache.org/release.html) with some information on releases, but > I'm not 100% sure what I would need to check to be able to meaningfully > vote. > > Is there any additional information on this? I suppose it means doing a > clean build on whatever platform I'm using (which should work since there > are automated builds that have already been done) and checking files such > as licenses, etc.? Does voting require additional testing (running our > pipelines on the new version, etc.)? > > Best, > Jens
