OP
- Thread Starter
- #26
I forgot, there's also code slush and tagging for the
A few weeks ago, 26th March:
doc tree. A few weeks ago, 26th March:
doc tree.
----------------------------------------------------------------------------------------> -CURRENT
\__ 11.0-RELEASE -> p1 -> p2, etc \__12.0-RELEASE \__ 13.0-RELEASE
\__ 11.1-RELEASE -> p1 -> p2, etc \__ 12.1-RELASE \
\__ 11.2-RELEASE \__ 12.2-RELEASE \
\__ 11.3-RELEASE \ 13-STABLE
\__ 11.4-RELEASE \
\ 12-STABLE
\
11-STABLE . ' .
. . : . .
'. ______ .'
' _.-"` `"-._ '
.' '.
`'--. / \ .--'`
/ \
; ;
- -- | | -- -
| _. |
; /__`A ,_ ;
.-' \ |= |;._.}{__ / '-.
_.-""-|.' # '. ` `.-"{}<._
/ 1938 \ \ x `" _________
----/ \_.-'|--X---- < RELEASE >
-=_ | | |- X. =_ ---------
- __ |_________|_.-'|_X-X## \ ^__^
jgs `'-._|_|;:;_.-'` '::. `"- \ (oo)\_______
.:;. .:. ::. '::. (__)\ )\/\
||----w |
|| ||
/|___
///| ))
/////| )))
///////| )))
/////////| )))
///////////| ))))
/////////////| )))
//////////////| )))
////////////////|___)))
______________|________
\ STABLE /
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >
≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅≅ C T ≅≅≅≅ >
U N
R R Ereleng cow thanks to rank-amateur-cowsay
This is something I've advocated for years. In fact one can also sign up for the mailing lists and get them delivered right to your door (as it were).
. I also like the developers to make sure everything is working as expected rather than giving users a bad experience.
-RC-5 is up and running
-RELEASE: the majority are squashed in -CURRENT, which can be a pleasure to use (as can -STABLE).A solution/work around for that is encourage users to try the release candidates if they can. It may not cover all the corner cases, but it can get coverage on "normal upgrade path on a variety of hardware". Maybe not as much on "fresh install" but it's all helpful.
This of course implies that it is the serious bugs that the release team is aware of, and want to fix. All software do contain bugs.
A nice idea, however we can not expect developers to test everything. Use cases are too many, too varied.
Telling whether things work in isolation and in combination – whether a thing meets expectations – is largely (I'd say mostly) the responsibility of testers, many of whom are not developers.
Of the types of bug that might be unacceptable in-RELEASE: the majority are squashed in-CURRENT, which can be a pleasure to use (as can-STABLE).
. And I would report/ask for help if anything bad happened.
github.com
github.com
Not automatic. Probably not required every minor upgrade.
The release notes say that the bootloader was updated with many improvements and that the boot time is cut to half comparing to 13.0.
rG1811c1e957ee
reviews.freebsd.org
stable/13 and releng/13.1:
github.com
None of the bootloaders are updated automatically, you always have to do this by hand.
Well, this didn't go well, i f**ed-up my boot partition