Hi all,
I personally feel that GeoExt2 is basically ready for prime time. We
used it successfully in some fairtly big applications and only found
minor bugs/annoyments we already fixed in the codebase. There is still
at least one fixed bug I am going to integrate into the master-branch soon.
Nevertheless, I suggest to start the release process for the version 2
of GeoExt.
Do you share that opinion?
I think that there is still a lot of work, though:
* We should double check all classes and examples with regard to
o API compatibility with v. 1
o documentation
o tests
o and some sort of coding style
* Where will we be hosting the API docs? Are we going to change
geoext.org? Or shall we simply stick with gh-pages? Are we going to
integrate runnable examples inside of the documentation?
* We also need some prose docs / tutorials
o about migrating existing application
o building a single-file application
o getting the best out of MVC
o API-changes (If we have any)
* What is the release procedure? Are the steps outlined here
(http://trac.geoext.org/wiki/Release/Procedure) still relevant?
I suggest starting with an early beta version in the next few days, so
that we can make people aware of GeoExt2 and hopefully get feedback
about the library.
In case you agree with the starting of the release process, we also need
to decide who will be the release manager?
What other points / aspects did I miss?
Please tell me your opinions and about the next steps needed to get to
GeoExt 2.0-beta.
Best regards,
Marc
_______________________________________________
Dev mailing list
Dev@geoext.org
http://www.geoext.org/cgi-bin/mailman/listinfo/dev
