> Should we:
> 1. just say "ha ha - fooled you" for the people doing rendering (and
> other modules) on 2.1.x. This pretty much means we're calling 2.1.x a
> fork.
>
2.1.x was always a fork? Stable branches by their nature are always
forks - I do expect 2.1.1 to
be released at some point.
> 2. Actually try to announce, vote, and transition API changes.
>
Jody, my question is more along the lines of when should the project mature into more of a maintenance stance than r&d. For those of you who would argue that it has already progressed to a maintenance stance, then the question is, how often should we phase out api / replace api / change api (This is a life cycle question). For example (don't want to single this case out ... there have been numerous cases), we should ask:
(Example questions)
1) is the new Style API backwards compatible
2) are any of the additions too close to the old methods (duplicates)
3) which methods (any?) are being removed, and how will this affect (1)
I asked back in september if I could add events in, I have not harmed
the interfaces on route. Justin putting
defaults into the interfaces have also not changed things with respect
to StyleFactory use. Many of the incompatiable
changes are due to mistakes, not having a StyleFactoryFinder, not
breaking things out into interfaces, not
matching SLD 1.0 ... I asked long and hard for a couple weeks how people
wanted me to proceed and
have done a good job sticking with that.
My comments are not on this direct case ... but more general in nature. I guess I should be more specific ... I do not support a two branch approach, I think we should only have one branch (the one currently dubbed 'stable').
> 3. <insert your 3rd option>
>
> dave
> PS. And *please* don't auto-format code anymore!
>
I have been good :-( Although I think the answer is to auto format all
the time... as it was when I joined the project.
Maybe I should phrase this question another way, can we arrange the IRC
meeting at a better time to increase attendance, or
set up a breakout IRC meeting on these things. I found that IRC was in
almost constant use last week as problem after problem
was found in the Style classes. We also wrote up a web page describing
what had been done...
Jody
-------------------------------------------------------
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_id=7637&alloc_id=16865&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
