The OpenBSD release cycle is different from most other projects. We do *everyting* in the HEAD branch, including preparation for releases. That includes changing the release name. A release, is simply a snapshot from a specific day. We're almost at that day (but won't say which one, until the official release happens). http://www.openbsd.org/papers/asiabsdcon2009-release_engineering/mgp00017.html
Theo talked about the process at AsiaBSDCon 2009, we're at the "Tree Locks" part of the diagram shown here: http://www.openbsd.org/papers/asiabsdcon2009-release_engineering/mgp00020.html Hope this helps! On 2017 Sep 30 (Sat) at 12:21:00 +0200 (+0200), Pau wrote: :Hi: : :That's my question. I've been running -current for the last 4 months :or so and I have noticed that : :$ uname -a : :shows : :OpenBSD xxxxxxxx 6.2 GENERIC.MP#120 amd64 : :$ dmesg | grep OpenBSD : :shows : :OpenBSD 6.2 (GENERIC.MP) #117: Thu Sep 28 11:57:37 MDT 2017 :OpenBSD 6.2 (RAMDISK_CD) #116: Thu Sep 28 12:02:00 MDT 2017 :OpenBSD 6.2 (GENERIC.MP) #117: Thu Sep 28 11:57:37 MDT 2017 :OpenBSD 6.2 (RAMDISK_CD) #117: Fri Sep 29 10:51:41 MDT 2017 :OpenBSD 6.2 (GENERIC.MP) #118: Fri Sep 29 10:47:18 MDT 2017 :OpenBSD 6.2 (RAMDISK_CD) #119: Sat Sep 30 03:06:49 MDT 2017 :OpenBSD 6.2 (GENERIC.MP) #120: Sat Sep 30 03:02:26 MDT 2017 : :Also, when I update the packages, if I run : :$ pkg_add -Iuv : :pkg_add does not complain, and I would expect it to complain unless I :added a -D snap flag to it : :When I boot from : :> boot bsd.rd : :the URL path suggested is : :pub/OpenBSD/6.2/amd64 : :instead of : :pub/OpenBSD/snapshots/amd64 : :It looks as if the system "thinks" I am running 6.2, while I am :running -current. : :What is the reason for this? : :thanks, : :Pau _______________________________________________ Openbsd-newbies mailing list Openbsd-newbies@sfobug.theapt.org http://mailman.theapt.org/listinfo/openbsd-newbies
