Plans¶
Due to limited CBA manpower, while the core of CBA needs careful consideration, we are using the following a schedule.
0.1.x¶
- Release CBA ASAP in order to make XEH available.
- Get preliminary feedback from potential users.
0.2.x¶
- Finalize the CBA core, lean and mean.
- Integrate some 3rd party core functionality that is deemed to be very useful.
- To enforce a coherent vision and enable rapid development, avoiding inviting new members to the core development team.
- Allow a number of changes to core functionality, based on feedback or overall consistency:
- For example, renaming functions or changing parameters (which will be properly deprecated, continuing to work but giving a warning message for any obsolete usage, before disabling old function after at least a full minor version (e.g. something deprecated in 0.2.x would not be actually disabled before 0.3.0, probably being left in until 0.4.0).
0.3.x and beyond¶
- Focus on submitted code, integrating more and more 3rd party functions to the library.
- Look to expanding the core development team.
- Avoid changes to core functionality if at all possible.
The Roadmap displays our estimations and more detail of what changes are to be made at which version.