Closed
Bug 372849
Opened 17 years ago
Closed 10 years ago
Need definitive support lifecycle information somewhere on the website
Categories
(Bugzilla :: bugzilla.org, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: justdave, Assigned: dkl)
References
Details
We need a page (or a section of a page?) somewhere on our website in an easy to find location (releases page/security page?) that explicitly lists the support lifetime of each branch. "When 3.0 releases" for the end-of-life of the 2.18 branch is fine, we just need to actually say it somewhere. This is good planning information for people getting ready to deploy in the enterprise.
Comment 1•17 years ago
|
||
I think the Release Info page would be a good place for this--we could just add another column, or add another table off to the right.
Severity: normal → enhancement
Summary: Need definitive security support information somewhere on the website → Need definitive support lifecycle information somewhere on the website
Comment 2•10 years ago
|
||
dkl, this is probably for you to write, but the gist of it as I understand it is: The current release and the two previous stable releases are supported. For the two previous releases, we only accept patches for security issues, data loss, and other critical fixes. glob mentioned that the discussion in the etherpad linked from bug 908563 is relevant here for more detail.
Flags: needinfo?(dkl)
See Also: → 908563
Assignee | ||
Comment 3•10 years ago
|
||
Thanks for bringing this to my attention Liz. I will take some time to add some text to the release info page stating our current policy (which is changing in the near future unfortunately).
Assignee: website → dkl
Status: NEW → ASSIGNED
Flags: needinfo?(dkl)
Assignee | ||
Comment 4•10 years ago
|
||
Checking in src/releases/index.html; /www/bugzilla-org/src/releases/index.html,v <-- index.html new revision: 1.22; previous revision: 1.21 done
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•