Blame
| ca8eb9 | Samuli Seppänen | 2025-03-19 12:09:12 | 1 | # Release cycle for a major OpenVPN version (WIP) |
| 2 | ||||
| 3 | ## Cycle length |
|||
| 4 | ||||
| 5 | Do we follow the debian stable release cycle? |
|||
| 6 | ||||
| 7 | ## Feature Freeze |
|||
| 8 | ||||
| 9 | Based on when we need to be ready to get the new release in the next debian release, we consequently plan our feature freeze. |
|||
| 10 | ||||
| 11 | At that point, after a few day we release our beta. |
|||
| 12 | ||||
| 13 | Once the Beta has got enough attention and bugfixes we release rc1. |
|||
| 14 | ||||
| 15 | Testing by broader audience is at this point automatic and more bug reports may come in. |
|||
| 16 | ||||
| 17 | After a few round of release candidates, i.e. around rc5/6, if the waters start to calm down, we call it stable and release 2.x.0 |