Not a blocker, but I think that when we release new plugins on our Eclipse update site, we should leave the older files as they were, if they were not modified. (I checked the signature for a uima-as plugin, the uima-as deployeditor, on the test-eclipse-update-site, and found it was signed by Peter).
So, for instance, plugins etc. belonging to uimaj or uima-as would be left as is, and therefore, signed by the people who released them. Of course, I think you could implement this during the "release" copying, by only copying the changed part of the update site :-) -Marshall On 5/7/2013 7:12 AM, Peter Klügl wrote: > Hi, > > the second release candidate of the sandbox project Apache UIMA Ruta > v2.0.1 is ready for voting. > > Changes in RC2 vs RC1: > - updated composite repository is provided > - small bug fixed: UIMA-2875 > > Staging repository: > https://repository.apache.org/content/repositories/orgapacheuima-015/ > > SVN tag: > https://svn.apache.org/repos/asf/uima/sandbox/ruta/tags/ruta-2.0.1-rc2 > > Composite repository: > https://dist.apache.org/repos/dist/dev/uima/eclipse-update-site > > Archive with all sources: > http://people.apache.org/~pkluegl/uima-releases/ruta-2.0.1-rc2/ruta-2.0.1-source-release.zip > > The issues fixed are in the RELEASE_NOTES.html. > They can also be found here: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%20%222.0.1ruta%22%20AND%20component%20%3D%20ruta%20AND%20status%20in%20(Resolved%2C%20Closed)%20ORDER%20BY%20priority%20DESC > > ONLY FOR REVIEWING: > > Single eclipse update site > http://people.apache.org/~pkluegl/uima-releases/ruta-2.0.1-rc2/ruta-2.0.1 > > Documentation (pdf file): > http://people.apache.org/~pkluegl/uima-releases/ruta-2.0.1-rc2/tools.ruta.book.pdf > > > Please vote on release: > > [ ] +1 OK to release > [ ] 0 Don't care > [ ] -1 Not OK to release, because ... > > Thanks. > > Peter >
