Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Road to GeoExt 2.1.0 final #356

Closed
9 tasks done
chrismayer opened this issue May 12, 2015 · 16 comments
Closed
9 tasks done

Road to GeoExt 2.1.0 final #356

chrismayer opened this issue May 12, 2015 · 16 comments

Comments

@chrismayer
Copy link
Contributor

This issue is a kind of roadmap towards the final release of GeoExt 2.1.0, which is currently in an alpha-state.

TODOs:

@chrismayer
Copy link
Contributor Author

I opened this to bring the release of GeoExt 2.1.0 up again. This is also meant as discussion platform.

If I missed some TODOs please extend the list above.

@marcjansen
Copy link
Member

Adapt the README file according to the changed setup

What do you mean by that?

Does anyone have time to review the PRs? I can possibly do #352 if you think it is ready (but @bentrm wanted to add sth. IMO) but I won't have time for much more.

The website stuff is very important, I'll open a separate ticket.

@chrismayer
Copy link
Contributor Author

Adapt the README file according to the changed setup

What do you mean by that?

I think there should be done some adaptions, mainly in the sections "What is GeoExt" and "Ok, I want to use GeoExt now..." because there are hints to ExtJS 4.2. This should be extended with the similar ExtJS 5 informations. I can do that.

I can take care of #355, maybe @weskamm can have a look at #349? Anyone there to take care of #357?

@marcjansen
Copy link
Member

I just gave #357 a review. It is not ready to be merged yet.

@chrismayer
Copy link
Contributor Author

I gave #355 a review. There are also still things to do before it can be merged. Since it is a more or less bigger thing a second review would be cool before final merge.

@chrismayer
Copy link
Contributor Author

#355 is postponed to a follow up release since it is to much work to get it done until we want to release 2.1.0.
See discussion on the dev-list: http://www.geoext.org/pipermail/dev/2015-August/001295.html

@chrismayer
Copy link
Contributor Author

Since #357 is the only open PR (and seems to be closed soon), I try to propose a timeline for the 2.1.0 release process:

  • 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

Any comments?

@marcjansen
Copy link
Member

That sounds great! 👍

@marcjansen
Copy link
Member

Ping @chrismayer

@chrismayer
Copy link
Contributor Author

Okay, I did the release for GeoExt 2.1.0, which is available here: https://github.com/geoext/geoext2/releases/tag/v2.1.0

I also updated the gh-pages branch with the current docs and examples as well as some adaptions to the index file of http://geoext.github.io/geoext2/. Feel free to have a look.

@chrismayer
Copy link
Contributor Author

Just re-opened #359 since the online examples do not work properly when opened with HTTPS.

@marcjansen
Copy link
Member

Aaaaargh! That was stupid, that we only did half the work in #359. Apologies!

Please ping us if you need help with fixing it. Very nice work with the release so far!

@chrismayer
Copy link
Contributor Author

With c8e1d7f which has been pushed to the gh-pages branch by me the online examples should be fine again. If you find any problems please report in #359.

@weskamm
Copy link
Member

weskamm commented Nov 26, 2015

Thanks @chrismayer for all your efforts! 👍

@chrismayer
Copy link
Contributor Author

Since #359 is closed now, I suggest to close this as well and announce version 2.1.0 on the mailing lists.

@marcjansen
Copy link
Member

Go for it! Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants