Is possible known in advance which release of a package go on the stable branch?

[aleunix]

As example i take the package firefox.
If i take a look at the repository for the actual stable release:
http://ftp.openbsd.org/pub/OpenBSD/5.0/packages/amd64/
i see that now is present:
firefox-5.0p3.tgz
While if i take a look at the openports mozilla-firefox is present the 9.
Essentially i would like known if each time there is a new stable release the release of a package included on it is taken from the last release present on openports or using other system.
Or perhaps exist a way for see over the web with packages are actually present on the current release?

[jggimi]

It is my understanding that a port will be developed and tagged for the stable branch only if:

• There is a recognized security issue
• The dependency chain does not change
• There is available time and interest from the port's maintainer.

You may determine what version of a port will likely be in the next release by examining the CVS repository after it has been locked for the next release, as is the case at the moment.

[aleunix]

Where exactly i must see for understand that a package is locked?
Is it sufficient going here:
CVS log for ports/www/mozilla-firefox/distinfo
and see these tags:
CVS tags: OPENBSD_5_1_BASE, OPENBSD_5_1, HEAD
for be sure that will be the default?
Or perhaps i should see only this tag:
OPENBSD_5_1_BASE

[jggimi]

The Ports tree status was posted on the ports@ mailing list. Individual ports and ports development is discussed there.

What you have discovered is that Firefox 9 has been tagged for 5.1, but that does not at this point in the development cycle guarantee that is the final decision. It is likely, though. 5.1 has just been tagged in the repositories within the last several hours. There may be some minor additional changes over the next few weeks, a process the Project calls "release engineering."

[aleunix]

Is possible use a web interface for consult it?
OpenBSD Mailing List Server

The following mailing lists are available at OpenBSD Mailing List Server. Click the name of a list to see more information about that list, a subscription form, and a link to the message archives.

ports Discussion about the OpenBSD ports collection
Message Archives Summary of the Available Archives
I can't see anything ...

Perhaps, is the same?
Neohapsis > Archives > OpenBSD Security> cvs> OpenBSD CVS Commits> current

From Mailing Lists i tried even the marc mailing list:
Mailing list ARChives
openbsd-ports
but is complicated use it because there isn't a list for package.

[jggimi]

Packages are ports that have been compiled or otherwise assembled into installable modules.

I recommend subscribing to the ports@ mailing list so that you can stay in touch with ports developments.

For historical review, I recommend using either the MARC or Gmane archives, and you might consider using both. Both are active archives, each has positives and negatives.

Gmane has a threaded view which may be easier for you to use to follow discussions. I believe that MARC has easier to use search facilities.

Please note: MARC has missed some postings over the last year due to technical problems. Sometimes these problems are transient, but sometimes outages and missed messages have lasted for days or even weeks.

-----

Please take the time to review the differences between ports and packages as described in FAQ 15. You should also read FAQ 5.1 on the twice yearly development cycle, so that you understand release development.

---

An understanding of CVS tags as used by the project will also be helpful. OPENBSD_X_Y is a -stable tag, while OPENBSD_X_Y_BASE is a -release tag. Those two tags will point to equivalent patch levels unless there is a -stable patch. In the case of Firefox 9, as you noted above, the tags show that -current (HEAD) is at the same patch level as the next -release. For the moment.

[aleunix]

Perhaps a more fast and easy way for have an idea, with a good approximation, could be take a look at the OpenBSD snapshots packages amd64?

[jggimi]

No longer. Already, -current is beyond 5.1-release.