[udig-devel] Re: [Geotools-devel] Keeping uDig temporarily on Geotools 2.4

[Rob Atkinson]

Cutting branches to support bug fixes from a stable place makes sense.  
Adding new functionality from this point is more problematic - the 
overhead of testing stuff against a branch and the trunk is high, and 
having the trunk orphaned again is a recipe for frustration and delay.

My own thought would be:

branch + bug fixes = good if and only if bug fixes are rolled to trunk
trunk + bug fixes = always good, and better if bugs are recorded as 
unfixed against branch to spur progress toward a continually improving 
trunk.
branch + new modules = good, but care should be taken the API is 
compatible with the trunk and well documented where changes will be 
required - and resource porting to trunk at each milestone of the module 
(not waiting for final release)

trunk+ new unit tests = imperative.

Rob

Adrian Custer wrote:
> Hey all,
>
> As of revision 26360 uDig can be run on eclipse 3.3 using geotools 2.4.
> This is a stable configuration for SDK developers so I hope we could
> keep some form of this configuration around for a while even if others
> want to rush to port uDig to the new feature model.  I'd like either for
> a branch to be made at this revision or for trunk not to be pushed
> forward to geotools 2.5 until we have stabilised the new feature model
> at least a little. 
>
> While I realize that uDig moving to geotools trunk will be needed to
> fully stabilize the new geotools feature model, I'd like not to jump the
> gun. We need some working examples (as requested by Rob A.) on Geotools
> trunk and some other basics before it's worth making uDig trunk totally
> unstable during the port.
>
> Thoughts, comments, rants?
>
> --adrian
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Geotools-devel mailing list
> Geotools-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: rob.vcf
Type: text/x-vcard
Size: 261 bytes
Desc: not available
Url : http://lists.refractions.net/pipermail/udig-devel/attachments/20070730/99cc5433/rob.vcf