FreeBSD 7.3 release engineering TODO

This is the FreeBSD 7.3 release engineering wiki page. It tracks the status of the FreeBSD 7.3 release process, including schedule, branching condition, change request queues, TODO lists, known issues, and more. It is updated regularly during the release process.

Please only edit this page if you are a member of the release engineering team, or if a member of the release engineering team has asked you to do so.

Release Status

FreeBSD 7.3 release cycle is past the point of no return.

Last updated: 23 March 2010

Release Schedule

All dates can/will change.

Action

Expected

Actual

Publicly announced

Initial release schedule announcement

-

2010-01-06

2010-01-23

Release schedule reminder

-

2010-01-16

-

Code Freeze

2010-01-22

2010-01-23

-

BETA1

2010-01-25

2010-01-27

2010-01-30

Doc tree schedule announcement

-

2010-01-31

2010-01-31

Doc tree slush

2010-02-05

2010-02-05

2010-02-05

Doc tree tag

2010-02-10

2010-02-10

2010-02-10

Ports tree schedule announcement

-

2010-01-31

2010-01-31

Ports tree feature freeze

2010-02-08

2010-02-15

2010-02-15

RC1

2010-02-08

2010-02-09

2010-02-15

stable/7 opened again

-

2010-02-22

-

RC2

2010-02-22

2010-03-01

2010-03-04

RELEASE build

-

2010-03-21

-

RELEASE announcement

2010-03-01

2010-03-23

2010-03-23

CAUTION: FreeBSD release schedules frequently slip -- the above release schedule should be interpreted with this caution in mind.

Branch status

Action

Status

Subversion: releng/7.3 created

DONE 2010-02-10

Subversion: release/7.3.0 created

DONE 2010-03-21

CVS: RELENG_7_3 created

DONE 2010-02-10

CVS: RELENG_7_3_0_RELEASE created

DONE 2010-03-21

Tinderbox: RELENG_7_3 configured

Change approval and merge guidelines

Change request guidelines

In order to submit a patch to the release engineering patch queue, you must be a FreeBSD developer able to commit the patch. If you are not a committer, you will need to identify a committer to proxy your request.

Please follow these guidelines when submitting patches -- all submissions must:

  1. include complete patches inline or attached to the e-mail; a URL is not sufficient.
    • Use "svn diff -x -p" where appropriate. Diff at the src/ or src/sys. The diff shall be done against merged tree, and include the svn:mergeinfo changes.
  2. be fully build- and run-time tested.
  3. be reviewed before submission; include this review information with your submission.
  4. include a proposed commit message.
  5. unless exceptional circumstances apply, have baked in head for at least three days before a merge is requested.
  6. include the head revision number that will be merged.

Requests that do not follow these guidelines may be rejected without further consideration.

Change merge guidelines

The following guidelines must be followed when merging changes from head to stable/7:

  1. Unless approved by the release engineering team, changes must be committed to head before being merged to stable/7.
    • Ideally they would have been tested in stable/8 as well.
  2. When merging, use the instructions found in SubversionPrimer/Merging.
    • Each changeset committed to head must be merged using svn merge as a single changeset to stable/7.
  3. Do not manually edit changes being merged to stable/7 without release engineering approval.
  4. Pay particular attention to the placement of mergeinfo.
  5. When committing the merge, include the original revision number (rXXXXXX) and a copy of the original commit message in the merge commit message.

Contact the release engineering team if you require assistance with the use of svn merge.

Release engineering issue and patch queue

The being-fixed and still-being-researched pile

A list of things Release engineering got asked about, made an enquiry about or has picked up from public discussions.

Blanket approvals

The following blanket approvals are valid until BETA1:

The following blanket approvals are valid until RC1:

The following blanket approvals extend into the RC series:

The waiting for approval pile

This includes only changes requested as of 20100123

The additional review or revisions sought pile

Sometimes the release engineering team will solicit further review or revisions for patches received; this list includes only changes requested as of 20100123.

The approved and queued for commit pile

These changes have been approved for merge to stable/7 and releng/7.3:

Committed fix pile

Changes that now appear in stable/7; this list includes only changes requested as of 20100123:

After BETA1:

After RC1 (changes go to stable/7 and releng/7.3):

The change request withdrawn pile

Changes in this list were requested, and then later withdrawn. This list includes only changes requested as of 20100123.

Rejected change request pile

This list contains changes requested during the end portion of the release cycle that were rejected, most likely due to the late point in the release cycle. This includes only changes requested as of 20100123.

This list contains changes requested during the end portion of the release cycle that were rejected, most likely due to the late point in the release cycle. This includes only changes requested as of 20100209 (past start of RC1). Please note that some of those were actually just informal requests to ask for an opinion from Release Engineering.

Likely errata items

The following known issues are unlikely to be resolved before FreeBSD 7.3, and may require errata items:

Leading up to the release

Prior to beginning the release process, the following areas were known to require work, including projects that were late wrapping up, or issues that required resolution to cut the release.

Known issues when the release process started

Releng/7.3TODO (last edited 2010-03-23 18:19:52 by BjoernZeeb)