Martin wrote: > Following Jody email > > But I currently get a change for every files, because of some changes > like the addition of $URL$ keyword. Can we do one of the following (when > Simone or Bryce would have a little bit of time of course)?
My current understanding was in a previous email to Jody: currently, I think that branch contains Simone's and Alessio's changes which were required to make a Geoserver/WCS. Some fixes to various GCE plugins, etc. It should shortly contain a 19123 implementation as well. > 1) Just explain (in plain text) where are the main changes applied > on coverages in coverage_branch For details, Simone's the one to talk to. > 2) Synchronize the coverage_branch with the trunk (using "svn merge" > from trunk to the branch) so the above-cited "svn diff" command > can get less verbose. I'd like to think we've been doing that. At least we started out doing that. Certainly we should synchronize before starting the 19123 implementation, so we have a nice clean baseline. Actually, we should probably make a "tag" for the last pre-implementation config, so we can always get back something that compiles. > Also, I would like a road map for merging coverages_branch to trunk. > > What do you think? I think I'll produce a road map before we merge to trunk. :) However, I think I'll be breaking the task at hand down into Implementation Work Units (IWUs) this week. As IWUs are produced, they will be formed into Jira tasks with the proper dependencies on existing, broad tasks ("Implement Coverage Objects") At this point, they may be taken by anyone, but will probably be taken by someone out of NURC or Firelab, as we are the most motivated. When these are all done, with test cases, and they work, and NURC's ready to make a Geoserver/WCS release against it, we'll _start_ thinking about how to merge to trunk. In short, for the _main implementation effort_, you're going to have #1 (above) before we generate any code at all. Bryce ------------------------------------------------------- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel