assign new version numbers to each project

[GoogleCodeExporter]

Now would be a great time to give new version numbers to each project.  One 
reason to split up the code into subprojects in the first place is to make it 
easier to communicate the maturity of different projects.  

Currently the projects either have a version of 0.9.9-SNAPSHOT or 
0.0.1-SNAPSHOT.  This is pretty useless.  Here's a listing of the projects with 
their current versions and a proposed version (I left out "SNAPSHOT" from each 
version number):

cleartk-chunker / 0.9.9 / 0.9.9
cleartk-examples / 0.0.1 / 0.5.0
cleartk-ml / 0.9.9 / 0.9.9
cleartk-ml-grmm / 0.0.1 / 0.5.0 (hasn't been used by anyone except Martin as 
far as I know, doesn't implement score method)
cleartk-ml-libsvm / 0.0.1 / 0.9.0 (we have some outstanding issues on this 
wrapper - in particular we should replace training with something java to avoid 
installation of a library)
cleartk-ml-mallet / 0.0.1 / 0.9.9
cleartk-ml-opennlp-maxent / 0.0.1 / 0.9.9
cleartk-ml-svmlight / 0.0.1 / 0.9.9
cleartk-named-entity / 0.0.1 / 0.1.0
cleartk-semantic-roles / 0.0.1 / 0.5.0
cleartk-syntax / 0.0.1 / 0.5.0
cleartk-syntax-opennlp / 0.0.1 / 0.8.0 (we have several outstanding issues on 
this wrapper)
cleartk-test-util / 0.6 / 1.0
cleartk-token / 0.0.1 / 0.7.0 (really needs a sentence segmenter)
cleartk-util / 0.0.1 / 0.7.0 (needs to have some classes cleaned out.)

The assumption is that those with a version of 0.9.9 are ready for a 1.0 
version very soon.  There are two main considerations that we should think 
about for a 1.0 stamp.  The first is some measure of completeness - does it do 
about as much as we think it should?  The second is some measure of approval - 
are we willing to support the project with some higher level of backwards 
compatibility?  This latter point is why I don't know what the version of 
cleartk-util should be.  There are a number of utility classes in there that I 
would rather get rid of and am not necessarily eager to support going forward.  
I'm not sure if this will be problematic for a project like cleartk-ml which is 
pretty much ready to go (except for lacking documentation) because it depends 
on cleartk-util.  I suppose it might actually make sense to let the version of 
cleartk-util lag behind for a while without holding up a 1.0 release of some of 
the other projects.  

Original issue reported on code.google.com by pvogren@gmail.com on 5 Jan 2011 at 10:30

[GoogleCodeExporter]

I left out cleartk-timeml on purpose because Steve likely has a better idea of 
what its version should be.

Original comment by pvogren@gmail.com on 5 Jan 2011 at 10:31

[GoogleCodeExporter]

cleartk-timeml should be in pretty good shape now. Mostly I see adding new 
classes (readers for the TempEval data, a TimeMLAnnotate that runs all TimeML 
annotators, etc.) and not much changing of old classes. So probably I'd say:

cleartk-timeml / 0.0.1 / 0.7.0

Original comment by steven.b...@gmail.com on 5 Jan 2011 at 10:46

[GoogleCodeExporter]

I'm working on this now.  Should commit changes within an hour.

Original comment by pvogren@gmail.com on 12 Jan 2011 at 4:14

[GoogleCodeExporter]

Ok - I know these version numbers are rather arbitrary - so feel free to change 
project version numbers as you see fit.  But I think this is a better starting 
point than what we had before this.  Here are the version numbers I assigned to 
all of the projects:

cleartk 0.5.0-SNAPSHOT
cleartk-jcasgen 0.5.0-SNAPSHOT
cleartk-test-util 0.9.9-SNAPSHOT
cleartk-util 0.7.0-SNAPSHOT
cleartk-ml 0.9.9-SNAPSHOT
cleartk-ml-grmm 0.5.0-SNAPSHOT
cleartk-ml-mallet 0.9.9-SNAPSHOT
cleartk-ml-opennlp-maxent 0.9.9-SNAPSHOT
cleartk-ml-svmlight 0.9.9-SNAPSHOT
cleartk-ml-libsvm 0.9.0-SNAPSHOT
cleartk-chunker 0.9.9-SNAPSHOT
cleartk-token 0.7.0-SNAPSHOT
cleartk-syntax 0.5.0-SNAPSHOT
cleartk-syntax-berkeley 0.0.1-SNAPSHOT
cleartk-syntax-opennlp 0.8.0-SNAPSHOT
cleartk-syntax-dependency 0.0.1-SNAPSHOT
cleartk-syntax-dependency-malt 0.5.0-SNAPSHOT
cleartk-semantic-roles 0.5.0-SNAPSHOT
cleartk-timeml 0.7.0-SNAPSHOT
cleartk-named-entity 0.1.0-SNAPSHOT
cleartk-examples 0.5.0-SNAPSHOT

It would be pretty easy to make a typo and not get all the versions updated so 
I double checked that everything looks good.  I also made sure that every 
instance of the dependency on cleartk-test-util has a scope of 'test' (I 
changed nearly every instance.)  

Original comment by pvogren@gmail.com on 12 Jan 2011 at 5:36

• Changed state: Fixed