On 9/20/10 2:16 AM, Andreas Hocevar wrote: > Hi, > > the plan was to bump all open tickets that are not committed by now to 1.1. > But here is one that I consider a blocker, because it would result in > possible API changes. Tim, can you please have a look at this: > > http://trac.geoext.org/ticket/262 (needs patch or comment) >
#262 is awaiting review. Notice to SliderTip, ZoomSliderTip, and LayerOpacitySliderTip users: this changes the argument sent to your custom getText methods. The getText method gets a thumb (that has a value property) instead of a reference to the slider. This is consistent with the Ext.slider.Tip. > And here is a list of tickets related to the WMSCapabilitiesLoader. If we > cannot address them now, what would developers think about releasing 1.0 > without the WMSCapabilitiesLoader, and add it as soon as these tickets are > resolved? > > http://trac.geoext.org/ticket/314 (blocker, needs a review) > http://trac.geoext.org/ticket/317 (blocker, needs patch) > http://trac.geoext.org/ticket/335 (blocker, tests failing) > http://trac.geoext.org/ticket/287 (needs a review) > I agree that WMSCapabilitiesLoader enhacements can come with 1.1. I'm unclear why #317 would break backwards compatibility. And I can't reproduce #335 in IE7 at r2371. Thanks for the release manager work. Tim > Also, here is a ticket that is marked commit. Bart, please look at it: > > http://trac.geoext.org/ticket/313 > > Listed below are tickets that are ready for review. Since we still have > unresolved blockers, I will not bump them to 1.1 before all blockers are > resolved. So if time permits, reviews of the following tickets are welcome: > > http://trac.geoext.org/ticket/139 > http://trac.geoext.org/ticket/329 > http://trac.geoext.org/ticket/334 > http://trac.geoext.org/ticket/339 > http://trac.geoext.org/ticket/308 > > Finally, we need to make sure that the documentation is updated to reference > Ext 3.x everywhere, and the sencha.com url is used in links rather than > extjs.com. If someone could look at this, I would greatly appreciate it. This > is not a blocker, but it's good to have a release with an up-to-date > documentation: > > http://trac.geoext.org/ticket/184 > > Regards, > Andreas. > > On Sep 13, 2010, at 10:55 , Andreas Hocevar wrote: > >> Hey, >> >> at the FOSS4G code sprint last friday, we made some good progress towards >> GeoExt 1.0. The plan is to release GeoExt 1.0 as soon as possible. The >> release will be tested against OpenLayers 2.10 and Ext 3.2.1. >> >> I volunteer to act as the release manager for 1.0. A few things that >> everybody should do before we can do a release candidate: >> >> * Please create tickets if you have important API changes in mind. These >> tickets should be ready to review by Sep 15th EOD, and have the "api change" >> keyword. >> >> * There are already some tickets ready for review that propose API changes. >> As far as I was aware, I have added the "api change" keyword to them. These >> are top priority. Please help reviewing them. >> >> * Post a list of tickets that you care about to the dev list. Only tickets >> that are ready for review by Sep 15th will be considered. There will be time >> to review all these tickets until Sep 19th, so please help reviewing tickets >> if time permits. >> >> * All tickets that are not committed by Sep 19th EOD will be bumped to 1.1. >> I am planning to do the release candidate on Sep 20th, given that all api >> changing tickets are addressed by then. >> >> Please comment if you have concerns. >> >> Regards, >> Andreas. >> >> -- >> Andreas Hocevar >> OpenGeo - http://opengeo.org/ >> Expert service straight from the developers. >> > -- Tim Schaub OpenGeo - http://opengeo.org Expert service straight from the developers. _______________________________________________ Dev mailing list [email protected] http://www.geoext.org/cgi-bin/mailman/listinfo/dev
