Marcus Meissner wrote: > The internal policy however sets it to backport if possible, to avoid > any problems like the above (or others still unknown).
this is a very important question, as the burden of backporting is high (on some products). could it be possible to write down a page (for example on opensuse wiki) to make this clear, for users but also for programmers. For this I'm ready to help For example: "A server must be able to run several years without major change. So it's mandatory to have stable version of any product patched for security for at least 5 years (don't forget this impact mostly comercial products). To achieve this is already done by most major comercial distributions. For a product to be included in such a distribution, making such patches available is a great plus. (then example of what to do and what to avoid - I'm sure you have plenty :-)" I know this is a reason for having paid clients, but I beg that if the original developpers makes it easier, they product have a great chance to be included in major distributions and themselves could provide this for a fee, still cheaper than making it from scratch :-) is this worth continuing? thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
