You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sis.apache.org by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov> on 2013/06/08 06:23:45 UTC

[DISCUSS] Apache SIS 0.3 release

Hey Guys,

I did release management in JIRA for 0.3, pushing all non fixed
issues off to 0.4 (after creating an 0.4 version in JIRA).
So far, we have: 30 / 30 issues solved for 0.3.

I say, we release and make an RC. Releasing is light-weight. If
we need to roll an 0.4 quickly or a 0.3.1 (patch release to 0.3)
we can do that too. No biggie.

What do you think Martin et al.?

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Joe White <wh...@gmail.com>.

+1 to a 0.3 release

Joe

On Saturday, June 8, 2013, Mattmann, Chris A (398J) wrote:

> Hey Guys,
>
> I did release management in JIRA for 0.3, pushing all non fixed
> issues off to 0.4 (after creating an 0.4 version in JIRA).
> So far, we have: 30 / 30 issues solved for 0.3.
>
> I say, we release and make an RC. Releasing is light-weight. If
> we need to roll an 0.4 quickly or a 0.3.1 (patch release to 0.3)
> we can do that too. No biggie.
>
> What do you think Martin et al.?
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov <javascript:;>
> WWW:  http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Martin Desruisseaux <ma...@geomatys.fr>.

Le 08/06/13 22:56, Travis L Pinney a écrit :
> Interesting. I updated maven using homebrew and it is working now. I was
> using 3.0.3 before.

It is good to know, thanks for sorting that out.

> I will use NetBeans then. It will be good to get it working with Eclipse
> because it is fairly popular. I just need to experiment a little more.

Well, I think you should use the IDE you feel the most comfortable with 
:-). (if we can fix the build)

     Martin

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Travis L Pinney <tr...@gmail.com>.

Interesting. I updated maven using homebrew and it is working now. I was
using 3.0.3 before.

I will use NetBeans then. It will be good to get it working with Eclipse
because it is fairly popular. I just need to experiment a little more.


Thanks!
Travis




On Sat, Jun 8, 2013 at 4:40 PM, Martin Desruisseaux <
martin.desruisseaux@geomatys.fr> wrote:

> Le 08/06/13 22:25, Travis L Pinney a écrit :
>
>  Thanks for fixing that. I was able to build everything from command line.
>>
>
> Cool :-)
>
>
>  Eclipse can run maven plugins. I am trying to figure out how to have it
>> run
>> that builder during a Junit run. It can sometimes be picky with
>> the configuration.
>>
>
> An alternative is to not run the plugins, and instead copy the "*.utf"
> files generated by Maven as if they were ordinary resources. I don't know
> how to achieve that with Eclipse however...
>
>
>  Also I see you have to do things like this
>>
>> mvn clean -Dmaven.version=3.0.4
>> mvn test -Dmaven.version=3.0.4
>>
>> Is there a reason to have a maven version be explicitly added to the
>> command line?
>>
>
> According Maven documentation, a ${maven.version} property is
> automatically provided by Maven since 3.0.4. However for a mysterious
> reason, it doesn't seem to be the case on the Jenkins machine, so I had to
> add them explicitly in the configuration. However I though they would not
> be needed on developer's local machine. Plain "mvn clean" or "mvn test"
> work for me. Isn't the case for you?
>
>
>  Also what text editor or ide do you use for java development?
>>
>
> I use NetBeans, mostly because I'm used to it. There is also Eclipse and
> IntelliJ fans around me. NetBeans can open Maven projects natively, but SIS
> also contains a "ide-project/NetBeans" directory with everything configured
> for those who wish. There is also a "ide-project/eclipse" directory for the
> same purpose, but I don't know if it is up-to-date...
>
>     Martin
>
>
>

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Martin Desruisseaux <ma...@geomatys.fr>.

Le 08/06/13 22:25, Travis L Pinney a écrit :
> Thanks for fixing that. I was able to build everything from command line.

Cool :-)

> Eclipse can run maven plugins. I am trying to figure out how to have it run
> that builder during a Junit run. It can sometimes be picky with
> the configuration.

An alternative is to not run the plugins, and instead copy the "*.utf" 
files generated by Maven as if they were ordinary resources. I don't 
know how to achieve that with Eclipse however...

> Also I see you have to do things like this
>
> mvn clean -Dmaven.version=3.0.4
> mvn test -Dmaven.version=3.0.4
>
> Is there a reason to have a maven version be explicitly added to the
> command line?

According Maven documentation, a ${maven.version} property is 
automatically provided by Maven since 3.0.4. However for a mysterious 
reason, it doesn't seem to be the case on the Jenkins machine, so I had 
to add them explicitly in the configuration. However I though they would 
not be needed on developer's local machine. Plain "mvn clean" or "mvn 
test" work for me. Isn't the case for you?

> Also what text editor or ide do you use for java development?

I use NetBeans, mostly because I'm used to it. There is also Eclipse and 
IntelliJ fans around me. NetBeans can open Maven projects natively, but 
SIS also contains a "ide-project/NetBeans" directory with everything 
configured for those who wish. There is also a "ide-project/eclipse" 
directory for the same purpose, but I don't know if it is up-to-date...

     Martin

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Travis L Pinney <tr...@gmail.com>.

Hi Martin,

Thanks for fixing that. I was able to build everything from command line.

Eclipse can run maven plugins. I am trying to figure out how to have it run
that builder during a Junit run. It can sometimes be picky with
the configuration.


Also I see you have to do things like this

mvn clean -Dmaven.version=3.0.4
mvn test -Dmaven.version=3.0.4


Is there a reason to have a maven version be explicitly added to the
command line? This confused me at first when I first tried to compile it.
Also what text editor or ide do you use for java development?


Thanks,
Travis



On Sat, Jun 8, 2013 at 4:13 PM, Martin Desruisseaux <
martin.desruisseaux@geomatys.fr> wrote:

