Hi all,

so I think we go with gh-pages for the moment. Fine for me. The online examples in the Ext-docs should not be to hard I have played with that for OpenLayers and it works like charm.

I will hopefully start work on the open things soon. I'll keep everyone updated.

Bye,
Marc



On 15.10.2012 15:47, Bart van den Eijnden wrote:
Hey Marc,

thanks for bringing up the subject, and sorry for a late reply.

Best regards,
Bart

--
Bart van den Eijnden
OpenGeo - http://opengeo.org <http://opengeo.org/>
Expert service straight from the developers.



On Oct 10, 2012, at 9:18 AM, Marc Jansen <jan...@terrestris.de <mailto:jan...@terrestris.de>> wrote:

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.

Great to hear you've used it in real life, we haven't as yet unfortunately.


Nevertheless, I suggest to start the release process for the version 2 of GeoExt.

Do you share that opinion?

Yes, please. Anything to adopt a broader use.


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

True, some quality checks are in order.

  * Where will we be hosting the API docs? Are we going to change
    geoext.org <http://geoext.org>? Or shall we simply stick with
    gh-pages? Are we going to integrate runnable examples inside of
    the documentation?

gh-pages sounds okay. What effort do you think is involved wrt the runnable examples? I wouldn't delay the release for this personally.

 *


  * We also need some prose docs / tutorials
      o about migrating existing application

True, did you keep any notes when upgrading your applications?

     o


      o building a single-file application

Doesn't Alexandre's example serve as that?

      o getting the best out of MVC

We could just point to Ext blogs / tutorials on the subject or not? I don't see where the GeoExt2 use case here is specific.

      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?

If you would want to be release manager, that would be great. I'll also try and help out as much as possible, feel free to assign me some specific tasks.


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 <mailto:Dev@geoext.org>
http://www.geoext.org/cgi-bin/mailman/listinfo/dev



--

  Dipl.-Geogr. Marc Jansen
  --- Anwendungsentwickler ---

  terrestris GmbH & Co. KG
  Pützchens Chaussee 56
  53227 Bonn

  Tel:   +49 (0)228 / 96 28 99 -53
  Fax:   +49 (0)228 / 96 28 99 -57

  Email: jan...@terrestris.de
  Web:   http://www.terrestris.de

  Amtsgericht Bonn, HRA 6835, Komplementärin: terrestris Verwaltungs-
  gesellschaft mbH, vertreten durch: Hinrich Paulsen, Till Adams

_______________________________________________
Dev mailing list
Dev@geoext.org
http://www.geoext.org/cgi-bin/mailman/listinfo/dev

Reply via email to