I've created the 1.0 release branch here:
Between now and the actual release the following things need to be considered:
- keep working on trunk
- if things need to be merged, _always_ merge from trunk to the branch and not vice versa
- be careful what you merge
If you are in doubt how to proceed, please contact me.
Before we branch the 1.0 release, I would suggest we split the public API according to the following
<module>.client.api.*: the general client API for anyone working with errai components
<module>.client.framework.*: module extension points, considered more like an SPI
The idea is to have two levels of public API, clearly identified by subpackage names.
One for working with errai (api.*) and one for extending errai (framework.*).
This allows users to focus on what they need, expecting most implementations to rely on the
client API (api.*), whereas integration with 3rd party technology would rely on the extension API (framework.*).
Javadocs should only be available for those subpackages and deprecation rules only allow
changes to that API in between major releases.
I've already prepared the workspaces module, but didn't touch the bus module yet.
Let me know what you think. Once we've come to an agreement, I would go ahead and prepare
the 1.0 release branch according to those guidelines.