Development Ethos
PostNuke is a completely volunteer run project. As a result, no specified amount of time each day, week, month or year can be spent on the project. Due to this situation no timescales are made available for each milestone listed in this roadmap. New versions will be released when they are ready, rather than to a specific timescale, leading to an overall improved product. Instead, this document is aimed to give some idea of the direction development of PostNuke will take in the future.
Versioning
PostNuke release versioning takes a specific format, used until the 1.0 release. This is of the form .ABC and each element of this form is discussed below.
A - Major Release
Encorporating the achievement of a specific milestone, and introducing other new features. Major releases represent a specific internal change to the codebase.
B - Minor Release
Some new featuresd, minor changes to the codebase. Perhaps released to make available new features in core modules.
C - Maintenance Release
Fixes to any reported issues and bugs (after a release has gone through release candidate stage). Only very few / minor modifications made.
Milestones and Goals
There are some very general goals for the continued development of PostNuke. Following these are specific, version-by-version goals and milestones for releases.
Move towards higher standards of code throughout PostNuke. Particular emphasis is on performance, templating core modules, API compliance in all core modules, and cross database compatibility through the ADOdb database abstraction layer.
Standards compliance, XHTML and Accessibility guidelines
Maintain, as far as possible, a bug free and high quality codebase
|
