[Mageia-dev] Update of backport, policy proposal

Sun Jun 26 11:43:12 CEST 2011

On Sun, Jun 26, 2011 at 10:58 AM, atilla ontas <tarakbumba at gmail.com> wrote:
+
+> Hi. I'm following this threat from the very beginning. While reading,
+> i feel i'm reading a Mandriva Cooker mailing list posts. As a
+> community distro, why Mageia developers still think like a Mandriva
+> employee? Why backports and why so many policies, like a commercial
+> enterprise distro? I mean, Mageia do not have paid developers to work
+> on packages all the time. Also Mageia do not have so many packagers
+> like Fedora or Ubuntu, So, why make so many things so hard?
+>
+> As wobo mentioned, people like latest and greatest software. I think,
+> except a few users will use unofficial 3rd party repos to get latest
+> software. While i was maintaining MVT (Mandriva Turkiye) repository,
+> our users asked for GNOME 2.32 while Mandriva have GNOME 2.30 on
+> official release.
+>
+> Personally i always hate the backports structure and policy. It
+> confuses minds. Why Mageia need a backports repo, i really do not
+> understand. Stability and bug free releases are of course a must. But
+> it needs developers dedicated to work, almost paid developers. If a
+> software do not related with core system, like vlc, it should included
+> updates repo. Let upstream fix bugs and security issues. If a packager
+> catchs a bug he should send a patch to upstream and wait for a new
+> release. Otherwise, it is not packaging it is coding, which many
+> potential packgers will avoid to contribute.
+>
+>
++1 I also see no usage of backports. I'm someone quite new to
+Mandriva/Mageia so I wouldn't know what backports are for (Ubuntu has
+nothing like this, Fedora too) so why backport?
+
+
+> Look at Debian and Arch Linux who haven't any paid developers but
+> community distros. Stable Debian releases provide software from a
+> century ago for the sake of stability. Arch provides latest software
+> including core system and occaionally have breakages. I think Mageia
+> should be between two of them. Release latest software in updates for
+> non core system and libs, keep core system stable. Remove this
+> backports thingy.
+>
+> My 2 cents...
+>
+This approach looks quite good, but the new software should be tested quite
+good so the system will not break. Sure core system won't break with this
+approach but what about the other software?
+
+
+-- 
+Mit freundlichen Grüßen
+
+Greetings
+
+Daniel Kreuter
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20110626/d5eb4c0e/attachment-0001.html>
+