Date: Thu, 2 Aug 2018 11:20:32 +0000 (UTC) From: Eitan Adler <eadler@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52075 - head/en_US.ISO8859-1/htdocs/portmgr Message-ID: <201808021120.w72BKWdU034488@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: eadler Date: Thu Aug 2 11:20:31 2018 New Revision: 52075 URL: https://svnweb.freebsd.org/changeset/doc/52075 Log: portmgr/qa: make a simple pass - We have not done ports freezes for a long time, and not used CVS in even longer - Replace pointyhat ref with pkg-status - Reference quarterly branches Modified: head/en_US.ISO8859-1/htdocs/portmgr/qa.xml Modified: head/en_US.ISO8859-1/htdocs/portmgr/qa.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/portmgr/qa.xml Thu Aug 2 10:57:07 2018 (r52074) +++ head/en_US.ISO8859-1/htdocs/portmgr/qa.xml Thu Aug 2 11:20:31 2018 (r52075) @@ -35,70 +35,15 @@ two main categories: </li> <li> - <p>Manage commits to the CVS tree for package builds via the - following steps:</p> - - <ol> - <li> - <p>Institute a freeze and produce packages for all the - appropriate architectures. Often this process has to be - repeated because either bugs are identified in various ports, - or changes to the src tree create a risk that the packages - that have already been built would not work with those - changes.</p> - - <p>To make sure that package builds are consistent and correct, - <i>all</i> commits must be approved by portmgr during a - freeze. Changes that are generally approved are:</p> - - <ul> - <li><p>fixes to make a package build at all;</p></li> - <li><p>security fixes to critical packages;</p></li> - <li><p>problems that are noticed with licensing issues.</p></li> - </ul> - - <p>Unfortunately, due to the sheer size of the Ports Collection - and the speed that applications are developed, it is - impossible to fix every single problem for a release.</p> - </li> - - <li> - <p>The tree is then locked for all commits and a CVS tag is laid - down.</p> - </li> - - <li> - <p>The tree is then unlocked and a <tt>slush</tt> is - announced. The intent of this state is to allow routine - changes to be made to the Ports Collection, but with the note - that these changes will not ship on the release ISOs. What - we particularly want to avoid is - <a href="implementation.html#sweeping_changes"> - sweeping changes</a>.</p> - - <p>The reason we want to avoid these commits is if some kind - of show-stopper problem is found (either security- or license- - related) such that we need to make a change that can go on - the release ISOs, we will need to slip the CVS tag on the - changed file(s). By allowing unlimited commits, the risk is - high that any such change would involve having to recreate all - the packages all over again, resulting in an endless release - cycle.</p> - </li> - </ol> - - <p>Only once the RE team and portmgr are happy with the final - state of the release ISOs is the ports tree completely available - for commits again.</p> + <p>Cut over to the new quarterly branch.</p> </li> - </ul> <h3><a name="qa-between-releases">Activities Between Release Cycles</a></h3> <ul> <li> - <p>Manage the <a href="http://pointyhat.FreeBSD.org">Ports Build + <p>Manage the <a href="https://pkg-status.freebsd.org/">Ports Build Cluster</a> machines. These machines continually build packages on all possible combinations of OS release and CPU architecture (in our terminology, <tt>build environments</tt>.)</p>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201808021120.w72BKWdU034488>