Hi devs, I propose the following timeline for the release process of version 2.1.0:
- Provide a beta version until 2015-09-04 - Wait for feedback for one week - Optional roundtrip for bugfixes / adaptions according to feedback (1 week) - Release a final version and adapt depending resources (gh-pages, etc.) until the end of September I published the same in our github roadmap [1]. Disscusion could be done there. Cheers Chris [1] https://github.com/geoext/geoext2/issues/356 Am 27.08.2015 um 11:31 schrieb Christian Mayer: > Hi Marc, > > thanks for your feedback. I will also comment inline. > > -- > Christian Mayer > GIS-Spezialist & Software-Developer > > meggsimum > Hauptstraße 165a | 67125 Dannstadt-Schauernheim > i...@meggsimum.de | www.meggsimum.de > > Am 26.08.2015 um 16:52 schrieb Marc Jansen: >> Hi Chris, >> >> good that you bring this up again. Find comments inline. >> >> >> On 26/08/15 12:13, Christian Mayer wrote: >>> Hi Devs, >>> >>> a while ago we published GeoExt 2.1.0-alpha [1] and added a roadmap to >>> final 2.1.0 [2]. With this mail I want to bring this up again, so we >>> hopefully get a final 2.1.0 soon. From my point of view we have the >>> following state: >>> >>> - PR #352 [3] needs a bit of rebase work of myself and then it seems >>> good to go (IMHO) >> Please merge once the final comment from me is adressed. I just added >> the comment to the PR. > I just merged the PR. >>> - PR #355 [4] is still a lot of work and should be postponed >> I agree, please update the issue/PR as you like. > I removed this PR from the roadmap, see #356 >>> - PR #357 [5] needs a little work or at least an agreement (mainly >>> @bentrm and @marcjansen) to postpone further optimization >> I will give my OK for a merge if we add a big TODO somewhere and maybe >> even an issue as the approach seems more than hackish to me. Nonetheless >> the result is better than what we had before, so plus one for merging it >> once it is updated with a big TODO. I just commented the PR. > You and @bentrm agreed on adding a big TODO before merging this. > So a merge should not be far away. >>> After having a finalized codebase we could release a beta and/or a RC. >>> After that we could take care of the final release steps (as described >>> in the roadmap issue #356). >> I'd be for a beta and a fixed timeframe for the other stuff including a >> final 2.1. > +1 for a timeframe. I will check what will be realistic and will publish > the timeline here and in the roadmap on github (#356) >>> Thanks for any thoughts / comments on this. >> I will not have time to do anything of importance for this release. Will >> you tackle this and get all the fame for v2.1, Chris? :-) >> >> I honestly hope you take that job! > I will take the job and grab the tons of fame ;-) > > Cheers, > Chris >> Thanks and best regards, >> Marc >> >>> Cheers, >>> Chris >>> >>> >>> [1] https://github.com/geoext/geoext2/releases/tag/v2.1.0-alpha.1 >>> [2] https://github.com/geoext/geoext2/issues/356 >>> [3] https://github.com/geoext/geoext2/pull/352 >>> [4] https://github.com/geoext/geoext2/pull/355 >>> [5] https://github.com/geoext/geoext2/pull/357 >>> >>> _______________________________________________ >>> Dev mailing list >>> 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 > _______________________________________________ > Dev mailing list > 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
