FreeBSD The Power to Serve

FreeBSD 9.3 Release Process

Introduction

This is the release schedule for FreeBSD 9.3. For more information about the release engineering process, please see the Release Engineering section of the web site.

General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list. MFC requests should be sent to re@FreeBSD.org.

Schedule

Action

Expected

Actual

Description

Initial release schedule announcement

-

4 March 2014

Release Engineers send announcement email to developers with a rough schedule.

Release schedule reminder

4 April 2014

11 April 2014

Release Engineers send reminder announcement e-mail to developers with updated schedule.

Code slush begins

9 May 2014

9 May 2014

Release Engineers announce that all further commits to the stable/9 branch will not require explicit approval, however new features should be avoided.

Code freeze begins

23 May 2014

23 May 2014

Release Engineers announce that all further commits to the stable/9 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc.

BETA1 builds begin

30 May 2014

30 May 2014

First beta test snapshot.

BETA2 builds begin

6 June 2014

6 June 2014

Second beta test snapshot.

BETA3 builds begin

13 June 2014

13 June 2014

Third beta test snapshot.

releng/9.3 branch

20 June 2014

20 June 2014

Subversion branch created; future release engineering proceeds on this branch.

RC1 builds begin

20 June 2014

20 June 2014

First release candidate.

RC2 builds begin

27 June 2014

27 June 2014

Second release candidate.

RC3 builds begin

4 July 2014

4 July 2014

Third release candidate.

RELEASE builds begin

11 July 2014

11 July 2014

9.3-RELEASE builds begin.

RELEASE announcement

16 July 2014

16 July 2014

9.3-RELEASE press release.

Turn over to the secteam

-

30 July 2014

releng/9.3 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information