Update the release manager guide to clean up the tagging instructions
[p5sagit/p5-mst-13.2.git] / Porting / release_schedule.pod
CommitLineData
ede492aa 1=head1 Release schedule
07962d9a 2
3This document lists the release engineers for at least the next
4four months of releases of bleadperl. If there are fewer than
5four months listed as you make a release, it's important
6that you extend the schedule AND B<identify the next release engineer>.
7
8Before adding a release engineer, you B<must> contact them and they
9B<must> consent to ship the release.
10
11When shipping a release, you should include the schedule for (at least)
12the next four releases. If a stable version of Perl is released,
13you should reset the version numbers to the next blead series.
14
15=head2 2009
16
17 October 2 - 5.11.0 - Jesse Vincent
18 October 20 - 5.11.1 - Jesse Vincent
19 November 20 - 5.11.2 - Yves Orton
20 December 20 - 5.11.3 - Leon Brocard
21
ede492aa 22=head2 2010
07962d9a 23
24 January 20 - 5.11.4 - Ricardo Signes
25
26=head1 VICTIMS
27
28The following porters have all consented to do at least
29one release of bleadperl. If you can't do a release
30and can't find a substitute amongst this list, mail p5p.
31
32Jesse Vincent <F<jesse@cpan.org>>
33Leon Brocard <F<acme@astray.com>>
34Yves Orton <F<demerphq@gmail.com>>
35Ricardo Signes <F<rjbs@manxome.org>>
36
37=head2 Reticent victims
38
39These folks have said that they'd be willing to release Perl but would
40prefer that others have the opportunity before they pitch in:
41
42David Golden <F<xdave@gmail.com>>
43
44
45=head1 AUTHOR
46
47Jesse Vincent <F<jesse@cpan.org>>
48
49=cut