Bug 173426 - [PATCH] www/opera: update to 12.10
Summary: [PATCH] www/opera: update to 12.10
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Dirk Meyer
Depends on:
Reported: 2012-11-06 17:10 UTC by Mark Felder
Modified: 2012-11-08 04:23 UTC (History)
1 user (show)

See Also:

opera-12.10.patch (4.99 KB, patch)
2012-11-06 17:10 UTC, Mark Felder
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Felder freebsd_committer 2012-11-06 17:10:00 UTC
update to 12.10


Port maintainer (dinoex@FreeBSD.org) is cc'd.

Generated with FreeBSD Port Tools 0.99_6 (mode: change, diff: suffix)
Comment 1 Edwin Groothuis freebsd_committer 2012-11-06 17:10:08 UTC
Responsible Changed
From-To: freebsd-ports-bugs->dinoex

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Dirk Meyer freebsd_committer 2012-11-06 17:43:21 UTC
State Changed
From-To: open->suspended

13.5.2. What is a "ports slush" or "feature freeze"? 

During a release cycle the ports tree may be in a "slush" state instead of in a hard freeze. The goal during a slush is to reach a stable ports tree to avoid rebuilding large sets of packages for the release and to tag the tree. During this time "sweeping changes" are prohibited unless specifically permitted by portmgr. Complete details about what qualifies as a sweeping change can be found on the Portmgr Implementation page. 

The benefit of a slush as opposed to a complete freeze is that it allows maintainers to continue adding new ports, making routine version updates, and bug fixes to most existing ports, as long as the number of affected ports is minimal. For example, updating the shared library version on a port that many other ports depend on.
Comment 3 Dirk Meyer freebsd_committer 2012-11-08 04:22:10 UTC
State Changed
From-To: suspended->closed

committed, thanks.