Hi Martin et al,

You might already know this, but releases have to be made with latest version 
of java (java 7 update 25) which have addressed the recently exposed javadoc 
vulnerability as discussed in - http://www.kb.cert.org/vuls/id/225657

Suresh

On Jun 30, 2013, at 9:59 AM, Martin Desruisseaux 
<[email protected]> wrote:

> Hello Chris
> 
> The "-geoapi3.0" suffix in the version number was in anticipation for 
> (hopefully) future GeoAPI releases. The next GeoAPI release is likely to have 
> some incompatibilities, at least because JSR-275 has been rejected by JCP. So 
> I though about maintaining a SIS branch implementing "geoapi 3.0" together 
> with the trunk implementing later release. However we may try to handle that 
> using Maven classifier instead than putting a suffix in the version number. 
> So I'm fine with using a plain "0.3" version number on trunk.
> 
> On the release process, I think that we will have some additional work to do 
> in addition of "mvn release". For example, we need to update the 
> org.apache.sis.util.Version.SIS constant and a few places in the 
> documentation. I would also suggest to delete the FRA namespace on the 
> release branch (not trunk), since I didn't had the time yet to isolate the 
> French profile in a separated module.
> 
>    Martin
> 
> 
> Le 30/06/13 02:06, Mattmann, Chris A (398J) a écrit :
>> Guys,
>> 
>> For fun I just tried running mvn release:prepare to take advantage of the
>> Maven natural support for staging a release and preparing the RC. Again I'm
>> happy to be the release manager and get this out the door.
>> 
>> I found that our current versioning scheme (0.3-geoapi3.0) doesn't lend
>> itself
>> nicely to the maven release plugin. How wed are we to 0.3-geoapi3.0 as a
>> version
>> number? Would 0.3 be just as OK? If so I think that would let us use the
>> plugin
>> which really helps in e.g., staging a Maven repo (which will eventually be
>> needed
>> we can sync to the Central repository), and in preparing the RC.
>> 
>> Martin, thoughts? Can I change it to 0.3-SNAPSHOT (which will then be
>> released as
>> 0.3 and then transformed in 0.4-SNAPSHOT all by the plugin)?
>> 
>> Cheers,
>> Chris
> 

Reply via email to