Hi Jens, Nice to hear from you :-)
Here's the asf release-policy link: http://www.apache.org/legal/release-policy.html You will notice there's a distinction made between "binding" and non-binding votes. Both are important, but only the binding ones count toward the minimum of 3 +1 votes. Binding-ness happens when you become a PMC member :-) . Here's what you should check: 1) download the source-release package, and try to build it. Although you might think it's guaranteed to build, sometimes, it fails, due to some quirk in the local setup which is not properly handled, so it's worth trying. Doing the build also installs this in your local maven repo (assuming you did mvn clean install ). 2) Try using this version (either from what you built, and/or from unzipping the "binary" distribution and doing the minimal setup scripts) for any UIMA applications you might have. This is most valuable, because there's always things that the automated tests do not adequately cover. Also, you can observe if some aspect of "performance" (space and/or time) is significantly out-of whack with what you expect. 2a) Try installing the Eclipse plugins into a freshly-unzipped new Eclipse installation, and see if they continue to work properly. 3) [really for the PMC members to do] check the licenses and notices for conformance to Apache policy, and that artifacts are properly signed. It's really step 2/2a which is most valuable, in establishing an increasing level of confidence that the release candidate is viable. Thanks! -Marshall On 3/30/2017 11:23 AM, Jens Grivolla 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 > > On Thu, Mar 9, 2017 at 12:02 AM, Marshall Schor <[email protected]> wrote: > >> Hi everyone, >> >> We have two votes for release approval that have been up for a while (Ruta >> for >> almost a week). >> >> It would help our process if we could get these approved (or rejected) more >> rapidly, so I encourage upping your prioritization (if feasible) for >> checking >> and voting on the releases :-). >> >> Thanks! -Marshall >> >>
