Makes sense to me Martin will look forward to the week of the 14th. 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: Martin Desruisseaux <[email protected]> Organization: Geomatys Reply-To: "[email protected]" <[email protected]> Date: Saturday, June 8, 2013 1:53 PM To: "[email protected]" <[email protected]> Subject: Re: [DISCUSS] Apache SIS 0.3 release >Hello Chris > >Le 08/06/13 06:23, Mattmann, Chris A (398J) a écrit : >> 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.? > >Indeed, SIS is feature-complete for what I though could be a release. I >was not planning to add any major public API. However I was hopping to >add tests and probably fix some bugs before a release. In particular, I >have not yet tested XML marshalling/unmarshalling and would be surprised >if it works right now. > >What about the following? Finish GeoHashCoder and a command line >interface, then no more functionality - we would focus only on tests, in >order to release sooner. > >The reason is that I would like very much for SIS to gain a reputation >of high quality library. Being 100% bug free is unrealistic, but I have >my "TODO" list of known bugs that I would like to fix before a release. >At the very least, I think that XML marshalling should be tested since I >see them as the "hearth" of a project targeting standard compliance - >this is needed for parts of WMS/WFS/WPS. > >Can we try one week of test/bug fixes, and revisit the release plan next >Friday (June 14th)? > > Martin >
