For those who haven’t noticed the announcement on the ports mailinglist, or noticed the flood of commits that started already before the announcement, the ports tree has been thawed, with the usual restrictions (see my announcement below). Note that the first committer to break INDEX will owe all portmgrs a beer at the next BSD conference, and a carton of beer if it’s within the next 24 hours.
The ports tree is now in “thaw” state after the tree has been tagged for
the 6.3 and 7.0 releases. This means that most normal commit that
affect only _one_ port are allowed. Sweeping changes are specifically
not allowed and when in doubt, please don’t hesitate to ask portmgr.Please also take into account that the 7.0 release won’t be for several
weeks yet, so we reallly need you all to be careful about what you
commit as we tags might need to be slipped later. Also, please contact
portmgr for any security related commits to get the tag slipped. For a
more detailed description of what is, and what is not, allowed, please
see: http://www.freebsd.org/portmgr/implementation.html#sweeping_changesThank you for your patience,
-erwin
Related posts:
- Ports tree frozen in preparation for 7.2-RELEASE The ports tree is now frozen for the 7.2 release...
- Ports feature freeze now enforced As an experiment, there will not be a complete ports...
- Partial ports thaw The ports tree is now tagged and partially thawed. Until...
- Partial ports thaw The ports tree is now tagged and partially thawed. Until...
- Ports freeze schedule for FreeBSD 8.0-RELEASE Below is the tentative schedule for the ports freeze in...
Related posts brought to you by Yet Another Related Posts Plugin.