Development cycle
This page lists our development cycle. Individual release schedules can be found here.
Contents |
Introduction
BibleTime will provide two full releases every year. The first of these releases will be done in the end of May, the second release will be done in the end of November, just before Advent.
Schedule of a development cycle
| Start | Description |
|---|---|
| Month 0 |
|
| Month 3 |
|
| Month 4 |
|
| Month 5, week 0 |
|
| Month 5, week 2 |
|
| Month 6 |
|
Feature freeze
No new features are allowed into trunk. Minor changes to existing features are still allowed.
Stable branch creation
A new stable branch is created from the master branch, and the master branch will be unfrozen. Here's the procedure:
| COMMAND LINE: Stable branch creation example for 2.8 with git |
|
cd /path/to/bibletime.git
git co master
git branch stable-2.8
|
Now changes to the new branch can be made. Finally, while still having the new branch checked out it has to be pushed (published) to the remote repository:
| COMMAND LINE: Stable branch publishing example for 2.8 with git |
|
git push origin stable-2.8
|
String freeze
In addition to the restrictions of a feature freeze, no changes to translatable strings are allowed. When entering the string freeze, translators are notified.
