this post was submitted on 12 Feb 2024
47 points (96.1% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54462 readers
258 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Did I say CURRENT? I meant STABLE. Which is weird because shouldn't something called stable be the version you release, but release is a separate one. It's confusing.
You need to read the handbook before you start spouting judgments about the releng process.
STABLE is cut from CURRENT. RELEASE is cut from STABLE.
Yeah I got that thanks. It's a very odd way to label things. It doesn't follow industry standards which are normally: alpha, beta, release candidate, release.
Or even the debian method of: unstable, testing, stable, oldstable.
Please quote me the relevant "industry standards." It is all perspective, and FreeBSD releng certainly does not cater to what some rando online might think is an intuitive way to name release trains. This has been done this way for 30 years.