Xfce development and release model

[Jannis Pohlmann]

Hey,

On Wed, 27 May 2009 18:04:08 +0200
Jannis Pohlmann <jannis at xfce.org> wrote:

> So, without further ado, here's the document:
> 
>   http://wiki.xfce.org/releng/release-policy

I've updated the document to clarify a few more things about which
concerns were raised:

  * the planning phase is now 2+2 weeks, allowing maintainers who were
    unavailable the first 2 weeks to request dependency changes later

  * after the 2+2 weeks planning phase, there is a dependency freeze
    which means no further changes to dependencies may be made, unless
    they are optional

  * API breakage in the development phase should be communicated and
    people should prepare other components for a release that
    introduces API breakage so that they can soon return to a
    release-ready state

  * there's a 2-days code freeze before each pre-release

  * there's a UI freeze at the same time as string freeze

  * bugfixes and release-critical changes may be committed to master
    during code freeze if, and only if they are signed off the release
    manager

I'll reply to the rest of the feedback soon. Please note that the
graphics on the page are currently out of date and the maintenance
process still has to be defined more detailed (like the support time
of maintenance cycles).

  - Jannis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://mail.xfce.org/pipermail/xfce4-dev/attachments/20090528/22125bae/attachment.pgp>