At the request of adamw@ (and others) we have setup a ports-announce@ mailing list to try distinguish the usual traffic on the ports@ list vs the announcements that seem to get lost in there.
You can subscribe at http://lists.freebsd.org/mailman/listinfo/freebsd-ports-announce
It is intended, but not limited, to be a means of communicating portmgr@ announcements, Calls for Testing, plus other relevant information to be used by our committers and ports maintainer community.
It is our hope to keep this relatively low in traffic. It is a moderated list, under the auspices of portmgr@.
Please subscribe, sit back, and enjoy.
on behalf of portmgr@
We are pleased to announce the addition of Beat Gaetzi (beat@) to the team. Beat, like many others was a long time contributor prior to receiving his commit bit in 2009. Beat is well know for his work with the Gecko and Vbox teams, in addition to his hosting of test/development repositories for many of our community members.
Beat’s next unenviable task will be taking us through the rocky road ahead in migrating the CVS Ports repository to Subversion.
Please join me in welcoming Beat to the team. Congratulations Beat!
on behalf of portmgr@
With this commit, http://svnweb.freebsd.org/base?view=revision&revision=227337, the RC2 phase is under way.
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.
on behalf of portmgr@
We would like to publicly thank the FreeBSD Foundation for granting Baptiste Daroussin and Julien Laffaye a travel grant to travel to BSDCan 2011 for the Ports and Packages Working Group held at in Ottawa last week. The working group itself was a huge success and a number of improvements with regard to automated binary package creation and distribution to ease upgrade procedures for our users were discussed and will hopefully be implemented over the next few months.
None of these improvements, however, would be possible without a long overdue rewrite of the package tools provided by FreeBSD. Over last few years, a number of attempts were made to enhance the current tools, but none have been as all-compassing as the PKGNG project by Baptiste and Julien. The presentation given by Baptiste at the packages summit and summariszed at the DevSummit track of BSDCan showed a comprehensive new tool that can completely replace the current tools, and provide a clear migration path from the old to the new tool. It also provides a large number of new features while keeping the old ones and is a lot more flexible to be able to add more features later. As you may have heard, Baptiste has also joined the ports management team as a result of his efforts.
Thanks again to the Foundation for sponsoring Baptiste, Julien, Simon Nielsen (Deputy Security Officer) and Thomas Abthorpe (Ports Management Team) who all were instrumental into making the ports working group such a success.
on behalf of portmgr@
The Ports Management team is pleased to announce that Thomas Abthorpe, tabthorpe@, has become a full voting member of the team. He will continue in his substantive postion as the -secretary in addition to other duties he will pick up along the way.
The FreeBSD Ports Management Team wishes to remind users that November 30
is also the end of support for the Ports Collection for both FreeBSD 6.4
RELEASE and the FreeBSD 6.x STABLE branch. Neither the infrastructure nor
individual ports are guaranteed to work on these FreeBSD versions after
that date. A CVS tag will be created for users who cannot upgrade for some
reason, at which time these users are advised to stop tracking the latest
ports CVS repository and use the RELEASE_6_EOL tag instead.
While many people still use RELENG_6, it is at the end of it’s development
cycle. The Ports Management team has set the following policies with regard
to EOL/EOS of this branch and we kindly ask developers to implement these:
- We will keep building 6.4 packages as long as we have the resources.
6.x package builds will however be deprioritised, meaning they will not
be rebuilt as frequently.
- We will continue to support the 6.x infrastructure until RELENG_6
EOL (11/30/2010) by building the INDEX on RELENG_6 for use by ‘make
fetchindex’, and making sure that the ports collection infrastructure
(bsd.port.mk, etc) continues to function on RELENG_6, subject to the
reduced testing that this branch will receive. This means that problems
may be noticed only after the fact and may require community support to
develop and test fixes.
- We do not require committers/maintainers to support 6.x, but ports
will need to be marked BROKEN/IGNORE if they do not build/run.
- Port maintainers are strongly encouraged to accept patches from the
community that allow their ports to build and run on 6.x. However,
since running on 6.x is no longer a requirement, maintainers may use
their discretion in cases where a proposed patch would be disruptive
to other supported FreeBSD branches, or would unreasonably impede
ongoing maintenance of the port.
- We will continue to accept patches for ports collection infrastructure
- We encourage all users and developers to migrate to the FreeBSD 7.x or
8.x branch, both of which is a stable and mature platform, and are now
the ‘reference’ branches for the ports collection.
Please also see the secteam@ announcement,
Just in case you missed it on the mailing list, http://lists.freebsd.org/pipermail/freebsd-ports/2010-June/061882.html, the tentative date for Feature Freeze will be June 18, noonish UTC.
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.
During the month of May, we were fortunate enough to see the return of two old committers. Marc Fournier, aka scrappy@, well known for http://www.bsdstats.org, and Ade Lovett, aka ade@, aka Mr. Autotools.
Please feel free to drop them a note to say welcome back