Re: Invite to join the Release Team
Hi dear Teams,
A few weeks ago, someone posted a link on planet.d.o, on how to
demotivate contributors (a wikipedia page)... unfortunately I can't find
the page anymore...
On Sun, 2010-03-14 at 00:02 +0100, Joerg Jaspert wrote:
> On 12053 March 1977, Luk Claes wrote:
> > You seem to send the message that you can judge from the sideline how
> > things should be run, so I hereby invite you to join the Release Team
> > and do a proper job.
> [..] The first was him taking the FTP team as an example for good communication
I have listed the announcements made by the Release team, and they seem
to spend quite some time doing it, as are quite a few entries (see below
Yes, the FTP team is trying to be transparent, and that's great. That's
no reason to pick on other teams. As usually, "patch welcome" applies (I
Some announcements made by the release team...
2008-07 : Etch updated (4.0r4) aka etch-and-a-half
2008-10 : Etch updated (4.0r5)
2008-12 : Etch updated (4.0r6)
2009-02 : Lenny Release update: deep freeze, planned dates, and remaining bugs
2009-02 : Etch updated (4.0r7)
2009-02 : Etch becomes old-stable.
2009-02 : Initial released : 5.0.0
2009-03 : Kicking off Squeeze: initial tidbits from the RMs
2009-04 : Etch updated (4.0r8)
2009-04 : Lenny updated (5.0.1)
2009-06 : Lenny updated (5.0.2)
2009-07 : Debian decides to adopt time-based release freezes
2009-07 : Bits from the release team and request for discussion
2009-07 : Debian GNU/Linux 6.0 "Squeeze" release goals
2009-08 : Bits from the release team: Release goals, schedule, state of the union
2009-09 : Lenny updated (5.0.3)
2009-09 : Release Team, BTS, and debian-release@ policy.
2009-10 : Bits from the release team: Planning, request for help]]
2010-01 : Lenny updated (5.0.4)
2010-02 : Release architectures
2010-02 : End of security updates / End of life.
2010-02 : Bits from the Stable Release Team