If we release a 3.0.0 version, people will consider it stable, no matter
how you mark it. E.g. people looking at Maven Central won't even notice
that marker. I'm somewhat -1 for a 3.0.0 version at this point.

Why don't we release as 3.0.0-alpha-1?

Cheers,

-- Richard

> On 20.01.2017, at 15:26, Marshall Schor <[email protected]> wrote:
> 
> Yes, my current thought is to do a 3.0.0 release, and "mark" it in the 
> announce
> email and in the news and on the download page as being "alpha" level quality.
> 
> The intent is that it is an official release from an Apache point of view so
> many more people can try it out and give feedback :-), while acknowledging 
> that
> it's "early" in the quality-hardening cycle.
> 
> -Marshall
> 
> 
> On 1/20/2017 3:26 AM, Peter Klügl wrote:
>> Hi,
>> 
>> 
>> what happens when there are three +1 votes? Will there be a 3.0.0 release?
>> 
>> 
>> This would be of course OK for me, just asking. I am quite busy these
>> days, could take some time until I can review it.
>> 
>> 
>> (I assume that it could be a bit complicated/error-prone/undesirable to
>> change the version of the RC afterwards to alpha)
>> 
>> 
>> Best,
>> 
>> 
>> Peter
>> 
>> 
>> Am 19.01.2017 um 22:45 schrieb Marshall Schor:
>>> Hi,
>>> 
>>> Here's RC3.  The changes from RC2 involved JCasGen for the new built-in 
>>> types;
>>> they were missing from tables JCasGen uses to construct the proper imports.
>>> 
>>> -----------
>>> 
>>> If you happen to use JCas in your pipelines, and have JCas classes other 
>>> than
>>> the standard built-in ones, these classes will need to be regenerated or
>>> migrated.  If you use the Maven JCasGen plugin to generate the JCas classes 
>>> as
>>> part of your project's build, your good - nothing special need be done.
>>> 
>>> There is a migration tool, and there are scripts to run it, as well as 
>>> Eclipse
>>> launch configurations to run it.  The instructions for running this are in 
>>> a new
>>> documentation "book", part of the binary distribution (html and pdf) - it's
>>> called the Uima V3 User's Guide.
>>> 
>>> The guide also has an overview section which lists the new features of this
>>> release.  Many of these need more test cases written for them; I'm happy to
>>> mentor any volunteers who want to improve the testing  .
>>> 
>>> The list of changes in Jira: 
>>> 
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%203.0.0SDK-alpha
>>> 
>>> The source and binary zip/tars and the Eclipse update site are staged to
>>> 
>>> http://home.apache.org/~schor/uima-release-candidates/uv3-alpha-rc3/
>>> <http://home.apache.org/%7Eschor/uima-release-candidates/uv3-alpha-rc3/>
>>> 
>>> The Maven artifacts are here: 
>>> https://repository.apache.org/content/repositories/orgapacheuima-1116/
>>> 
>>> The SVN tags are here:
>>> https://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-3.0.0/
>>> 
>>> and for the Eclipse Update Site:
>>> http://home.apache.org/~schor/uima-release-candidates/uv3-alpha-rc3/eclipse-update-site/
>>> <http://home.apache.org/%7Eschor/uima-release-candidates/uv3-alpha-rc3/eclipse-update-site/>
>>> 
>>> Please vote on release:
>>> 
>>> [ ] +1 OK to release
>>> [ ] 0   Don't care
>>> [ ] -1 Not OK to release, because ...
>>> 
>>> Thanks.
>>> 
>>> -Marshall
>>> 
>> 
> 

Reply via email to