Thanks for testing !

re: unsigned JARs - that's on purpose... See the website page on signing:
https://uima.apache.org/dev-eclipse-plugin-signing .  Any feedback on the
release process with signing is appreciated - this is the first time we're
trying this out.

One thing I could try is to "test-sign" the jars - I've done that already as an
experiment - it works, but Eclipse still says you're installing unsigned
artifacts - but then on the next dialog screen if you proceed, it says there are
artifacts signed using an untrusted certificate (the "test" signing).  So I
guess it's "working".  We'll know for sure once we try signing for real.

I'll look into the problems with the examples project.  I might do another RC
with no changes other that that and the fixes to the release notes.  (There's
another fix to the release notes to mention - about the latest changes stuck
into RC5 about the generification (if that's a word) of some of the JCas classes
for collections of things, and the addition of Java 8 capabilities like Streams
(and making them iterable) for those.

I'll hold off deciding on whether to re-spin an RC, hoping to get some more
testing :-) . 

If I do another RC, it will be a small diff from the current one, so the review
I hope will be minimal (after confirming it is a small delta).

Cheers. -Marshall

On 10/21/2017 4:25 PM, Richard Eckart de Castilho wrote:
> On 17.10.2017, at 17:40, Marshall Schor <[email protected]> wrote:
>> Please vote on release:
>>
>> [ ] +1 OK to release
>> [ ] 0 Don't care
>> [ ] -1 Not OK to release, because ...
>
> - checked for differences between SVN tag and sources ZIP: OK
> - build with Java 8 and empty Maven repo: OK
> - built uimaFIT v3-branch against beta: OK
> - built DKPro Core v3-branch against beta: OK
> - RELEASE_NOTES file: OK
>   - sometimes it is "Beta", sometimes "beta"
>   - mailing list URL is not a link
> - Trying to install plugins into Eclipse (from update site): OK
>   - However, Eclipse says that the JARs are unsigned! (features + plugins)
> - Importing the example project into Eclipse: FAIL
>   - The project imports ok, but some libraries in the project
>     have older versions than what is actually provided in the lib folder
> - Signature spot check: OK
>
> Well, all in all, it's probably good enough for a beta version
> which likely targets existing users rather than new users. But
> e.g. the example project should be fixed for the final release.
>
> [X] +1 OK to release
>
> General notes:
> - IMHO beta releases should be numbered (-beta-1, -beta-2, etc.)
> - The "Overview and Setup" document contains a section on 
>   changes from previous major versions. Would be nice to have 
>   such a section for UIMA 3. There is also a section for 
>   "the migration utility" (from IBM UIMA to Apache UIMA). 
>   This could be updated with info about the new utility
>   for v2 to v3 migration.
> - The V3 users guide looks very useful, but I need more time
>   to read it properly.
> - The getting-started guide still talks about fetching UIMA
>   from our old incubator website and that the Eclipse plugins
>   require Java 1.5.
>
> Cheers,
>
> -- Richard
>
>

Reply via email to