| | 110 | |
| | 111 | == Release Manager == |
| | 112 | |
| | 113 | The current release manager is Ryan52 starting from 0.46 (Sept 2009) for about one month |
| | 114 | |
| | 115 | == Release schedule == |
| | 116 | |
| | 117 | The exact release schedule is decided by the current release manager, below are the general guidelines |
| | 118 | |
| | 119 | Padre is released to CPAN about once every week when trunk seems to be in a stable state. |
| | 120 | |
| | 121 | Once a month we set aside a version for a "packaged" release for which we use a longer time on the release branch. |
| | 122 | |
| | 123 | We take the latest regular release and base the "packaged" release right on the regular release. |
| | 124 | So for example we have 0.43, 0.44, regular releases then based on 0.44 we create a release branch for 0.45 |
| | 125 | We give the translators a few days to catch up on this branch. That time will also allow |
| | 126 | people to give feedback on 0.44 so we can fix really critical issues on the 0.45 branch. |
| | 127 | |
| | 128 | This release should be scheduled just a few days after Rakudo is released. |
| | 129 | |
| | 130 | Once it is done CSJewell creates the windows [wiki:Distribution distributions] based on Strawberry Perl. |
| | 131 | |
| | 132 | That means we have these "packaged" and translated releases by ~ 20-25th of every month. |
| | 133 | |