Bug 262470 comment 1 added 13.1-RELEASE to the list of versions for OS in Bugzilla – thanks koobs@ From <https://forums.freebsd.org/posts/559707>: > … a freshly upgraded stable/13 system now labels itself 13.1-STABLE. In due course, please: * remove 11.4-RELEASE and 11.4-STABLE for new report purposes * add 13.1-STABLE Thanks again.
*** Bug 262747 has been marked as a duplicate of this bug. ***
@Glen Historically we've added new bugzilla version entries for each X.Y-STABLE version (as reported in uname) rather than updating existing version entry strings. We've also done this for BETAX and RCX too because: - Those are the version users *see*, where they don't need to know the underlying branch from which it came (though that's infer-able/mostly implicit for people who are familiar with the releng and dev process). This is in contrast to versions for the branch it came from (stable/13 -> 13.X-STABLE vs releng/13.X -> 13.X-RELEASE) - 'updating' version strings rather than 'creating' new version entries means all existing bug reports (for earlier X.Y-stable versions) now appear to be reported for the latest version of the field. What would be ideal is: 1) Not having to create a new version entries for each (X.Y level) for non-release development branch version strings. 2) Having each version entry (and Bugzilla version string value) refer to a fixed (not changing over time) version/branch combination. This also means never having to 'mass change' existing bug reports again to update/change their version field, and easily being able to close certain subsets of issues based on version support status (EoL) without worrying about closing reports for later and still supported versions, or closing those that are 'ambiguous'. 3) Version string values that are obvious and explicit to users for reporting, who aren't familiar with dev process and versioning schemes (uname -a string vs branch from where it comes, etc). Doing so also means *much* less manually 'correcting' Version values, or having to ask clarifying questions from reporters. Note: We have this 'moving version string' issue with CURRENT too. The bugzilla version string is CURRENT, but the displayed version string is 14.0-CURRENT , and this displayed version string changes over time. We've never had separate X.Y-CURRENT version entries, in contrast to X.Y-STABLE. It would be good to get rid of this inconsistency. In the meantime, i'm going to add a new version entry for 13.1-STABLE (continuation of existing scheme) until we can come up with a scheme that makes sense for everyone and moves us forward to a better place.
Created attachment 232833 [details] version list/counts screenshot Forgot to add screenshot of existing Version entries, and bug counts
- Added: 13.1-STABLE Version - Disabled: 13.0-STABLE Version (disabled for new bugs)
Created attachment 236217 [details] Screenshot (In reply to Kubilay Kocak from comment #2) Thanks, is it (now) reasonable to remove the first four listings – for _new report_ purposes? 11.4-RELEASE 11.4-STABLE 12.2-RELEASE 12.2-STABLE Apologies if I'm missing something.
Please add 13.2-STABLE, thanks
Committed as part of 267310.