| 169 | == Release Schedule == |
| 170 | |
| 171 | * Quarterly release schedule, with the target release date the 15th of the first month of each quarter. |
| 172 | |
| 173 | * If a release is late, that does not slip the date of the next quarter's release. |
| 174 | |
| 175 | * If something isn't ready for the current release, it is simply held until the next release. The current release is not delayed. |
| 176 | |
| 177 | * Being ready means being ready by the cutoff date set by the release manager. That will be relative early in the release cycle. |
| 178 | |
| 179 | === Rationale === |
| 180 | |
| 181 | Regular releases that occur on a predictable schedule have many benefits: |
| 182 | |
| 183 | * Developers know far in advance when library updates must be ready, and that's both an aid to planning and a motivation to get stuff done. |
| 184 | |
| 185 | * Users know far in advance when library updates will be ready, and that helps their planning and reassures them of continuing support. |
| 186 | |
| 187 | * Regularity creates a sense of quality and trust in Boost for both developers and users. |
| 188 | |
| 189 | Quarterly releases seem about right: |
| 190 | |
| 191 | * It's often enough that the process will become smooth. |
| 192 | |
| 193 | * It's often enough that developers won't feel pressure to release immature updates. |
| 194 | |
| 195 | * It's often enough that users will feel bug fixes and new libraries are being released on a timely basis. |
| 196 | |
| 197 | * It isn't so often that users will view Boost as unstable, particularly given the predictable schedule. |
| 198 | |
| 199 | * It isn't so often that developers and release managers will become fatigued. |
| 200 | |
| 201 | * A quarterly (or similar) schedule has been very successful for both open source and commercial projects. |
| 202 | |