James Macgill a écrit :
2.1 is a branch. The moment work not related to bug fixes (is
optimization a bug fix?) started it became a fork. I have said all
along that I have been very very uncompfortable with the level of
development work happening on 2.1.x but the people doing that work
assured me they were happy to keep 2.1 and 2.2 synch. These same
people now seem to be very un-happy keeping that level of effort up.
I can recall no commitment from 2.2 developers to make life easy for
2.1 developers other than ensuring that code written against 2.1 would
work on 2.2. (I can well imagine that this is not holding true and if
so needs to be addresed urgently)
I see that in the same way. I'm surprised that so much development
continue on the 2.1 branch, and it is not clear for me why this work
happen. I understand that GeoServer and uDig need a stable fundation,
but I though that 2.1 code were supposed to run on 2.2? In theory,
conservative client code just need to avoid 2.2-specific API (marked by
"@since 2.2" in javadoc) until 2.2 final is out. So why do we maintain 2.1?
If a 2.1 API is broken in a 2.2 public package (i.e. a package that is
not flagged as "do not use" in javadoc), then I agree that this
situation need to be fixed.
I can understand that broken build is sometime a problem. An alternative
is to release Geotools more often. I can volunter for deploying Maven 2
snapshot releases more often (for example weekly) and publish them on
http://maven.geotools.org/gt2/org/geotools/ if there is a demand for
that. I would not make ZIP file weekly for SourceForge (and I do not
volunter for making Maven 1 releases neither), but the
maven.geotools.org repository should allow Maven 2 users to download
automatically Geotools binaries for any specific release without having
to bother about building Geotools themself.
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
