The ports tree is now tagged and partially thawed. Â Until 8.0 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.
As an experiment, there will not be a complete ports freeze ahead of theÂ release of 8.0. Â To ensure that the tree is kept in a stable condition,Â we do need to have more discipline about the feature freeze we areÂ currently using. Â To achieve this, I have added a new tag to the commitÂ log Feature safe: which needs to be set to yes explicitly for eachÂ commit. Â While this is is tedious, it does mean that commits will beÂ allowed without prior explicit approval from portmgr. Â Portmgr is stillÂ working on a written set of rules for what is and isn’t allowed during aÂ feature freeze, so please use common sense for now, and try to err onÂ the side of caution and contact portmgr when in any doubt. Â SweepingÂ commits touching a large number of ports, shared library updates affectÂ more than a trivial number of ports, you get the picture; anything thatÂ would require a rebuild of more than a trivial amount of ports is notÂ allowed without prior approval from portmgr. Â With the release only aÂ few weeks off, we cannot afford any major mishaps, so be conservative.
The feature freeze is enforced from right now and current plan is to tagÂ the tree after RC1 is released. Â There will be a short freeze while theÂ tag is processed, and after that we will proceed with the ports slush asÂ usual.
Please consider your commits in this light and help make this experimentÂ a success so we can avoid long freezes for future releases.