DokuWiki Installer

:

This page assists in the first time installation and configuration of Dokuwiki. More info on this installer is available on it's own documentation page.

DokuWiki uses ordinary files for the storage of wiki pages and other information associated with those pages (e.g. images, search indexes, old revisions, etc). In order to operate successfully DokuWiki must have write access to the directories that hold those files. This installer is not capable of setting up directory permissions. That normally needs to be done directly on a command shell or if you are using hosting, through FTP or your hosting control panel (e.g. cPanel).

This installer will setup your DokuWiki configuration for ACL, which in turn allows administrator login and access to DokuWiki's admin menu for installing plugins, managing users, managing access to wiki pages and alteration of configuration settings. It isn't required for DokuWiki to operate, however it will make Dokuwiki easier to administer.

Experienced users or users with special setup requirements should use these links for details concerning installation instructions and configuration settings.

For security reasons this script will only work with a new and unmodified Dokuwiki installation. You should either re-extract the files from the downloaded package or consult the complete Dokuwiki installation instructions

driven by DokuWiki powered by PHP
Branching and Release Management Policy [Mantis Bug Tracker Wiki]

User Tools

Site Tools


mantisbt:development_scheme

Branching and Release Management Policy

There are usually two active branches at any given time:

  • The stable branch
  • The development branch

Release packages from stable and development branches are linked on the home page.

Between releases, the latest code is always available from our Subversion repository

Stable branch policy

The stable branch should receive only the most important bug fixes, so that:

  1. The development resources are focused on development branch, avoiding porting efforts when possible.
  2. The stable branch is kept very stable and hence guarantee a safe upgrade path for everybody

For these reasons, we will fix on the stable branch the following kind of issues:

  • Bugs with category “security”
  • Critical bugs like deployment stoppers, blank screens, installation and upgrade issues
  • Bugs that are generating a lot of support requests

If unsure, feel free to ask on the mantisbt-dev mailing list

Development Branch Policy

The development branch (i.e. SVN trunk) is where all the “interesting” things happens; new features and bug fixes are usually applied here first, then tested and ported to the stable branch when deemed necessary.

Whenever the development branch reaches a state considered good enough for becoming the “stable” one, the following happens:

  • A new branch is created from SVN trunk
  • A release candidate (RC) is created off this new branch
  • The RC branch enters in a “feature freeze” mode (no new features added)
  • Testing and bug fixing continue on the RC branch until it can be declared stable

During feature freeze:

  • New features can still enter SVN trunk, but all developers are encouraged to help polishing the RC branch before focusing again on the development branch.
  • No official releases are composed from SVN trunk (that is, the soon-to-be development branch)
  • ONLY CRITICAL FIXES are applied to the stable branch

At release time:

  • The RC branch becomes the new stable branch
  • Support ends for the old stable branch
  • Normal development resumes on SVN trunk
mantisbt/development_scheme.txt · Last modified: 2008/10/29 04:25 (external edit)