![](https://seccdn.libravatar.org/avatar/7799af0ed31c42f018005e32a288c00f.jpg?s=120&d=mm&r=g)
Sorry for the rant that follows, but something seems terribly wrong at the moment with the processes we as hobby packagers have to follow. I really, really, really get frustrated over the time sr takes. Now my sr for r-base, a package that made it into 11.4 and now had an upstream update, lasts for 20 days after I changed the licences string to gplv2+. Before I had one or two further tries to get the same new upstream version into 12.1., which went faster but ended in rejections. On irc I was told today "shouldn't take too much longer". Fantatstic. If this continues I see r-base out of 12.1 again. The time differences between milestones are smaller than the time it takes for a single sr?! How is this supposed to work?! Hej guys, I do this as a real community service. No money involved on my side, just my time. I do it _just_ _for_ _fun_ and the fun of a few thousand people around the world who use the binaries instead of compiling themselves. But after building R for all the suse versions since 2001 I never felt nearly as frustrated. For now the fun factor has gone. I can go to irc and get some help, all people there are nice and helpful, especially coolo and darix (thx for all the help!), but in the end I have to stare on review licencedigger for 20 days. :-( A second sr (rkward) is in this state for a week now. The next upstream release coming along in a few days. This is not what collaborating should feel. Indeed it doesn't feel like collaborating for me anymore. More like begging. How am I supposed to work with turnaround times measured in _weeks_?! Where is documentation I can read and that doesn't constantly change or at least reliably informs me over any changes? Now I try my best, but it always remains trial and error, afterwards some googling or chatting to find out what that "reject" means. Correct some minor changes, next try. I understand the need for a legal review, I understand the need for quality control. But if the queues get longer and longer some process has broken down. Thank you for listening. Detlef -------- Original-Nachricht --------
Datum: Thu, 26 May 2011 10:14:29 +0200 Von: Stephan Kulow <coolo@novell.com> An: opensuse-factory@opensuse.org Betreff: [opensuse-factory] We\'re nearing Milestone 1
Hi,
I just changed the release from Milestone 0 to Milestone 1, so one of the next builds could be released as Milestone 1. For a month we didn't have live cds because too much was broken, but last night we saw working DVDs (openqa sees tons of problems in installation, but my own tests worked) and live cds.
The GNOME one "fails to load GNOME3", but I played (and won of course :) a round of freecell solitaire as Live-CD User, so I'd say it's good enough for a Milestone 1 ;-)
It would be great if we saw some more factory testing now - and perhaps we even see a KDE networkmanager for next week, but I would release M1 without, NetworkManager-gnome fits on the KDE Live CD as temporary aid, so much I tested already.
I would take some more packages today and tomorrow and then release what has finished building on monday - and move Milestone 2 a week later.
So we have: Milestone 1: 2.6. Milestone 2. 22.6. (23rd is a public holiday in Germany) Milestone 3: 13.7.
Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org