Roadmap to release v3.0.0

[marcjansen]

This issue tries to list the things we should do before we can release v3.0.0. As such we will probably edit the content.

In order to see where we are, I propose to release an early v3.0.0-alpha.1 soon. Then we can tackle any of the following for subsequent pre releases or the final v3.0.0.

• Fix FeatureStore Bug FeatureStore with fields config do not work #171
• Add an example for a universal app or link to a repo containing one (see also e.g. Dashboard example with GeoExt 3 panel #115)
• Add an example for all the different aspects of the library (At least double check we have one)
  • Update or remove the MapViewForm example (see also e.g. MapViewForm example showing no map / tiles #54), done with Update form example #121
• Test untested lines/statements. Can we reach 90% coverage?
• Update the README.md and probably restructure it with content available in DEVELOPMENT.md
• Double check the packaging done by the CI.
  • Does the subfolder generation work when we are building for a git-tag?
  • Can we release the packages under a subfolder? Currently one sencha package replaces the previous one. This is IMO only OK while we don't have v3.0.0. I never want to loose the v3.0.0 package, even if we already are at say v3.1.0.
• Better API docs with more inline examples. See Various API documentation enhancements #118
• Update issue Road to a "universal app" #65 "Road to universal app".
• Fix or delay remaining issues
  • Popup enhancements and remaining issues Remaining popup issues and wanted enhancements #25
• Check if and how we can publish the package also in the sencha Market
• Document differences to previous versions. If we provide fewer functionality, hint at a possible solution without dedicated components.

Please feel free to share your thoughts and ideas here. For any of the above tasks fell free to add dedicated tickets (and link them here).

[chrismayer]

Hey @marcjansen, thanks a lot for bringing this up. I agree that we should push this forward to have a v3.0.0 soon. Your roadmap looks good to me. Should we think about a time frame or does it make any sense at all?

[marcjansen]

Should we think about a time frame

Yes, we should. Please feel free to list estimated target days for any releases in the body of this issue. You should be able to edit it.

[jgrocha]

Thanks @marcjansen.

I'll improve the #115 example in the next days and add some documentation related to it, as well. This example is more focused on all GeoExt features and not just on features available in both classic and modern toolkits.

Creating a universal app is already documented in universal-app.md. We can add the application app described as an example.

[marcjansen]

Comments:

• Add an example for all the different aspects of the library (At least double check we have one)

We don't have an example for everything, and for v3.0.0 we will not have one. That is OK for me.

• Test untested lines/statements. Can we reach 90% coverage?

We have ~ 86% That is enough for me.

• Double check the packaging done by the CI.

We'll do that during the release.

• Fix or delay remaining issues

I opt for delay.

• Check if and how we can publish the package also in the sencha Market

Sencha market will be closed down soon. We can ignore this.

• Document differences to previous versions. If we provide fewer functionality, hint at a possible solution without dedicated components.

Detailed docs for this are missing, we might add them one day... Delayed for now.

I will close this ticket in favor of #259. Please speak up there, if needed.