> Hello Travis
>
> Le 08/06/13 13:10, Travis L Pinney a écrit :
>
>  It looks like the trunk has unit tests errors currently.
>>
>> https://builds.apache.org/job/**sis-trunk/181/<https://builds.apache.org/job/sis-trunk/181/>
>>
>
> Those errors were caused by the "sis-build-helper" plugin not being
> executed anymore after the pom.xml changes. It should be fixed now.
>
> A good way to check if everything go well is to execute the following
> command:
>
> unzip -ll core/sis-utility/target/sis-**utility-0.3-geoapi3.0-**
> SNAPSHOT.jar
>
> The output of this command shall not contains com/sun/* entry (excluded by
> the ant plugin), and shall contains some org/apache/sis/util/resources/***.utf
> entries (created by the sis-build-helper plugin). The NullPointerException
> were caused by the *.utf files being absent.
>
> However maybe it doesn't work well with Eclipse. Can Eclipse run Maven
> plugins?
>
>     Cheers
>     Martin
>
>

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Martin Desruisseaux <ma...@geomatys.fr>.

Hello Travis

Le 08/06/13 13:10, Travis L Pinney a écrit :
> It looks like the trunk has unit tests errors currently.
>
> https://builds.apache.org/job/sis-trunk/181/

Those errors were caused by the "sis-build-helper" plugin not being 
executed anymore after the pom.xml changes. It should be fixed now.

A good way to check if everything go well is to execute the following 
command:

unzip -ll core/sis-utility/target/sis-utility-0.3-geoapi3.0-SNAPSHOT.jar

The output of this command shall not contains com/sun/* entry (excluded 
by the ant plugin), and shall contains some 
org/apache/sis/util/resources/*.utf entries (created by the 
sis-build-helper plugin). The NullPointerException were caused by the 
*.utf files being absent.

However maybe it doesn't work well with Eclipse. Can Eclipse run Maven 
plugins?

     Cheers
     Martin

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Travis L Pinney <tr...@gmail.com>.

It looks like the trunk has unit tests errors currently.

https://builds.apache.org/job/sis-trunk/181/

I am working off of this revision now.

svn co https://svn.apache.org/repos/asf/sis/trunk -r 1490723


Even though eclipse is able to load the project correctly the unit tests
are failing.

One place that is causing a lot of problems in the unit tests is in

/sis-utility/src/main/java/org/apache/sis/util/resources/IndexedResourceBundle.java

and it is throwing a null pointer exception in the function ensureLoaded in
when resources == null

 // If we get a NullPointerException or ClassCastException here

// it would be a bug in the way we create the chain of parents.

    values = ((IndexedResourceBundle) parent).ensureLoaded(key);



Attached is the patch I am working off of. I am going to do some more
investigations.


Thanks,
Travis





On Sat, Jun 8, 2013 at 12:23 AM, Mattmann, Chris A (398J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> Hey Guys,
>
> I did release management in JIRA for 0.3, pushing all non fixed
> issues off to 0.4 (after creating an 0.4 version in JIRA).
> So far, we have: 30 / 30 issues solved for 0.3.
>
> I say, we release and make an RC. Releasing is light-weight. If
> we need to roll an 0.4 quickly or a 0.3.1 (patch release to 0.3)
> we can do that too. No biggie.
>
> What do you think Martin et al.?
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Travis L Pinney <tr...@gmail.com>.

I switched to NetBeans in the meantime. I think an incremental step would
be to create updated .project and .classpath files for the build that works
with Eclipse. The next step would be to get it to work when importing into
Eclipse from a checkout. After I get the shapefile patch out I am going to
look at Eclipse integration.


Thanks,
Travis



On Mon, Jun 17, 2013 at 2:44 PM, Adam Estrada <es...@gmail.com>wrote:

> Great Martin, thanks! I am also curious to see if the issues @tlpinney was
> having with the build were sorted out. I believe it was a matter of
> building within Eclipse or from the command line using straight Maven.
>
>
> On Mon, Jun 17, 2013 at 11:50 AM, Martin Desruisseaux <
> martin.desruisseaux@geomatys.fr> wrote:
>
> > Hello all
> >
> > There is the current development status before a possible 0.3 release:
> >
> >  * I'm in the process of putting a safety guard against a possible
> >    infinite recursivity in metadata equals, hashCode() and toString()
> >    methods. This is the very last bug on my "todo" list that I wanted
> >    to fix prior 0.3 release.
> >  * I still have to port the XML tests. I estimate this work to
> >    approximatively 3 days. I noticed some anomalies, like the
> >    declaration of the "http://www.cnig.gouv.fr/2005/**fra<
> http://www.cnig.gouv.fr/2005/fra>"
> > schema in the
> >    XML produced by the command line. That schema shall be declared only
> >    for the French profile of metadata, not by default. This will
> >    hopefully be a minor fix.
> >
> >
> >     Martin
> >
> >
>

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Martin Desruisseaux <ma...@geomatys.fr>.

Hello Adam

Le 17/06/13 20:44, Adam Estrada a écrit :
> I am also curious to see if the issues @tlpinney was
> having with the build were sorted out. I believe it was a matter of
> building within Eclipse or from the command line using straight Maven.

It was an issue with Eclipse - since I'm not familiar with that 
environment, I don't know how to maintain its configuration.

Straight Maven on the command line shall always work. Actually I tend to 
consider straight Maven as the reference. I see Eclipse/NetBeans or 
other IDE configuration as conveniences only, while straight Maven 
should work in all configuration. Actually I suggest to adopt as a 
policy to always commit on SVN only after a successful "mvn install". 
Does is sound okay?

     Martin

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Adam Estrada <es...@gmail.com>.

Great Martin, thanks! I am also curious to see if the issues @tlpinney was
having with the build were sorted out. I believe it was a matter of
building within Eclipse or from the command line using straight Maven.


On Mon, Jun 17, 2013 at 11:50 AM, Martin Desruisseaux <
martin.desruisseaux@geomatys.fr> wrote:

> Hello all
>
> There is the current development status before a possible 0.3 release:
>
>  * I'm in the process of putting a safety guard against a possible
>    infinite recursivity in metadata equals, hashCode() and toString()
>    methods. This is the very last bug on my "todo" list that I wanted
>    to fix prior 0.3 release.
>  * I still have to port the XML tests. I estimate this work to
>    approximatively 3 days. I noticed some anomalies, like the
>    declaration of the "http://www.cnig.gouv.fr/2005/**fra<http://www.cnig.gouv.fr/2005/fra>"
> schema in the
>    XML produced by the command line. That schema shall be declared only
>    for the French profile of metadata, not by default. This will
>    hopefully be a minor fix.
>
>
>     Martin
>
>

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Adam Estrada <es...@gmail.com>.

Thanks Martin!

A


On Thu, Jun 27, 2013 at 6:54 PM, Martin Desruisseaux <
martin.desruisseaux@geomatys.fr> wrote:

> Hello all
>
> Many thanks Suresh for the wiki and the INFRA jira task. I started to read
> the wiki, but will need to read it more attentively again.
>
> I have 4 remaining JUnit test classes that I wish to port, and I'm done.
>
>     Martin
>
>
>
> Le 27/06/13 03:53, Suresh Marru a écrit :
>
>  I just noticed that svnpubsub for release publishing is not setup. So I
>> requested the same - https://issues.apache.org/**jira/browse/INFRA-6468<https://issues.apache.org/jira/browse/INFRA-6468>
>>
>> As part of this setup, we will be asked to copy a KEYS file and a release
>> artifact so the setup can be complete. I will use the 0.2 release when
>> INFRA asks for it.
>>
>> Suresh
>>
>
>

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Martin Desruisseaux <ma...@geomatys.fr>.

Hello all

Many thanks Suresh for the wiki and the INFRA jira task. I started to 
read the wiki, but will need to read it more attentively again.

I have 4 remaining JUnit test classes that I wish to port, and I'm done.

     Martin



Le 27/06/13 03:53, Suresh Marru a écrit :
> I just noticed that svnpubsub for release publishing is not setup. So I requested the same - https://issues.apache.org/jira/browse/INFRA-6468
>
> As part of this setup, we will be asked to copy a KEYS file and a release artifact so the setup can be complete. I will use the 0.2 release when INFRA asks for it.
>
> Suresh

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Suresh Marru <sm...@apache.org>.

I just noticed that svnpubsub for release publishing is not setup. So I requested the same - https://issues.apache.org/jira/browse/INFRA-6468

As part of this setup, we will be asked to copy a KEYS file and a release artifact so the setup can be complete. I will use the 0.2 release when INFRA asks for it. 

Suresh

On Jun 26, 2013, at 9:42 PM, Suresh Marru <sm...@apache.org> wrote:

> I just cloned Airavata instructions to SIS website. Can we work from it and customize them for SIS? Here is the draft - http://sis.apache.org/release-management.html
> 
> Thanks,
> Suresh
> 
> On Jun 26, 2013, at 9:08 PM, Suresh Marru <sm...@apache.org> wrote:
> 
>> Hi Martin & Adam,
>> 
>> No worries on this one, we all learn through the process and I learned the hard way. As Chris pointed out to earlier on this thread, one of the important aspect in ASF is getting the releases. We can informally roll-out RC's for testing. But before we can vote on a release, that has to be done on cryptographically signed artifacts. Also there are constraints on where the signed KEYS are located and so forth. Also, we need to properly follow the way we distribute release notes and also publish artifacts to nexus repo so downstream users can get them. 
>> 
>> I will be happy to help put together some detailed instructions on the website so we will have them for future. Here is a stating point on Airavata release management - http://airavata.apache.org/development/release-management.html 
>> 
>> Suresh
>> 
>> On Jun 26, 2013, at 7:34 PM, Adam Estrada <es...@gmail.com> wrote:
>> 
>>> OK guys...moving this to a [VOTE] thread...
>>> 
>>> A
>>> 
>>> On Jun 25, 2013, at 3:54 PM, Travis L Pinney wrote:
>>> 
>>>> +1 for Friday release
>>>> 
>>>> 
>>>> On Tue, Jun 25, 2013 at 3:47 PM, Martin Desruisseaux <
>>>> martin.desruisseaux@geomatys.fr> wrote:
>>>> 
>>>>> Thanks Adam and Chris
>>>>> 
>>>>> So Friday would be RC 1. I will read more attentively the release process
>>>>> documentation tomorrow. Thanks for the link and for your help
>>>>> 
>>>>> Martin
>>>>> 
>>>>> 
>>>>> Le 25/06/13 20:37, Adam Estrada a écrit :
>>>>> 
>>>>> That sounds good Martin! I will work with you and Mattmann on the release
>>>>>> process. This is very exciting!!!
>>>>>> 
>>>>>> 
>>>>>> On Tue, Jun 25, 2013 at 2:27 PM, Martin Desruisseaux <
>>>>>> martin.desruisseaux@geomatys.**fr <ma...@geomatys.fr>>
>>>>>> wrote:
>>>>>> 
>>>>>> Hello all
>>>>>>> 
>>>>>>> Unless I spot a significant problem, I think that I could fix tomorrow as
>>>>>>> my last testing day. I could also eventually process to the following
>>>>>>> minor
>>>>>>> changes on Thursday:
>>>>>>> 
>>>>>>> * Replace LatLon by DirectPosition2D
>>>>>>> * Replace LatLonRect by Envelope2D
>>>>>>> 
>>>>>>> The two above classes were defined in SIS 0.2. The proposed replacement
>>>>>>> are implementations of OGC/ISO objects.
>>>>>>> 
>>>>>>> We could target a release on Friday if peoples are okay with that.
>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> 
>

Re: [DISCUSS] Apache SIS 0.3 release

Posted by Suresh Marru <sm...@apache.org>.

I just cloned Airavata instructions to SIS website. Can we work from it and customize them for SIS? Here is the draft - http://sis.apache.org/release-management.html

Thanks,
Suresh

On Jun 26, 2013, at 9:08 PM, Suresh Marru <sm...@apache.org> wrote:

> Hi Martin & Adam,
> 
> No worries on this one, we all learn through the process and I learned the hard way. As Chris pointed out to earlier on this thread, one of the important aspect in ASF is getting the releases. We can informally roll-out RC's for testing. But before we can vote on a release, that has to be done on cryptographically signed artifacts. Also there are constraints on where the signed KEYS are located and so forth. Also, we need to properly follow the way we distribute release notes and also publish artifacts to nexus repo so downstream users can get them. 
> 
> I will be happy to help put together some detailed instructions on the website so we will have them for future. Here is a stating point on Airavata release management - http://airavata.apache.org/development/release-management.html 
> 
> Suresh
> 
> On Jun 26, 2013, at 7:34 PM, Adam Estrada <es...@gmail.com> wrote:
> 
>> OK guys...moving this to a [VOTE] thread...
>> 
>> A
>> 
>> On Jun 25, 2013, at 3:54 PM, Travis L Pinney wrote:
>> 
>>> +1 for Friday release
>>> 
>>> 
>>> On Tue, Jun 25, 2013 at 3:47 PM, Martin Desruisseaux <
>>> martin.desruisseaux@geomatys.fr> wrote:
>>> 
>>>> Thanks Adam and Chris
>>>> 
>>>> So Friday would be RC 1. I will read more attentively the release process
>>>> documentation tomorrow. Thanks for the link and for your help
>>>> 
>>>>  Martin
>>>> 
>>>> 
>>>> Le 25/06/13 20:37, Adam Estrada a écrit :
>>>> 
>>>> That sounds good Martin! I will work with you and Mattmann on the release
>>>>> process. This is very exciting!!!
>>>>> 
>>>>> 
>>>>> On Tue, Jun 25, 2013 at 2:27 PM, Martin Desruisseaux <
>>>>> martin.desruisseaux@geomatys.**fr <ma...@geomatys.fr>>
>>>>> wrote:
>>>>> 
>>>>> Hello all
>>>>>> 
>>>>>> Unless I spot a significant problem, I think that I could fix tomorrow as
>>>>>> my last testing day. I could also eventually process to the following
>>>>>> minor
>>>>>> changes on Thursday:
>>>>>> 
>>>>>> * Replace LatLon by DirectPosition2D
>>>>>> * Replace LatLonRect by Envelope2D
>>>>>> 
>>>>>> The two above classes were defined in SIS 0.2. The proposed replacement
>>>>>> are implementations of OGC/ISO objects.
>>>>>> 
>>>>>> We could target a release on Friday if peoples are okay with that.
>>>>>> 
>>>>> 
>>>> 
>> 
>

Re: [DISCUSS] Apache SIS 0.3 release - versions

Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.

Thanks Martin. +1 to punting and solving this problem later,
but not letting it block the 0.3 release.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++






-----Original Message-----
From: Martin Desruisseaux <ma...@geomatys.fr>
Organization: Geomatys
Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
Date: Monday, July 1, 2013 2:31 AM
To: "dev@sis.apache.org" <de...@sis.apache.org>
Subject: Re: [DISCUSS] Apache SIS 0.3 release - versions

>Hello all
>
>I replaced the "0.3-geoapi3.0" version number by a plain "0.3" on trunk.
>We may try to manage the branches using Maven classifier instead. Maven
>documentation said:
>
>    As a motivation for this element, consider for example a project
>    that offers an artifact targeting JRE 1.5 but at the same time also
>    an artifact that still supports JRE 1.4. The first artifact could be
>    equipped with the classifier jdk15 and the second one with jdk14
>    such that clients can choose which one to use.
>
>Which is pretty close to our case. However the issue that I'm facing is
>that classifier applies only to JAR files; the pom.xml files have
>identical names regardless of classifier, which implies that our pom.xml
>need to be identical on all branches if we want to avoid chaotic
>behaviour when two branches are used on the same machine. I don't know
>yet how to do that, even with Maven profiles. Problem is: if a project
>declares a SIS dependency with classifier A, how to ensure that the
>transitive SIS dependencies also use classifier A? Does a Maven property
>exist for telling us which classifier was used by the project that
>imported us?
>
>I think that we can ignore this problem for now, and keep the "0.3-jdk6"
>and "0.3-jdk7" version number for the JDK6 and JDK7 branches for now,
>which shouldn't hurt since they are not released. However I think that
>we will probably need to find a solution if we release a GeoAPI 3.1 or
>4.0 standard, since I would like to release both a "SIS for GeoAPI 3.0"
>and "SIS for GeoAPI 3.1/4.0" at that time.
>
>     Martin
>

Re: [DISCUSS] Apache SIS 0.3 release - versions

Posted by Martin Desruisseaux <ma...@geomatys.fr>.

Hello all

I replaced the "0.3-geoapi3.0" version number by a plain "0.3" on trunk. 
We may try to manage the branches using Maven classifier instead. Maven 
documentation said:

    As a motivation for this element, consider for example a project
    that offers an artifact targeting JRE 1.5 but at the same time also
    an artifact that still supports JRE 1.4. The first artifact could be
    equipped with the classifier jdk15 and the second one with jdk14
    such that clients can choose which one to use.

Which is pretty close to our case. However the issue that I'm facing is 
that classifier applies only to JAR files; the pom.xml files have 
identical names regardless of classifier, which implies that our pom.xml 
need to be identical on all branches if we want to avoid chaotic 
behaviour when two branches are used on the same machine. I don't know 
yet how to do that, even with Maven profiles. Problem is: if a project 
declares a SIS dependency with classifier A, how to ensure that the 
transitive SIS dependencies also use classifier A? Does a Maven property 
exist for telling us which classifier was used by the project that 
imported us?

I think that we can ignore this problem for now, and keep the "0.3-jdk6" 
and "0.3-jdk7" version number for the JDK6 and JDK7 branches for now, 
which shouldn't hurt since they are not released. However I think that 
we will probably need to find a solution if we release a GeoAPI 3.1 or 
4.0 standard, since I would like to release both a "SIS for GeoAPI 3.0" 
and "SIS for GeoAPI 3.1/4.0" at that time.

     Martin

Re: [DISCUSS] Apache SIS 0.3 release - versions

Posted by Martin Desruisseaux <ma...@geomatys.fr>.

Hello Suresh

Le 30/06/13 17:17, Suresh Marru a écrit :
> 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

Thanks. It sound like that Java 6 after update 45 are fine too (I have 
update 51 on my machine).

     Martin

Re: [DISCUSS] Apache SIS 0.3 release - versions

Posted by Suresh Marru <sm...@apache.org>.

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 <ma...@geomatys.fr> 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
>

Re: [DISCUSS] Apache SIS 0.3 release - versions

Posted by Martin Desruisseaux <ma...@geomatys.fr>.

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

Re: [DISCUSS] Apache SIS 0.3 release - one minor licensing issue

Posted by Adam Estrada <es...@gmail.com>.

Me too!


On Mon, Jul 1, 2013 at 7:57 PM, Mattmann, Chris A (398J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> +1 from me.
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>
>
> -----Original Message-----
> From: Martin Desruisseaux <ma...@geomatys.fr>
> Organization: Geomatys
> Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
> Date: Monday, July 1, 2013 8:29 AM
> To: "dev@sis.apache.org" <de...@sis.apache.org>
> Subject: Re: [DISCUSS] Apache SIS 0.3 release - one minor licensing issue
>
> >The following file:
> >
> >http://svn.apache.org/repos/asf/sis/trunk/src/main/docbook/book.xsl
> >
> >contains parts which have been copied from
> >http://docbook.sourceforge.net, then edited. The license of the docbook
> >project seems unclear to me, but it doesn't seem to be Apache.
> >Consequently I didn't added Apache License header on that file, and I
> >presume that we shall not distribute it. Given that this file is used
> >only for generating the "developer guide" page, and given that that page
> >has not yet been translated to English, I presume that excluding those
> >files from the release is what most peoples would expect anyway.
> >
> >In the future, we are considering to convert the docbook files to HTML5.
> >This would get ride of that book.xsl file.
> >
> >     Martin
> >
>
>

Re: [DISCUSS] Apache SIS 0.3 release - one minor licensing issue

Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.

+1 from me.

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++






-----Original Message-----
From: Martin Desruisseaux <ma...@geomatys.fr>
Organization: Geomatys
Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
Date: Monday, July 1, 2013 8:29 AM
To: "dev@sis.apache.org" <de...@sis.apache.org>
Subject: Re: [DISCUSS] Apache SIS 0.3 release - one minor licensing issue

>The following file:
>
>http://svn.apache.org/repos/asf/sis/trunk/src/main/docbook/book.xsl
>
>contains parts which have been copied from
>http://docbook.sourceforge.net, then edited. The license of the docbook
>project seems unclear to me, but it doesn't seem to be Apache.
>Consequently I didn't added Apache License header on that file, and I
>presume that we shall not distribute it. Given that this file is used
>only for generating the "developer guide" page, and given that that page
>has not yet been translated to English, I presume that excluding those
>files from the release is what most peoples would expect anyway.
>
>In the future, we are considering to convert the docbook files to HTML5.
>This would get ride of that book.xsl file.
>
>     Martin
>

Re: [DISCUSS] Apache SIS 0.3 release - one minor licensing issue

Posted by Martin Desruisseaux <ma...@geomatys.fr>.

The following file:

http://svn.apache.org/repos/asf/sis/trunk/src/main/docbook/book.xsl

contains parts which have been copied from 
http://docbook.sourceforge.net, then edited. The license of the docbook 
project seems unclear to me, but it doesn't seem to be Apache. 
Consequently I didn't added Apache License header on that file, and I 
presume that we shall not distribute it. Given that this file is used 
only for generating the "developer guide" page, and given that that page 
has not yet been translated to English, I presume that excluding those 
files from the release is what most peoples would expect anyway.

In the future, we are considering to convert the docbook files to HTML5. 
This would get ride of that book.xsl file.

     Martin

Re: [DISCUSS] Apache SIS 0.3 release - versions

Posted by Martin Desruisseaux <ma...@geomatys.fr>.

Le 01/07/13 15:52, Suresh Marru a écrit :
> Yes this is exactly what I was referring. Great!. I will see if I can 
> add the headers it is complaining today.

Thanks I appreciate! But I already started to add the easy ones. However 
there two cases I'm not sure what to do about:

1) All files in ide-project/resources-links/ should be ignored, since 
this is a convenience symbolic link for NetBeans users only (ignored by 
Maven). I will try to remove those links and use an other approach instead.

2) ide-project/NetBeans/nbproject/build-impl.xml and genfiles.properties 
and automatically generated files for NetBeans users only. I guess that 
we are better to not edit those files...

3) All *.apt files: do you know if there is any template for Apache 
License header in those files?

     Martin

Re: [DISCUSS] Apache SIS 0.3 release - versions

Posted by Suresh Marru <sm...@apache.org>.

Hi Martin,

On Jul 1, 2013, at 9:47 AM, Martin Desruisseaux <ma...@geomatys.fr> wrote:

> Hello Suresh
> 
> Le 30/06/13 02:18, Suresh Marru a écrit :
>> I think rat check have to be part of release steps which saves significant time in verifying the license header.
> Does the Maven generated RAT report provides the required information?
> 
> https://builds.apache.org/job/sis-trunk/site/rat-report.html

Yes this is exactly what I was referring. Great!. I will see if I can add the headers it is complaining today.

> 
>> Also, I suggest to use different assembly for source and binaries so license and notice files can be captured separately and bundled accordingly.
> I agree for 2 separated download files, one for source and one for binary. Is that the proposal?

Yes, I would propose to use the separate assembly, I am trying not to step onto you and Chris, but if needed, I can help out with these.

Suresh

> 
>    Martin
>

Re: [DISCUSS] Apache SIS 0.3 release - versions

Posted by Martin Desruisseaux <ma...@geomatys.fr>.

Hello Suresh

Le 30/06/13 02:18, Suresh Marru a écrit :
> I think rat check have to be part of release steps which saves significant time in verifying the license header.
Does the Maven generated RAT report provides the required information?

https://builds.apache.org/job/sis-trunk/site/rat-report.html

> Also, I suggest to use different assembly for source and binaries so license and notice files can be captured separately and bundled accordingly.
I agree for 2 separated download files, one for source and one for 
binary. Is that the proposal?

     Martin

Re: [DISCUSS] Apache SIS 0.3 release - versions

Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.

Hey Suresh,

Thanks, I'll happily get this going and happy to step away once
we show how it's done and hopefully Martin, Adam, or anyone else
can do it after doing it once.

Here's what I see needs to get done (and honestly not by committee,
but by some crazy person with the cycles to just do it)

1. Update release version to be numeric so it works with mvn
release:prepare
2. Add RAT (not a blocker, but a nicety since we have made 2 incubating
releases
so far the changes of having introduced some "bad" dependency IMO are
fairly
small).
3. Publish RC to Nexus
4. Stage RC to dev dist area or p.a.o (both methods are still supported
per latest
infra docs)
5. Call VOTE

I'll see if I can get closer on the above today.

Cheers,
Chris



++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++






-----Original Message-----
From: Suresh Marru <sm...@apache.org>
Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
Date: Saturday, June 29, 2013 5:18 PM
To: "dev@sis.apache.org" <de...@sis.apache.org>
Subject: Re: [DISCUSS] Apache SIS 0.3 release - versions

>Hi Chris,
>
>I was planning to either help Martin or volunteer myself to be the RM.
>But if you have cycles, thats really nice. Few more thoughts on improving
>the release process:
>
>I think rat check have to be part of release steps which saves
>significant time in verifying the license header. Also, I suggest to use
>different assembly for source and binaries so license and notice files
>can be captured separately and bundled accordingly.
>
>I think once we stream line the release process (and automate as much as
>possible) and document clearly the steps, subsequent releases will be
>very easy and painless.
>
>Cheers,
>Suresh
>
>On Jun 29, 2013, at 8:06 PM, "Mattmann, Chris A (398J)"
><ch...@jpl.nasa.gov> wrote:
>
>> 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
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW:  http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
>> 
>> 
>> 
>> 
>> 
>> -----Original Message-----
>> From: Adam Estrada <es...@gmail.com>
>> Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
>> Date: Saturday, June 29, 2013 4:57 PM
>> To: "dev@sis.apache.org" <de...@sis.apache.org>
>> Subject: Re: [DISCUSS] Apache SIS 0.3 release - finished porting the
>>tests
>> 
>>> Thanks a lot Chris and Martin. Just want to note that SIS also builds
>>> without any problems on Windows 8 64bit.
>>> 
>>> D:\Apache\SIS>mvn --version
>>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
>>>2013-02-19
>>> 08:51:
>>> 28-0500)
>>> Java version: 1.7.0_15, vendor: Oracle Corporation
>>> Java home: C:\Program Files\Java\jdk1.7.0_15\jre
>>> Default locale: en_US, platform encoding: Cp1252
>>> OS name: "windows 8", version: "6.2", arch: "amd64", family: "windows"
>>> 
>>> [INFO] Writing OBR metadata
>>> [INFO]
>>> 
>>>------------------------------------------------------------------------
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Apache SIS ........................................ SUCCESS
>>> [6.660s]
>>> [INFO] Apache SIS core modules ........................... SUCCESS
>>> [0.051s]
>>> [INFO] Apache SIS build helper ........................... SUCCESS
>>> [6.250s]
>>> [INFO] Apache SIS utilities .............................. SUCCESS
>>> [17.197s]
>>> [INFO] Apache SIS metadata ............................... SUCCESS
>>> [5.145s]
>>> [INFO] Apache SIS referencing ............................ SUCCESS
>>> [1.145s]
>>> [INFO] Apache SIS storage ................................ SUCCESS
>>> [0.091s]
>>> [INFO] Apache SIS common storage ......................... SUCCESS
>>> [1.664s]
>>> [INFO] Apache SIS NetCDF storage ......................... SUCCESS
>>> [17.884s]
>>> [INFO] Apache SIS applications ........................... SUCCESS
>>> [0.072s]
>>> [INFO] Apache SIS web services layer ..................... SUCCESS
>>> [4.805s]
>>> [INFO] Apache SIS console ................................ SUCCESS
>>> [0.988s]
>>> [INFO]
>>> 
>>>------------------------------------------------------------------------
>>> [INFO] BUILD SUCCESS
>>> [INFO]
>>> 
>>>------------------------------------------------------------------------
>>> [INFO] Total time: 1:03.687s
>>> [INFO] Finished at: Sat Jun 29 19:52:42 EDT 2013
>>> [INFO] Final Memory: 43M/275M
>>> [INFO]
>>> 
>>>------------------------------------------------------------------------
>>> 
>>> 
>>> On Sat, Jun 29, 2013 at 1:14 AM, Mattmann, Chris A (398J) <
>>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>> 
>>>> Hi Martin,
>>>> 
>>>> -----Original Message-----
>>>> 
>>>> From: Martin Desruisseaux <ma...@geomatys.fr>
>>>> Organization: Geomatys
>>>> Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
>>>> Date: Friday, June 28, 2013 3:27 PM
>>>> To: "dev@sis.apache.org" <de...@sis.apache.org>
>>>> Subject: Re: [DISCUSS] Apache SIS 0.3 release - finished porting the
>>>> tests
>>>> 
>>>>> Hello all
>>>>> 
>>>>> I finished porting the tests that I wanted. I think that the test
>>>>> coverage is still insufficient, but we will hopefully start receiving
>>>>> feedbacks from users.
>>>> 
>>>> woot! OK that sounds great.
>>>> 
>>>>> 
>>>>> I would appreciate if some volunteers could try "mvn install" on
>>>>>their
>>>>> machine. Some methods are locale or timezone sensitive. I tried to
>>>>> protect the test cases against timezone changes, but I may have
>>>>>forgot
>>>>> some cases.
>>>> 
>>>> OS: Mac OS X 10.8.4
>>>> MacBook Air Intel i7
>>>> Java Version:
>>>> [chipotle:~/tmp/apache-curator-2.1.0/apache-curator-2.1.0-incubating]
>>>> mattmann% java -version
>>>> java version "1.6.0_45"
>>>> Java(TM) SE Runtime Environment (build 1.6.0_45-b06-451-11M4406)
>>>> Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01-451, mixed mode)
>>>> [chipotle:~/tmp/apache-curator-2.1.0/apache-curator-2.1.0-incubating]
>>>> mattmann%
>>>> 
>>>> Maven Version:
>>>> 
>>>> 
>>>> [chipotle:~/tmp/apache-curator-2.1.0/apache-curator-2.1.0-incubating]
>>>> mattmann% mvn --version
>>>> Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800)
>>>> Maven home: /usr/share/maven
>>>> Java version: 1.6.0_45, vendor: Apple Inc.
>>>> Java home: 
>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>>> Default locale: en_US, platform encoding: MacRoman
>>>> OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"
>>>> [chipotle:~/tmp/apache-curator-2.1.0/apache-curator-2.1.0-incubating]
>>>> mattmann%
>>>> 
>>>> 
>>>> Test results
>>>> 
>>>> All tests pass.
>>>> 
>>>> [INFO] Writing OBR metadata
>>>> [INFO]
>>>> 
>>>>-----------------------------------------------------------------------
>>>>-
>>>> [INFO] Reactor Summary:
>>>> [INFO]
>>>> [INFO] Apache SIS ........................................ SUCCESS
>>>> [2.521s]
>>>> [INFO] Apache SIS core modules ........................... SUCCESS
>>>> [0.743s]
>>>> [INFO] Apache SIS build helper ........................... SUCCESS
>>>> [5.010s]
>>>> [INFO] Apache SIS utilities .............................. SUCCESS
>>>> [28.158s]
>>>> [INFO] Apache SIS metadata ............................... SUCCESS
>>>> [8.591s]
>>>> [INFO] Apache SIS referencing ............................ SUCCESS
>>>> [2.432s]
>>>> [INFO] Apache SIS storage ................................ SUCCESS
>>>> [0.181s]
>>>> [INFO] Apache SIS common storage ......................... SUCCESS
>>>> [3.575s]
>>>> [INFO] Apache SIS NetCDF storage ......................... SUCCESS
>>>> [1:21.364s]
>>>> [INFO] Apache SIS applications ........................... SUCCESS
>>>> [0.084s]
>>>> [INFO] Apache SIS web services layer ..................... SUCCESS
>>>> [3.465s]
>>>> [INFO] Apache SIS console ................................ SUCCESS
>>>> [1.684s]
>>>> [INFO]
>>>> 
>>>>-----------------------------------------------------------------------
>>>>-
>>>> [INFO] BUILD SUCCESS
>>>> [INFO]
>>>> 
>>>>-----------------------------------------------------------------------
>>>>-
>>>> [INFO] Total time: 2:19.080s
>>>> [INFO] Finished at: Fri Jun 28 21:48:58 PDT 2013
>>>> [INFO] Final Memory: 35M/88M
>>>> [INFO]
>>>> 
>>>>-----------------------------------------------------------------------
>>>>-
>>>> [chipotle:~/src/sis/trunk] mattmann%
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> 
>>>>> I will try to read Suresh's instructions this weekend. Some tasks
>>>>>that
>>>>> popup from my heads before to make a release are:
>>>>> 
>>>>> * Update the web site and the wiki (the last "recent report" is 14
>>>>>   months old)
>>>>> * Re-organize the "getting started" instructions
>>>> 
>>>> This can be done post release.
>>>> 
>>>>> * Review pending JIRA tasks
>>>> 
>>>> Pre release, I will help with this.
>>>> 
>>>>> * Review javadoc
>>>> 
>>>> Post release.
>>>> 
>>>>> * Decide on the content of the distributed ZIP files.
>>>> 
>>>> We can do this now. Apache simply releases source, that's what we VOTE
>>>> on.
>>>> Everything else is "convenience" binaries, provided by the Release
>>>> Manager
>>>> or project at their own desire.
>>>> 
>>>>> 
>>>>> 
>>>>> I don't know yet if there is Apache recommendation about the content
>>>>>of
>>>>> the distributed ZIP files. One proposal could be to provide 3
>>>>>separated
>>>>> files: binary, javadoc and source code. The content of the ZIP file
>>>>>for
>>>>> the binary could be:
>>>>> 
>>>>>  README
>>>>>  LICENSE
>>>>>  NOTICE
>>>>>  bin/sis
>>>>>  bin/sis.bat
>>>>>  bin/sis.jar
>>>>>  etc/logging.properties
>>>>> 
>>>>> 
>>>>> where "sis" and "sis.bat" would be convenience shell scripts (Unix
>>>>>and
>>>>> Windows respectively) for invoking "sis.jar", and "etc" would be any
>>>>> configuration file (only an optional "logging.properties" for now).
>>>> 
>>>> I would say we simply:
>>>> 
>>>> 1. Create tag
>>>> 2. tar cvzf apache-sis-0.3-incubating-src.tar.gz tag
>>>> 3. asc, md5 and sha1 that
>>>> 4. put up artifacts from 2-3 and for VOTE'ing
>>>> 
>>>> Shouldn't be much harder than that.
>>>> 
>>>>> 
>>>>> Is there any though?
>>>> 
>>>> See above..
>>>> 
>>>> Cheers,
>>>> Chris
>>>> 
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Chris Mattmann, Ph.D.
>>>> Senior Computer Scientist
>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>>> Office: 171-266B, Mailstop: 171-246
>>>> Email: chris.a.mattmann@nasa.gov
>>>> WWW:  http://sunset.usc.edu/~mattmann/
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Adjunct Assistant Professor, Computer Science Department
>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 
>>>> 
>>>> 
>>>>> 
>>>>> 
>>>>> Le 27/06/13 03:08, Suresh Marru a écrit :
>>>>>> Hi Martin & Adam,
>>>>>> 
>>>>>> No worries on this one, we all learn through the process and I
>>>> learned
>>>>>> the hard way. As Chris pointed out to earlier on this thread, one of
>>>> the
>>>>>> important aspect in ASF is getting the releases. We can informally
>>>>>> roll-out RC's for testing. But before we can vote on a release, that
>>>> has
>>>>>> to be done on cryptographically signed artifacts. Also there are
>>>>>> constraints on where the signed KEYS are located and so forth. Also,
>>>> we
>>>>>> need to properly follow the way we distribute release notes and also
>>>>>> publish artifacts to nexus repo so downstream users can get them.
>>>>>> 
>>>>>> I will be happy to help put together some detailed instructions on
>>>> the
>>>>>> website so we will have them for future. Here is a stating point on
>>>>>> Airavata release management -
>>>>>> http://airavata.apache.org/development/release-management.html
>>>>>> 
>>>>>> Suresh
>>>>> 
>>>> 
>>>> 
>> 
>

Re: [DISCUSS] Apache SIS 0.3 release - versions

Posted by Suresh Marru <sm...@apache.org>.

Hi Chris,

I was planning to either help Martin or volunteer myself to be the RM. But if you have cycles, thats really nice. Few more thoughts on improving the release process:

I think rat check have to be part of release steps which saves significant time in verifying the license header. Also, I suggest to use different assembly for source and binaries so license and notice files can be captured separately and bundled accordingly.

I think once we stream line the release process (and automate as much as possible) and document clearly the steps, subsequent releases will be very easy and painless. 

Cheers,
Suresh

On Jun 29, 2013, at 8:06 PM, "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov> wrote:

> 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
> 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Adam Estrada <es...@gmail.com>
> Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
> Date: Saturday, June 29, 2013 4:57 PM
> To: "dev@sis.apache.org" <de...@sis.apache.org>
> Subject: Re: [DISCUSS] Apache SIS 0.3 release - finished porting the tests
> 
>> Thanks a lot Chris and Martin. Just want to note that SIS also builds
>> without any problems on Windows 8 64bit.
>> 
>> D:\Apache\SIS>mvn --version
>> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
>> 08:51:
>> 28-0500)
>> Java version: 1.7.0_15, vendor: Oracle Corporation
>> Java home: C:\Program Files\Java\jdk1.7.0_15\jre
>> Default locale: en_US, platform encoding: Cp1252
>> OS name: "windows 8", version: "6.2", arch: "amd64", family: "windows"
>> 
>> [INFO] Writing OBR metadata
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache SIS ........................................ SUCCESS
>> [6.660s]
>> [INFO] Apache SIS core modules ........................... SUCCESS
>> [0.051s]
>> [INFO] Apache SIS build helper ........................... SUCCESS
>> [6.250s]
>> [INFO] Apache SIS utilities .............................. SUCCESS
>> [17.197s]
>> [INFO] Apache SIS metadata ............................... SUCCESS
>> [5.145s]
>> [INFO] Apache SIS referencing ............................ SUCCESS
>> [1.145s]
>> [INFO] Apache SIS storage ................................ SUCCESS
>> [0.091s]
>> [INFO] Apache SIS common storage ......................... SUCCESS
>> [1.664s]
>> [INFO] Apache SIS NetCDF storage ......................... SUCCESS
>> [17.884s]
>> [INFO] Apache SIS applications ........................... SUCCESS
>> [0.072s]
>> [INFO] Apache SIS web services layer ..................... SUCCESS
>> [4.805s]
>> [INFO] Apache SIS console ................................ SUCCESS
>> [0.988s]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESS
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 1:03.687s
>> [INFO] Finished at: Sat Jun 29 19:52:42 EDT 2013
>> [INFO] Final Memory: 43M/275M
>> [INFO]
>> ------------------------------------------------------------------------
>> 
>> 
>> On Sat, Jun 29, 2013 at 1:14 AM, Mattmann, Chris A (398J) <
>> chris.a.mattmann@jpl.nasa.gov> wrote:
>> 
>>> Hi Martin,
>>> 
>>> -----Original Message-----
>>> 
>>> From: Martin Desruisseaux <ma...@geomatys.fr>
>>> Organization: Geomatys
>>> Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
>>> Date: Friday, June 28, 2013 3:27 PM
>>> To: "dev@sis.apache.org" <de...@sis.apache.org>
>>> Subject: Re: [DISCUSS] Apache SIS 0.3 release - finished porting the
>>> tests
>>> 
>>>> Hello all
>>>> 
>>>> I finished porting the tests that I wanted. I think that the test
>>>> coverage is still insufficient, but we will hopefully start receiving
>>>> feedbacks from users.
>>> 
>>> woot! OK that sounds great.
>>> 
>>>> 
>>>> I would appreciate if some volunteers could try "mvn install" on their
>>>> machine. Some methods are locale or timezone sensitive. I tried to
>>>> protect the test cases against timezone changes, but I may have forgot
>>>> some cases.
>>> 
>>> OS: Mac OS X 10.8.4
>>> MacBook Air Intel i7
>>> Java Version:
>>> [chipotle:~/tmp/apache-curator-2.1.0/apache-curator-2.1.0-incubating]
>>> mattmann% java -version
>>> java version "1.6.0_45"
>>> Java(TM) SE Runtime Environment (build 1.6.0_45-b06-451-11M4406)
>>> Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01-451, mixed mode)
>>> [chipotle:~/tmp/apache-curator-2.1.0/apache-curator-2.1.0-incubating]
>>> mattmann%
>>> 
>>> Maven Version:
>>> 
>>> 
>>> [chipotle:~/tmp/apache-curator-2.1.0/apache-curator-2.1.0-incubating]
>>> mattmann% mvn --version
>>> Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800)
>>> Maven home: /usr/share/maven
>>> Java version: 1.6.0_45, vendor: Apple Inc.
>>> Java home: 
>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
>>> Default locale: en_US, platform encoding: MacRoman
>>> OS name: "mac os x", version: "10.8.4", arch: "x86_64", family: "mac"
>>> [chipotle:~/tmp/apache-curator-2.1.0/apache-curator-2.1.0-incubating]
>>> mattmann%
>>> 
>>> 
>>> Test results
>>> 
>>> All tests pass.
>>> 
>>> [INFO] Writing OBR metadata
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Apache SIS ........................................ SUCCESS
>>> [2.521s]
>>> [INFO] Apache SIS core modules ........................... SUCCESS
>>> [0.743s]
>>> [INFO] Apache SIS build helper ........................... SUCCESS
>>> [5.010s]
>>> [INFO] Apache SIS utilities .............................. SUCCESS
>>> [28.158s]
>>> [INFO] Apache SIS metadata ............................... SUCCESS
>>> [8.591s]
>>> [INFO] Apache SIS referencing ............................ SUCCESS
>>> [2.432s]
>>> [INFO] Apache SIS storage ................................ SUCCESS
>>> [0.181s]
>>> [INFO] Apache SIS common storage ......................... SUCCESS
>>> [3.575s]
>>> [INFO] Apache SIS NetCDF storage ......................... SUCCESS
>>> [1:21.364s]
>>> [INFO] Apache SIS applications ........................... SUCCESS
>>> [0.084s]
>>> [INFO] Apache SIS web services layer ..................... SUCCESS
>>> [3.465s]
>>> [INFO] Apache SIS console ................................ SUCCESS
>>> [1.684s]
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD SUCCESS
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 2:19.080s
>>> [INFO] Finished at: Fri Jun 28 21:48:58 PDT 2013
>>> [INFO] Final Memory: 35M/88M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [chipotle:~/src/sis/trunk] mattmann%
>>> 
>>> 
>>> 
>>> 
>>>> 
>>>> I will try to read Suresh's instructions this weekend. Some tasks that
>>>> popup from my heads before to make a release are:
>>>> 
>>>> * Update the web site and the wiki (the last "recent report" is 14
>>>>   months old)
>>>> * Re-organize the "getting started" instructions
>>> 
>>> This can be done post release.
>>> 
>>>> * Review pending JIRA tasks
>>> 
>>> Pre release, I will help with this.
>>> 
>>>> * Review javadoc
>>> 
>>> Post release.
>>> 
>>>> * Decide on the content of the distributed ZIP files.
>>> 
>>> We can do this now. Apache simply releases source, that's what we VOTE
>>> on.
>>> Everything else is "convenience" binaries, provided by the Release
>>> Manager
>>> or project at their own desire.
>>> 
>>>> 
>>>> 
>>>> I don't know yet if there is Apache recommendation about the content of
>>>> the distributed ZIP files. One proposal could be to provide 3 separated
>>>> files: binary, javadoc and source code. The content of the ZIP file for
>>>> the binary could be:
>>>> 
>>>>  README
>>>>  LICENSE
>>>>  NOTICE
>>>>  bin/sis
>>>>  bin/sis.bat
>>>>  bin/sis.jar
>>>>  etc/logging.properties
>>>> 
>>>> 
>>>> where "sis" and "sis.bat" would be convenience shell scripts (Unix and
>>>> Windows respectively) for invoking "sis.jar", and "etc" would be any
>>>> configuration file (only an optional "logging.properties" for now).
>>> 
>>> I would say we simply:
>>> 
>>> 1. Create tag
>>> 2. tar cvzf apache-sis-0.3-incubating-src.tar.gz tag
>>> 3. asc, md5 and sha1 that
>>> 4. put up artifacts from 2-3 and for VOTE'ing
>>> 
>>> Shouldn't be much harder than that.
>>> 
>>>> 
>>>> Is there any though?
>>> 
>>> See above..
>>> 
>>> Cheers,
>>> Chris
>>> 
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Chris Mattmann, Ph.D.
>>> Senior Computer Scientist
>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>> Office: 171-266B, Mailstop: 171-246
>>> Email: chris.a.mattmann@nasa.gov
>>> WWW:  http://sunset.usc.edu/~mattmann/
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> Adjunct Assistant Professor, Computer Science Department
>>> University of Southern California, Los Angeles, CA 90089 USA
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 
>>> 
>>> 
>>>> 
>>>> 
>>>> Le 27/06/13 03:08, Suresh Marru a écrit :
>>>>> Hi Martin & Adam,
>>>>> 
>>>>> No worries on this one, we all learn through the process and I
>>> learned
>>>>> the hard way. As Chris pointed out to earlier on this thread, one of
>>> the
>>>>> important aspect in ASF is getting the releases. We can informally
>>>>> roll-out RC's for testing. But before we can vote on a release, that
>>> has
>>>>> to be done on cryptographically signed artifacts. Also there are
>>>>> constraints on where the signed KEYS are located and so forth. Also,
>>> we
>>>>> need to properly follow the way we distribute release notes and also
>>>>> publish artifacts to nexus repo so downstream users can get them.
>>>>> 
>>>>> I will be happy to help put together some detailed instructions on
>>> the
>>>>> website so we will have them for future. Here is a stating point on
>>>>> Airavata release management -
>>>>> http://airavata.apache.org/development/release-management.html
>>>>> 
>>>>> Suresh
>>>> 
>>> 
>>> 
>