[opensuse-project] End of lifetime patches: openSUSE-release
Hi Maintenance I'm currently checking how the end of lifetime for an openSUSE release is handled - and currently I just see "release-notes-openSUSE" as the only package which is released for this. But IMHO the following packages should see a update at the end of a product like openSUSE 13.1: 1) release-notes-opensuse 2) openSUSE-release 3) monitoring-plugins-zypper Reasons: for 1: the release notes should contain a chapter / note at the very beginning about the end of lifetime for a product. This helps customers to quickly note that they are trying to get outdated information for an outdated product. => done. for 2: openSUSE-release "owns" the file /etc/products.d/openSUSE.prod - here you can add a line like this: <endoflife>2015-01-01</endoflife> This line will trigger YaST to add a popup window telling the user that his product is no longer supported (tested with openSUSE 13.1) once he starts the update manager. for 3: the monitoring-plugins-zypper package - once installed on a client - currently also checks for outdated OS versions by parsing /etc/SuSE-release (resp. the successor). If we implement the "endoflife" Tag in the product file, this package can rely on this tag and does not need updates any longer for this. At the moment, this package allows administrators to check via remote monitoring if a system needs update or is out of lifetime. What do you think? Especially if the "openSUSE-release" package see's a patch like the suggested one in the future, this can also be used by other tools. Should I open a bug report for this? with kind regards, Lars -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
Hi, Am 30.03.2015 um 12:02 schrieb Lars Vogdt:
I'm currently checking how the end of lifetime for an openSUSE release is handled - and currently I just see "release-notes-openSUSE" as the only package which is released for this.
But IMHO the following packages should see a update at the end of a product like openSUSE 13.1:
- release-notes-opensuse
- openSUSE-release
- monitoring-plugins-zypper
Reasons: for 1: the release notes should contain a chapter / note at the very beginning about the end of lifetime for a product. This helps customers to quickly note that they are trying to get outdated information for an outdated product. => done.
for 2: openSUSE-release "owns" the file /etc/products.d/openSUSE.prod
- here you can add a line like this: <endoflife>2015-01-01</endoflife> This line will trigger YaST to add a popup window telling the user that his product is no longer supported (tested with openSUSE 13.1) once he starts the update manager.
for 3: the monitoring-plugins-zypper package - once installed on a client - currently also checks for outdated OS versions by parsing /etc/SuSE-release (resp. the successor). If we implement the "endoflife" Tag in the product file, this package can rely on this tag and does not need updates any longer for this. At the moment, this package allows administrators to check via remote monitoring if a system needs update or is out of lifetime.
What do you think? Especially if the "openSUSE-release" package see's a patch like the suggested one in the future, this can also be used by other tools.
Should I open a bug report for this?
so only partly related but now time to discuss this apparently. So I'm adding two questions here: What should be the difference in EOLing an openSUSE thing to full EOL or Evergreen EOL? Related to that, what does SUSE maintenance think about keep using the normal maintenance flow for Evergreen support (with a different group of people responsible)? Back when we started 11.4 maintenance from Evergreen we were not fully aligned but discussed the possibilities to improve the handover and process into Evergreen support. So I'd like to hear opinions about that from responsible persons managing current maintenance and security for openSUSE. Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
Le 30/03/2015 12:20, Wolfgang Rosenauer a écrit :
What should be the difference in EOLing an openSUSE thing to full EOL or Evergreen EOL?
Related to that, what does SUSE maintenance think about keep using the normal maintenance flow for Evergreen support (with a different group of people responsible)?
yes, this is pretty important, specially for 13.1 thanks Wolfgang for your involvement :-) jdd -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
On Mon, Mar 30, 2015 at 12:20:24PM +0200, Wolfgang Rosenauer wrote:
Hi,
Am 30.03.2015 um 12:02 schrieb Lars Vogdt:
I'm currently checking how the end of lifetime for an openSUSE release is handled - and currently I just see "release-notes-openSUSE" as the only package which is released for this.
But IMHO the following packages should see a update at the end of a product like openSUSE 13.1:
- release-notes-opensuse
- openSUSE-release
- monitoring-plugins-zypper
Reasons: for 1: the release notes should contain a chapter / note at the very beginning about the end of lifetime for a product. This helps customers to quickly note that they are trying to get outdated information for an outdated product. => done.
for 2: openSUSE-release "owns" the file /etc/products.d/openSUSE.prod
- here you can add a line like this: <endoflife>2015-01-01</endoflife> This line will trigger YaST to add a popup window telling the user that his product is no longer supported (tested with openSUSE 13.1) once he starts the update manager.
for 3: the monitoring-plugins-zypper package - once installed on a client - currently also checks for outdated OS versions by parsing /etc/SuSE-release (resp. the successor). If we implement the "endoflife" Tag in the product file, this package can rely on this tag and does not need updates any longer for this. At the moment, this package allows administrators to check via remote monitoring if a system needs update or is out of lifetime.
What do you think? Especially if the "openSUSE-release" package see's a patch like the suggested one in the future, this can also be used by other tools.
Should I open a bug report for this?
so only partly related but now time to discuss this apparently.
So I'm adding two questions here:
What should be the difference in EOLing an openSUSE thing to full EOL or Evergreen EOL?
Related to that, what does SUSE maintenance think about keep using the normal maintenance flow for Evergreen support (with a different group of people responsible)?
I am still open for having you and on or two others as part of the openSUSE maintenance team and responsible for 13.1 there.
Back when we started 11.4 maintenance from Evergreen we were not fully aligned but discussed the possibilities to improve the handover and process into Evergreen support. So I'd like to hear opinions about that from responsible persons managing current maintenance and security for openSUSE.
Ciao, Marcus -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
participants (4)
-
jdd -
Lars Vogdt -
Marcus Meissner -
Wolfgang Rosenauer