Hi, I also think this is a great idea!
Julien On 15-01-12 03:10 AM, Bart van den Eijnden wrote: > Assuming we have no backwards-incompatible changes in the ExtJS 5 > branch, this would work for me. > > Best regards, > Bart > > Bart van den Eijnden > Front End Software Engineer | Boundless <http://boundlessgeo.com/> > bart...@boundlessgeo.com <mailto:bart...@boundlessgeo.com> > 1-877-673-6436 <tel:917-460-7207> > @boundlessgeo <http://twitter.com/boundlessgeo/> > > <http://boundlessgeo.com> > >> On 10 Jan 2015, at 11:18, Marc Jansen <jan...@terrestris.de >> <mailto:jan...@terrestris.de>> wrote: >> >> 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 <mailto:Dev@geoext.org> >> http://www.geoext.org/cgi-bin/mailman/listinfo/dev > > > > _______________________________________________ > Dev mailing list > Dev@geoext.org > http://www.geoext.org/cgi-bin/mailman/listinfo/dev > -- Julien-Samuel Lacroix T: +1 418-696-5056 #202 Mapgears http://www.mapgears.com/ _______________________________________________ Dev mailing list Dev@geoext.org http://www.geoext.org/cgi-bin/mailman/listinfo/dev
