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: [email protected] 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 <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Saturday, June 29, 2013 4:57 PM To: "[email protected]" <[email protected]> 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) < >[email protected]> wrote: > >> Hi Martin, >> >> -----Original Message----- >> >> From: Martin Desruisseaux <[email protected]> >> Organization: Geomatys >> Reply-To: "[email protected]" <[email protected]> >> Date: Friday, June 28, 2013 3:27 PM >> To: "[email protected]" <[email protected]> >> 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: [email protected] >> 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 >> > >> >>
