- 0 Talk
-
Release Strategy
Contents |
Introduction
Edit
This page describes the development and release strategy adopted as of December 2011. Original discussion in the forum http://chdk.setepontos.com/index.php?topic=2905.15
History / MotivationEdit
Prior to the adoption of this strategy, there was a single "autobuild" which was both the development trunk and the only version readily available to end users. This made it extremely difficult to implement major changes without negatively impacting users.
Process overviewEdit
- A stable release is maintained for bug fixes and ports.
- New features and other major changes to the core code are implemented in an unstable development branch.
- At intervals, the development branch will enter a period of stabilization.
- When the result is judged sufficiently stable, a new stable branch is made, and development of the next version proceeds in the development branch.
Development branchEdit
The development "branch" is always be the trunk, found at http://subversion.assembla.com/svn/chdk/trunk/
All major new features or code re-writes will be done here.
As of February 2012, the development version 1.1.0 is in the "active development phase" as described below.
Autobuilds of the development branch will be available at some point.
Development branch lifecycleEdit
- Release branch N created, development for N+1 proceeds in trunk
- Active development phase
- Release branch recommended for users and new ports
- Development of major / disruptive features
- Stabilization phase
- Major features complete
- Development builds suggested for users who want new features
- Low risk features may be added
- Release candidate phase
- Development branch recommended for users
- New ports go in development branch, not back ported by default
- Focus on bug fixes
- Release - GOTO 1
Stable branchEdit
The stable branch represents a "release" where major functionality and features are frozen. New ports may be added to the stable branch.
The stable branch will always be named release-N_M, where N and M are the major and minor version numbers.
As of February 2012, the stable version is 1.0.0, found in the svn branch http://subversion.assembla.com/svn/chdk/branches/release-1_0/
Autobuilds from the stable version are available from http://mighty-hoernsche.de/
Important: stable refers to the feature set, not necessarily the maturity of the software. Stable does not mean that all features are fully functional on all cameras, or that the software won't crash.
Individual ports within the stable branch may vary widely in completeness and functionality. Individual ports will be labeled Alpha or Beta as appropriate.
PortsEdit
It is currently recommended that new ports may be developed for the stable branch, unless they require major changes in the core code.
The development branch is probably not a good target for new ports, since the port developer may encounter problems not related to the port. However, the choice of which branch to target is up to the developer doing the port, and the correct choice will depend on the developer and the current state of the development branch.
RoadmapEdit
Version 1.1Edit
Version 1.1 is in the unstable development phase. The following features are currently targeted for 1.1. This list is subject to change.
- Loadable binary modules
- Script improvements (ubasic performance, non-ui scripts)
- Re-write of USB remote code
- "Live view" over PTP
- Support for Eye-Fi cards.
- Integration of chdkde features (details TBD)
Version 1.0Edit
Current stable.
