Re: [HEADSUP]: ports feature freeze starts soon
On Fri, Oct 07, 2011 at 11:20:28AM +0200, Erwin Lansing wrote: In preparation for 9.0 the ports tree will be in feature freeze after release candidate 2 (RC2)is released, currently planned for October 17. Depending on your timezone, October 17 has come and gone and the ports tree has not frozen yet. As always, we'll follow the actual dates during the release cycle and not the estimated dates in the tentative schedule. A rough guess would be that RC2, and thus the ports feature freeze, will happed at the end of the month, so please take this as a reminder to get anything you want included in the release into the tree as soon as possible. Erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Fwd: Re: [HEADSUP]: ports feature freeze starts soon
Just on case anyone's not on ports@: -- Forwarded message -- From: Chris Rees cr...@freebsd.org Date: 8 Oct 2011 10:30 Subject: Re: [HEADSUP]: ports feature freeze starts soon To: Thomas Mueller mueller6...@bellsouth.net Cc: freebsd-po...@freebsd.org, Erwin Lansing er...@freebsd.org On 8 October 2011 10:22, Thomas Mueller mueller6...@bellsouth.net wrote: from Erwin Lansing er...@freebsd.org: In preparation for 9.0 the ports tree will be in feature freeze after release candidate 1 (RC2)is released, currently planned for October 17. Was there a typo here? Did you mean release candidate 1 or 2? RC1 seems more logical, since RC1 has not been released yet, and October 17 is only nine days away. -- Forwarded message -- From: Erwin Lansing er...@freebsd.org Date: 7 October 2011 17:34 Subject: Re: [HEADSUP]: ports feature freeze starts soon To: develop...@freebsd.org develop...@freebsd.org On Oct 7, 2011, at 11:20, Erwin Lansing er...@freebsd.org wrote: In preparation for 9.0 the ports tree will be in feature freeze after release candidate 1 (RC2)is released, currently planned for October 17. Sorry about the typo, just to be clear I did mean RC2, not RC1 as usual as an RC3 has been planned in this release cycle. Erwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[HEADSUP]: ports feature freeze starts soon
In preparation for 9.0 the ports tree will be in feature freeze after release candidate 1 (RC2)is released, currently planned for October 17. If you have any commits with high impact planned, get them in the tree before then and if they require an experimental build, have a request for one in portmgr hands within the next few days. Note that this again will be a feature freeze and not a full freeze. Normal upgrade, new ports, and changes that only affect other branches will be allowed without prior approval but with the extra Feature safe: yes tag in the commit message. Any commit that is sweeping, i.e. touches a large number of ports, infrastructural changes, commts to ports with unusually high number of dependencies, and any other commit that requires the rebuilding of many packages will not be allowed without prior explicit approval from portmgr after that date. -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[HEADSUP] ports feature freeze starts soon
In preparation for 8.1-RELEASE, the ports tree will be in feature freeze after release candidate 1 (RC1) is released, currently planned for June 11. If you have any commits with high impact planned, get them in the tree before then and if they require an experimental build, have a request for one in portmgr@ hands within the next few days. Note that this again will be a feature freeze and not a full freeze. Normal upgrade, new ports, and changes that only affect other branches will be allowed without prior approval but with the extra Feature safe: yes tag in the commit message. Any commit that is sweeping, i.e. touches a large number of ports, infrastructural changes, commits to ports with unusually high number of dependencies, and any other commit that requires the rebuilding of many packages will not be allowed without prior explicit approval from portmgr@ after that date. Thomas with portmgr-secretary@ hat on -- Thomas Abthorpe | FreeBSD Ports Management Team Secretary tabtho...@freebsd.org | portmgr-secret...@freebsd.org pgplW61OQcvRl.pgp Description: PGP signature
