Stuart Henderson(s...@spacehopper.org) on 2019.09.02 17:58:55 -0000: > On 2019-09-02, Marcus MERIGHI <mcmer-open...@tor.at> wrote: > > Hello Joerg, > > > > just passing on my user experience...: > > > > streckf...@dfn-cert.de (Joerg Streckfuss), 2019.09.02 (Mon) 10:15 (CEST): > >> Furthermore I'm not sure which snapshot should I run. Almost every day > >> there will be a fresh one. > > > > you seem to be watching closely, therefore you will notice a time when > > there are no new daily snapshots for a couple of days. this is usually > > when the next release is tagged/built. additionally you can monitor > > ports@ to see when the ports tree gets locked for the next release. > > Ports lock is no indication of the state of base. The locks are independent. > > >> Perhaps is there a moment/date where a > >> freeze of the code base will be done which reflects the 6.6 release?
While a bit dated, this presentation explains what we do: https://www.openbsd.org/papers/asiabsdcon2009-release_engineering/ > Use sysupgrade -n and monitor the OS version number ("what > /home/_sysupgrade/bsd"). If you see 6.6-current it is post-release and > you should not install it ("rm /bsd.upgrade"), you can then wait until > actual release day and update to be sure you're running on the proper > release binaries.
