Jody Garnett a écrit :
Do you want me to create a 2.2-M3 release now (not sure I got what you
mean)?
Sure - but can we call it 2.2.RC0 (ie release candidate zero). That
would be swell.
I can do that (preferably with Maven 2, if nobody object, but after
making sure that the build was successfull with Maven 1). I will finish
the part that I'm hacking right now and will go ahead.
If we call this release 2.2.RC0, then what it the correct process?
- Create a 2.2 branch before the 2.2.RC0 tag, and only bug fixes
should be applied on that branch.
- Do not create a 2.2 branch (only a 2.2.RC0 tag) and continue to
apply bug fixes directly on trunk. But release 2.2 final very
soon before too much development occur on the trunk (in which
case 2.2.RC0 would not a release candidate anymore, but still
a beta in development).
As a last note, there is one thing that I would like before the release.
We still have a 50 Mb file on the SVN:
plugin/geotiff/test/org/geotools/gce/geotiff/test-data/002025_0100_010722_l7_01_utm21
And a 8 Mb zipped file (50 Mb unzipped):
plugin/gtopo30/test/org/geotools/gce/gtopo30/test-data/W020N90.zip
Do we have a volunter for trimming down those files too?
Martin.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
