From Mageia wiki
Revision as of 11:37, 2 August 2021 by Marja (talk | contribs) (Category Bug Squad is being moved to Category Bugsquad)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


End Of Life for a Mageia release

  • Announce what we're going to do to bugsquad and dev mailing lists.
There are currently 421 open bug reports for Mageia 4, which has reached its 
end of life two days ago.

Bug Squad is going to follow the steps at 
https://wiki.mageia.org/en/Maintenance_of_bug_reports

Roughly: first clean up what's easy to clean up (done already), then send 
automated comments to all Mageia 4 open bug reports (see model in link above), 
giving a one month delay to change the version to a later one if the bug 
report is still valid. After one month, all remaining Mageia 4 bug reports 
will be closed as RESOLVED OLD.

Where do *you* intervene? By making sure that the bugs you reported or that 
were assigned to you, or that you have interest in are not closed erroneously 
if they are still valid. So please take a few minutes to go through your 
Mageia 4 bugs, or simply don't ignore the bugzilla notifications that are about 
to reach your inbox.

Here are links to save you some time:
* Mageia 4 bugs by assignee: https://lstu.fr/mga4-bugs-by-assignee-name
* Mageia 4 bugs by reporter: https://lstu.fr/mga4-bugs-by-reporter

Best regards,

Samuel Verschelde, on behalf of Bug Squad.
  • Look for RPM package requests, make sure they are actually RPM package requests, and set them to cauldron.
  • Look for backport requests, make sure they are actually backport requests, and close them as old explaining that Mageia n has reached EOL.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no 
longer maintained, which means that it will not receive any further updates. 
As a result we are closing this bug report. 

If you would like to help with updates and backports in the future, don't 
hesitate to join the packager team via our mentoring program [1], our QA 
Team (who tests the updates and backport candidates and always welcomes 
help) [2] or join the teams that fit you most [3].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] https://wiki.mageia.org/en/QA_Team
[3] http://www.mageia.org/contribute/
  • Look for enhancement requests against the "RPM Packages" component) and set those that are still valid to cauldron.
  • Look for installer or release bugs (should be set to cauldron already but we might have missed some). Check they are really installer or release bugs and set them to cauldron with NEEDINFO and asking if still valid.
Installer and Release bugs version should always be set to cauldron, because 
once the ISOs for a stable version have been created, they cannot be changed.

This bug was filed for Mageia 4. Was this bug still valid for Mageia 5?

(If so, please do _not_ set the version to "5". Only asking because if it was 
still valid for Mageia 5, that then we'll know we'll have to pay attention to 
this issue when testing the next version's alpha's and later).

Please close this bug report as FIXED if the problem was solved in Mageia 5.
  • Mass message for Mageia n bugs announcing that we are going to close the bugs still set to Mageia n, so that people can set them to cauldron or Mageia n+1. Give one month of delay.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 4's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia. If it's valid in 
several versions, select the highest and add MGAxTOO in whiteboard for each 
other valid release. 
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
  • Manually check critical bugs and maybe major bugs for important bug reports we don't want to lose if reporters or packagers don't reply within one month: set to Mageia n+1 / cauldron.
  • One month later, mass close as RESOLVED OLD with EOL message.
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on
2015-09-19. It is is no longer maintained, which means that it will not receive
any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see
it and didn't already do so: please upgrade to Mageia 5 (or, if you read this
much later than this is written: make sure you run a currently maintained
Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are
encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to
"REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know
it's valid in several versions, select the highest and add MGAxTOO in
whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced
bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same
cause, then please file a new bug report and mention this one in it (please
include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/