[OpenLayers-Dev] v3 branch on GitHub for deprecation & API changes

[Eric Lemoine]

On Fri, Nov 4, 2011 at 3:35 PM, Andreas Hocevar <ahocevar at opengeo.org> wrote:
> If done right, this can work. But our previous attempt to do that (ol3 on github) terribly failed, mostly because core developers were not able to contribute enough time for reviewing and mentoring. For those who contributed this is frustrating, and it should not happen again. The easiest way to focus resources is a code sprint, but this requires planning and a compelling roadmap in order to get enough funding.
>
> Having said that, people can send pull requests regardless of the presence or absence of a v3 branch. For the contributors, it is important that core developers pay attention to these pull requests. If a v3 branch increases the level of core developer attention, I'm all for it. Correct me if you think this is wrong, but as a PSC member, I see my duty now in joining forces with the whole PSC and other interested parties to plan a sprint with focus on a new API and find sponsors for it.


Today's situation might be more favorable than before. fredj has
already put quite some effort into removing deprecated code, and Tom
MacWright has submitted pull requests that go in the same direction. I
think it would be a shame to loose that momentum, I'd rather see these
guys (and possibly others) join effort in v3 branch. Today's situation
may also be different because our main development branch (master) is
now also on github, so maintaining a v3 branch (i.e. sync'ing it from
the main development branch) is a lot easier than before.

--
Eric Lemoine

Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac, Cedex

Tel : 00 33 4 79 44 44 96
Mail : eric.lemoine at camptocamp.com
http://www.camptocamp.com