Hi all,
even though I am non-PSC committer, I think a separate branch might be
the easiest way to go towards 3.0.
Thanks go to Schuyler for "...I volunteer to try to manage the process
of collating proposed API changes, and to try to stay on top of
forward-porting future improvements to 2.x to the 3.x branch...",
because that'll likely be some hard work.
Just my two ยข
Marc
On 22.11.2011 03:58, Schuyler Erle wrote:
Hey, guys, I already made this motion once, but, after some initially
confusing discussions on IRC today, I thought I'd best make it again,
more concretely this time, because it's a topic about which people
feel passionately.
I move that we create a *new* v3 branch in Github in order to allow
people to begin work on redesigning the OpenLayers API, towards a
version 3.0 release. Obviously I am +1, and moreover I volunteer to
try to manage the process of collating proposed API changes, and to
try to stay on top of forward-porting future improvements to 2.x to
the 3.x branch.
I would really appreciate it if at least a couple other members of the
PSC would chime in with +1s before I go ahead with making the branch.
Also, if you'd like to veto this proposal, please do, but let's
discuss? I'd like to move ahead in the next day. Thanks!
SDE
_______________________________________________
Dev mailing list
d...@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/openlayers-dev
_______________________________________________
Dev mailing list
d...@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/openlayers-dev