Hi everybody,
as soon as we have released 2.0.3 (see my other mail), I propose the
following:
1. create a permanent branch 'v-2.0.x' from which future 2.0.x releases
may happen, if we decide we need any.
2. work hard on making pull request #274
(https://github.com/geoext/geoext2/pull/274, Support for the next
major ExtJS version 5.1) mergeable
3. merge #274 into master and create tickets for the remaining issues.
This would mean that on master certain things wouldn't fully work as we
don't support anything in a GeoExt based on ExtJS5. For users of 4.2.1
nothing would change, everything should be working fine for them.
A future version 2.1.0 would then finally be released from the
then-to-be master, and it'll bring support for ExtJS5.
Thoughts?
Best,
Marc
_______________________________________________
Dev mailing list
Dev@geoext.org
http://www.geoext.org/cgi-bin/mailman/listinfo/dev
