Release Process Guidelines

Discuss general development subjects that are not specific to a particular version like the versioning control system we use or other infrastructure.
Locked
User avatar
naderman
Product Manager
Product Manager
Posts: 1727
Joined: Sun Jan 11, 2004 2:11 am
Location: Karlsruhe, Germany
Contact:

Release Process Guidelines

Post by naderman » Fri Feb 05, 2016 6:02 pm

This sticky is used to document decisions by/for release managers.

Announcement Policy
  • Alpha releases
    • Should be announced internally to all team members, ISTs and translators
    • Should be announced on Area51, in the discussion forum for the major release
    • May optionally be published on the blog
  • Beta releases
    • Should be announced internally to all team members, ISTs and translators
    • Should be announced on Area51, in the discussion forum for the major release
    • Should be published on the blog
    • Should be marketed on social media (Twitter and Facebook)
  • RC releases
    • Should be announced internally to all team members, ISTs and translators
    • Should be announced on Area51, in the discussion forum for the major release
    • Should be announced in the announcement forum on phpbb.com
    • Should be marketed on social media (Twitter and Facebook)
  • Final releases
    • Should be announced internally to all team members, ISTs and translators
    • Should be announced on Area51, in the discussion forum for the major release
    • Should be announced in the announcement forum on phpbb.com
    • Should be marketed on social media (Twitter and Facebook)
    • Should be announced to the release mailing list
Please create a new topic if you want to discuss any of these policies

Locked