[opensuse-factory] Nginx Mainline (1.9.x)
I'm curious, why does Tumbleweed have Nginx "stable" (1.8.x) and not "mainline" (1.9.x)?
Note that stable does not mean more reliable or more bug-free. In fact, the mainline is generally regarded as more reliable because we port all bug fixes to it, and not just critical fixes as for the stable branch.
And
We recommend that in general you deploy the NGINX mainline branch at all times. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, On Sun, Jan 31, 2016 at 1:17 PM, Ibrahim M. Ghazal <imgx64@gmail.com> wrote:
I'm curious, why does Tumbleweed have Nginx "stable" (1.8.x) and not "mainline" (1.9.x)?
I maintained nginx for a while. I just followed the choice of the previous maintainers. so let's not discuss the 'why', just take it as 'facts'. Let's talk about 'how'. How to update TW's nginx while keep Leap's at stable? The update itself is easy. but I can't promise that next time when we pick Leap packages. the mainline version in TW contains no incomplete features (at least that's what upstream did for 1.6 and 1.7). anyway in my view, odd number always means experimental. And I don't want users to explicitly install "nginx-mainline", "nginx-stable", "nginx-1.8", "nginx-1.9"...that's not friendly. A dummy Provides might help. but I have to apply maintainership in server:http to rename packages. Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, Jan 31, 2016 at 11:07 AM, Marguerite Su <i@marguerite.su> wrote:
Hi,
On Sun, Jan 31, 2016 at 1:17 PM, Ibrahim M. Ghazal <imgx64@gmail.com> wrote:
I'm curious, why does Tumbleweed have Nginx "stable" (1.8.x) and not "mainline" (1.9.x)?
I maintained nginx for a while. I just followed the choice of the previous maintainers. so let's not discuss the 'why', just take it as 'facts'.
Let's talk about 'how'.
How to update TW's nginx while keep Leap's at stable?
The update itself is easy. but I can't promise that next time when we pick Leap packages. the mainline version in TW contains no incomplete features (at least that's what upstream did for 1.6 and 1.7). anyway in my view, odd number always means experimental. And I don't want users to explicitly install "nginx-mainline", "nginx-stable", "nginx-1.8", "nginx-1.9"...that's not friendly.
A dummy Provides might help. but I have to apply maintainership in server:http to rename packages.
I just did the change.. request id 356966. let's provide just *one* nginx based on upstream recommendations. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, Jan 31, 2016 at 10:25 PM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
The update itself is easy. but I can't promise that next time when we pick Leap packages. the mainline version in TW contains no incomplete features (at least that's what upstream did for 1.6 and 1.7). anyway in my view, odd number always means experimental. And I don't want users to explicitly install "nginx-mainline", "nginx-stable", "nginx-1.8", "nginx-1.9"...that's not friendly.
A dummy Provides might help. but I have to apply maintainership in server:http to rename packages.
I just did the change.. request id 356966. let's provide just *one* nginx based on upstream recommendations.
That's hardly called "discussion". And my concern wasn't answered at all. There must be a reason upstream provides two branches. If they're so confident then stable didn't exist at all. If I am the upstream, I'll encourage users to stick to the latest version too. At least I don't want my own forum server open to flaws caused by incomplete/experimental features. Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 2016-01-31 17:59, Marguerite Su wrote:
I just did the change.. request id 356966. let's provide just *one* nginx based on upstream recommendations.
There must be a reason upstream provides two branches. If they're so confident then stable didn't exist at all.
Well if you like, call stable "backports", and mainline "stable" instead. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Feb 1, 2016 at 1:04 AM, Jan Engelhardt <jengelh@inai.de> wrote:
Well if you like, call stable "backports", and mainline "stable" instead.
If so, 'backports' is a must. 1. see this: https://build.opensuse.org/project/show/openSUSE:Backports:SLE-12 packages lay there need to be in factory first. 2. think about maintenance for released products. http://nginx.org/en/CHANGES changelog for 1.9.8: * Bugfix: a segmentation fault might occur in a worker process when using LibreSSL; the bug had appeared in 1.9.6. what if the nginx in Leap is exactly 1.9.6? we create an updatestack to update it to 1.9.8? then 1.9.10 to fix 3 more security bugs? the path is not smooth. I am not against the inclusion of mainline version. I just think we don't need to take the cost of dropping stable version. Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Marguerite Su wrote:
I just think we don't need to take the cost of dropping stable version.
There are so many different definitions of "stable". => IMO the term "stable" is highly overrated and often misleading. The package maintainer should decide upon this based on careful observation of upstream project. (Personally I prefer to go with mainline version.) Ciao, Michael.
Marguerite Su wrote:
On Sun, Jan 31, 2016 at 1:17 PM, Ibrahim M. Ghazal <imgx64@gmail.com> wrote:
I'm curious, why does Tumbleweed have Nginx "stable" (1.8.x) and not "mainline" (1.9.x)?
I maintained nginx for a while. I just followed the choice of the previous maintainers. so let's not discuss the 'why', just take it as 'facts'.
Let's talk about 'how'.
How to update TW's nginx while keep Leap's at stable?
The update itself is easy. but I can't promise that next time when we pick Leap packages. the mainline version in TW contains no incomplete
There are still a few months left until we have to branch for the next Leap :-) While the default modus operandi is to pick packages from Factory there is still also the option to go for a different branch if needed. IOW as package maintainer you should feel free to put whatever version in TW that you think fits best for the target audience there. When thinking about Leap the different target audience might justify a different version of course. If in case of nginx having packages for two branches in Factory makes sense then that's fine too IMO as long as there's at least one package actually called 'nginx'. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday 01 of February 2016 11:41:18 Ludwig Nussel wrote:
There are still a few months left until we have to branch for the next Leap :-) While the default modus operandi is to pick packages from Factory there is still also the option to go for a different branch if needed.
Is this really supposed to be default? My understanding always was that Leap should be treated as long-term stable, i.e. even for packages picked from Factory for 42.1, keeping the 42.1 version should be preferred for 42.2 and only if there is a strong reason, package would be upgraded to current Factory. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Cristian Rodríguez -
Ibrahim M. Ghazal -
Jan Engelhardt -
Ludwig Nussel -
Marguerite Su -
Michael Ströder -
Michal Kubecek