The ports tree is now tagged and partially thawed. Until 7.2 is released, sweeping commits still need explicit approval from portmgr to assure that tags can be slipped for potential security issues. For more information what constitutes a sweeping change, see the portmgr web pages.

The ports tree is now frozen for the 7.2 release cycle.

No commits will be allowed without explicit portmgr approval. We hope we can keep the freeze short and go into slush after two weeks. The tree will be completely unfrozen after the release is announced. For the full schedule, see the release schedule.

As always, only commit that fix existing breakage will be allowed during the freeze and we encourage everyone will help fix as many ports as possible for this release. For more information about what kinds of commits are allowed during which period, please see the portmgr policies webpage.

The ports freeze for the upcoming release of 7.2 will start in one week time on April 13. Release packages will be built immediately and have to be ready for RC2 which is scheduled for April 20. To keep the freeze as short as possible, the date might be moved depending on any delays in the src release process. Also, to keep this freeze this short we kindly ask anyone with commits in their queues that might have any larger effect on the packages to run their changes by portmgr from today to make sure no new regressions are introduced.

As always, we are looking for volunteers to fix outstanding errors, and this is a good time to focus on existing errors and regressions instead of new features to make sure as many packages can be included in the
release.

For a list of outstanding build errors, please see this link.

Remember: All commits after April 13 need explicit approval from portmgr!