January 2009 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] openSUSE 11.2 schedule
by Michael Loeffler 15 Mar '09

15 Mar '09

Moin, openSUSE 11.1 is almost out of the door and we (coolo, aj, zonker and myself) had some discussion about the release date for openSUSE 11.2. First we talked about July '09 release to come close to an 8 months release cycle. But KDE 4.3 is scheduled for release on June 30th and probably an OpenOffice.org release will be out end of June as well - both wouldn't make it into a July openSUSE 11.2. Therfor we're now thinking about a September release. Beside of getting the most current OpenOffice and KDE in thhis would even have one additional upside. It probably would be just in front of our openSUSE conference. So the conference could be used for very a focused openSUSE 11.3 planning. But it has its downside as well. Finalization of the release would happen during the summer holiday season. To address this we we added one Beta to stretch the development time a bit. Here's what we're talking about: 2009-02-05 openSUSE 11.2 Alpha 0 2009-03-05 openSUSE 11.2 Alpha 1 2009-04-02 openSUSE 11.2 Alpha 2 2009-04-30 openSUSE 11.2 Alpha 3 2009-05-28 openSUSE 11.2 Alpha 4 2009-06-25 openSUSE 11.2 Beta 1 2009-07-09 openSUSE 11.2 Beta 2 2009-07-24 openSUSE 11.2 Beta 3 2009-08-06 openSUSE 11.2 Beta 4 2009-08-20 openSUSE 11.2 RC1 2009-09-03 openSUSE 11.2 GM 2009-09-10 openSUSE 11.2 Public Release Events to consider March 3-8 CeBIT March 8-13 BrainShare June 24-27 LinuxTag June 3-11 Akademy/Guadec Sept openSUSE conference (mid of sept) Sept Plumbers conference (around Sept 20-25) Let us know what you're thinking about this. Best M -- Michael Löffler, Product Management SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

33 115

[opensuse-project] openSUSE GNOME meeting (2009/1/29)
by Rodrigo Moya 01 Feb '09

01 Feb '09

11.2 features discussion • New organization decided: ∘ http://en.opensuse.org/GNOME/Ideas will be a place for putting wild ideas, and when well thought and documented, will be moved to openFATE (or just Bugzilla?) ∘ 11.1 and 11.2 pages have been merged into http://en.opensuse.org/GNOME/Ideas please review and remove already implemented features Packaging day • Next Thursday, to package GNOME 2.25.* Packaging • eel integrated in nautilus 2.25, so remove • farsight to be removed (farsight2 replaces it) • glade-2 (move to contrib?) -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

2 2

[opensuse-project] Accessing packages sources without any account
by Vincent Untz 29 Jan '09

29 Jan '09

Hi, I know it was discussed at some point, but is there some progress on publishing the sources of the packages, browsable in an easy way, outside of the build service? (so that people can access them, especially the patches without having an account) If no, is there anyway I can help with that? It's really important for upstream to be able to browse the patches, to see what's going on. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

2 4

[opensuse-project] openSUSE GNOME meeting (2009/1/22)
by Rodrigo Moya 22 Jan '09

22 Jan '09

11.2 planning ∘ http://en.opensuse.org/GNOME/Ideas/11.2 ∘ Use this page to add any ideas, and when formed a little bit, move to openFATE ∘ AI: everyone review 11.1 ideas page (http://en.opensuse.org/GNOME/Ideas/11.1) and move unfinished tasks to 11.2 page Policy bugs ∘ Plan is to quickly discuss a few bugs that would take hours to discuss on the mailing list ∘ https://bugzilla.novell.com/show_bug.cgi?id=462077 -> remove patch ∘ https://bugzilla.novell.com/show_bug.cgi?id=460963 -> WONTFIX, PolicyKit-based solutions will solve this ∘ https://bugzilla.novell.com/show_bug.cgi?id=407286 -> use openSUSE icon for both main menu and menu bar applet ∘ https://bugzilla.novell.com/show_bug.cgi?id=329630 -> provide our own branding for the menu, to get no submenus ∘ For bugs to be discussed in future meetings, mail vuntz(a)novell.com with the bug # Discuss repo names ∘ GNOME:Stable and G:Unstable created ∘ G:S:2.24 will contain GNOME 2.24.x from openSUSE:11.1, and G:S will point to that, then to G:S:2.26 once released, and so on ∘ G:U will be created from G:Factory as soon as the GNOME:Factory/GNOME:Factory:Next merge is done ∘ Stable release updates (updates to CD/DVD versions) available right now in several separated repos, would be great to have 1 meta-repo that links to the latest for a released distro (Contrib?) -> move discussion to opensuse-project ML ∘ AI: captain_magnus to populate G:S:2.24 Community building ∘ GNOME release days as packaging days (next is Feb 4th) ∘ Bug triage (P5 bugs prioritization) (http://tinyurl.com/cxknu3) can be done by anyone, specially with JP's bug triaging guide FOSDEM ∘ Send a photo of yourself to vuntz(a)novell.com for a talk about the opensuse-GNOME team Next meeting (Jan 29th) ∘ 11.2 features discussion ∘ Having a packaging day soon -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

[opensuse-project] Error in 64 bit (x86-64) version of x11-video-fglrxG01-8.561-1.1 for openSuSE 11.1
by Joop Boonen 22 Jan '09

22 Jan '09

All, This might help people who want/need to use the closed source driver in openSuSE 11.1 64. I see the following error in /var/log/Xorg.0.log <quote> drmOpenByBusid: drmGetBusid reports PCI:3:0:0 (EE) AIGLX error: dlopen of /usr/lib/dri/fglrx_dri.so failed (/usr/lib/dri/fglrx _dri.so: wrong ELF class: ELFCLASS32) (EE) AIGLX: reverting to software rendering (II) fglrx(0): Enable the clock gating! </quote> The problem is that it tries to use the 32 libs library in stead of the 64 bits. I solved the problem by: mv /usr/lib/dri/fglrx_dri.so /usr/lib/dri/fglrx_dri.so.org ln -s /usr/lib64/dri/fglrx_dri.so /usr/lib/dri/fglrx_dri.so Regards, Joop. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 1

[opensuse-project] A couple mailing list issues
by Eric Springer 21 Jan '09

21 Jan '09

I'm not sure if I'm missing something, but how come emails sent don't have the "reply-to: <ml>@opensuse.org" header? OS is the only mailing list I've used without it -- and I'm sure I can't be the only one who accidentally sends off replies to person rather than list. And while on the topic of mailing lists, with the opensuse-features list for openfate -- can we stop firing off emails everytime someone adds themselves to the "interested: " part? I can't imagine anyone actually wants to be notified in this event. I want to read comments and new feature ideas, but checking new messages to only find it's a "+1 person interested" 99% of the time is frustrating. Regards, Eric. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

7 7

[opensuse-project] Minutes from Board meeting on Dec 10
by Michael Loeffler 20 Jan '09

20 Jan '09

Happy new year to all of you. And sorry for the delay of the meeting minutes. Best Michael openSUSE Board Meeting Minutes Dec 10th, 8pm - 10:20pm CET Participants: Federico Mena Quintero (federico1) Hendrik Vogelsang (henne) Michael Löffler (michl) Bryen Yunashko (suseROCKs) Pascal Bleser (yaloki) Joe Brockmeier (zonker), for the first hour *Advisory Board (zonker) Proposal get reviewd by Novell's lawyers and then up to the project mailing list *Awarding good people We should award outstanding contributors and good poeple Everybody agreed, just with what and how to find all valuable contributors? *openSUSE conference (zonker) probably September '09 in the Nuremberg area Zonker clarified that all openSUSE talks will be public. But there migth be a few Novell internal talks (eg. company processes) *FOSDEM - We should have a talk with the Board, kind of or meet and great (in our dev room) - there is probably an open source project track where openSUSE would fit to participate -> best to contact mlasars on that (AI: yaloki) *Creation of thoughts page Done in the Board wiki *Board blog Some feel the board should have its own blog or a seperate channel to communicate. As spotlight.opensuse.org already exists its kind of a simple task to enlarge this to the openSUSE Board. An zonker is not lonely anmore. Everybody agreed to do so. AI: henne to make this happen *Board's public presence To increase Board's presence in the community and visibility in the public we agreed on having a public Board Meeting in January together with the project meeting Board articles Rotate each board member to write an article on a topic the board agrees to speak to the public on. Bryen writes up an review 2008, the rest will review and should be sent out soon Old AIs *AI henne, post meeting logs to board wiki Henne had an issue and didn't do it but will mail them around * michl to write thank you letter letter written but not sent out, waiting for the flash lights * Members approval 46 queued up again, should be down to 0 latest end of the month We'll meet on Dec 17th to go through them *Contrib repo http://en.opensuse.org/Talk:Contrib This turned out in a long, constructive discussion. Meanwhile already announced, http://news.opensuse.org/2008/12/17/get-going/ Next meeting Jan 14th - a public one with the project meeting -- Michael Löffler, Product Management SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

11 20

[opensuse-project] Creating opensuse-performance list
by Hans Petter Jansson 20 Jan '09

20 Jan '09

Hi, I'd like for a new topic mailing list, "opensuse-performance", to be created. We'll use it to coordinate our work towards making openSUSE boot faster. See http://en.opensuse.org/Boottime/Boot_time for more info. -- Hans Petter -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

4 6

Ad: [opensuse-project] Novell´s plans for the comming releases
by birger.kollstrand＠googlemail.com 19 Jan '09

19 Jan '09

2009/1/19, Lars Marowsky-Bree <lmb(a)suse.de>: > On 2009-01-16T16:22:25, Birger Kollstrand <birger.kollstrand(a)googlemail.com> > wrote: > >> There is an overwhelming desire to create different implementations of >> the same problem. > > This is an apparently necessary step before convergence can happen; the > community tends to have the resources to explore many (subtly) different > technical/social/organizational directions at once before converging. > That is actually one of the strengths. Yes I agree, but I also belive that a structured unit like a company can help out in the process of actually getting a convergence. Either by supporting directly with development resources or by trying to lead the community by asking different teams to work together. I do not believe many projects would take it badly if a leading person from openSUSE-Novell asked if there where any common ground that wold gain all. Or simply by discussing with community projects that this and that functionality would be a benefit for openSUSE? cu -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

[opensuse-project] Novell´s plans for the comming releases
by Birger Kollstrand 19 Jan '09

19 Jan '09

Hi, I tried my luck on the factory list with asking about the plans, goals and dreams :-) for the comming releases. Seen from Novell´s point of view. Not much came of that unfortunately. What I´m looking for is much more than which upgrade upgraded desktop environment is going in. What use cases does Novell want to reach? What should the user be able to do with SUSE? - Portability/Laptop/Nettbooks and so on - Connectivity of devices - Support for syncronizing devices - Home server setup, mediaserver, DNLA, UpnP, file , print and so on. All the nice stuff that needs to be made with KDE this or that and Gnome what ever. It would be really good if Novell can take a user stand and not a developer stand in the comming project. And with user , I´m thinking of the everyday user that does not even know what Linux is. The most important thing is not which desktop environment version is available, but what an everyday user can do with it. So pleeeeease somebody, enlighten me :-) Is there any strategy available? Kind regards, Birger

16 31

Re: [opensuse-project] Novell?s plans for the comming releases
by Cristian Rodríguez 16 Jan '09

16 Jan '09

Birger Kollstrand escribió: > Patents on SW is not valid in Europe. I know, however openSUSE, is produced by legal means, by an US based company. > Patens on SW/Processes in the US > is also a movig target with the Supreeme court reexamening the paent > couts. In the meanwhile the situation improves, we have to live with them (I wouldnt hold my breath though) > Yes, but this discussion is not where I want to raise them. I would > like to see if there was som strategy from SUSE´s main contributor. As Henne told you, there isn't a single strategy. -- "We have art in order not to die of the truth" - Friedrich Nietzsche Cristian Rodríguez R. Software Developer Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/

2 1

[opensuse-project] Re: [opensuse-announce] openSUSE Project Opens Feature Tracking with openFATE
by Rob OpenSuSE 16 Jan '09

16 Jan '09

2009/1/16 Joe 'Zonker' Brockmeier <jzb(a)zonker.net>: > openSUSE Project Opens Feature Tracking with openFATE > > The openSUSE Project is pleased to announce that feature tracking and requests > are now available to the larger openSUSE Community. The openSUSE feature > tracking system, openFATE[1], is now live and accessible to anyone with an > openSUSE account. This is nice! It was frustrating when Bug Enhancement request was resolved by an inacessible fate #. The comments actually seem to work to. Great improvment, thank you. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

[opensuse-project] openSUSE GNOME meeting (2009/1/15)
by Rodrigo Moya 15 Jan '09

15 Jan '09

Back to weekly meetings 11.2 plan: • AI: add 11.1 ideas that were not finished (http://en.opensuse.org/index.php?title=GNOME/Ideas/11.2) • Focus on 3 things: ∘ Community building (building new tools, mails, etc) ∘ Integration (Remove more little niggles in openSUSE with how GNOME and other pieces work) ∘ Features: ‣ 3-5 big issues for upstream this year to be delivered back to openSUSE via GNOME releases 11.2 ideas: • DeviceKit integration to replace HAL • Package review (excessive build requires, splitting) • further PulseAudio adoption • sound themes • P2P integration (bittorrent) • podcast creation platform • remove bonobo from libslab • scheduled jobs tool • flickr slideshow screensaver • time machine • new desktop default setups • PolicyKit deeper integration (RunAsRoot in .desktop/AdminKit) • Color management on the desktop • ship a selection of screensavers • fix the applications menu ∘ the structure (too complex, too many submenus, etc.) ∘ the desktop files appearing in many places ∘ hiding desktop files that we don't care about • fix the GenericName vs Name vs Comment stuff in desktop files • move packages to Contrib • HIG improvements in upstream and opensuse-specific things • Find 10 common items people do on 1st install and make those work really well • Boot/desktop loading performance improvement • More marketing: ∘ tips&tricks on linux, non-opensuse specific, things (screencast howto, hardware usage (TV cards, webcams, GPS, etc), etc, etc) to get more people to try openSUSE ∘ Daily ISO/live CDs? ∘ Prebuilt VM images? ∘ More blogging • Upstream: ∘ Working-out-of-the-box jhbuild ∘ build brigade/build service integration ∘ more housekeeping in g-s-d ∘ move gconf schemas to /usr/share (schemas are data, so will remove lots of rpmlint warnings) Next meeting (Thu 22nd Jan) • Prepare package days/bug squashes • Discuss features -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

[opensuse-project] new security checks of the installation media for 11.1
by David Bolt 13 Jan '09

13 Jan '09

I'm the present maintainer of makeSUSEdvd[0] and am trying to figure out what's changed between the release of 11.1a2 and 11.1 that results in broken ISOs. Previously, makeSUSEdvd was able to take the contents of any of the release DVDs, allow extra packages/patterns to be added and, after the contents file was updated and signed, would create a bootable ISO that allowed installation without complaints. However, there was a change somewhere between alpha 2 and gold master, and this is no longer the case. Now, although the contents file on the DVD is signed, the installation routines check the contents file on the new image, claim it isn't signed and so aborts the installation. So, if anyone has any helpful pointers as to what needs to be done to satisfy the new 11.1 security checks, they would be most helpful. [0] built packages are here: <URL:http://download.opensuse.org/repositories/home:/davjam79/openSUSE_11.1/…> <URL:http://download.opensuse.org/repositories/home:/davjam79/openSUSE_11.0/…> <URL:http://download.opensuse.org/repositories/home:/davjam79/openSUSE_10.3/…> Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s | openSUSE 10.3 32b | openSUSE 11.0 32b | openSUSE 10.2 64b | openSUSE 10.3 64b | openSUSE 11.0 64b | openSUSE 11.1 64b TOS 4.02 | openSUSE 10.3 PPC | RISC OS 3.6 | RISC OS 3.11 -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

2 3

[opensuse-project] Boxed editions slipping on release dates (3 weeks in some cases)
by Eric Springer 09 Jan '09

09 Jan '09

On Thu, Jan 8, 2009 at 2:19 AM, Dirk Müller <dmueller(a)suse.de> wrote: > In one of my previous mails I and several other people have proposed to split > openSUSE into a "common core" base that contains the newest hardware > enablement and base system (compiler, kernel etc), and the addons, like the > desktops. both can be released independently and the common core can be > released in a staged fashion, allowing people to use a stable base system or > the most recent base system, one of which might be ideal for their hardware. > > It was dismissed as "very hard to promote a new openSUSE release which only > changes the base system", but I have the counter argumetn: it is a lot easier > to promote a new desktop on a stable openSUSE base system (that was released > and fixed already). > > Greetings, > Dirk For what it's worth, I think it's a fantastic idea. It'd be short sighted to dismiss this for marketing reasons, when (imo) we'd end up with a clearly superior product. I know it's not exactly the marketing being referred to, but I recently recommended and offered to install openSUSE on a colleague's laptop. After using it for a little, I was forced to eat my words -- ask around for an XP cd -- and put it back on. It was simply far too buggy/crashy/unstable, and I can't very well say "Oh, just wait a couple weeks and the updates should/might sort it out". So we can have something that we can market (Shiny new release!) or something that is actually marketable. =) Besides, if we used this to be the first major distro to release for new versions of gnome, kde and xfce that in itself would be more publicity than we currently receive. -- Eric Springer (Erikina) -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

[opensuse-project] openSUSE GNOME meeting (2009/1/8)
by Rodrigo Moya 08 Jan '09

08 Jan '09

2008 accomplishments + We now have a community around GNOME that didn't exist in 2007, Novell people not from the desktop team +, more importantly, external people + 2 GNOME-ish people on the openSUSE board + Improved collaboration with upstream, but still lots of work to do: intl clock, multihead + Bug triaging, package days were a good thing, but lack the regularity to engage more community + Build service usage and osc gnome plugins were awesome + FOSDEM was a big success 2009 plans + Testing and bug filing is working ok, but need to get community people more involved - users.opensuse.org could be a place for external people to meet up in areas of interest - Novell infrastructure (iChain, closed bugzilla) sometimes doesn't help, maybe openSUSE could be decoupled from Novell? - Market openSUSE as a great platform for software development? - Mentor university students (outside of Google SoC) - Internal people are online working hours, but not always on weekends or evenings, which is when most external people come - Will come back to weekly meetings + Should we innovate more? On what? - Automating stuff, like in osc gnome, helps a lot (weekly meetings) + Leadership - Some activities (bug days, meetings, etc) are not done by a dedicated "team", so sometimes they don't get organized + Upstream - Package jhbuild with all needed dependencies - Participate more in new UI designs (3.0, drive usability tests, experiment with new UIs, etc) Next meeting + Everyone brings a goal and ways to to achieve it for discussion + Discuss having regular bug days, patch upstreaming, etc days + Discuss more ways of getting people involved + Discuss working on more new upstream features + Discuss 11.2 features (http://en.opensuse.org/GNOME/Ideas/11.1) -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

[opensuse-project] Development release: How to make it better,
by Eric Springer 08 Jan '09

08 Jan '09

On Sat, Jan 3, 2009 at 3:00 AM, Cristian Rodríguez <crrodriguez(a)suse.de> wrote: > nordi escribió: > Just replace the binaries with >> >> xmessage "OpenOffice is currently broken. We're working on it." > > What is happening in this thread ? suggestions are getting more and more > ridiculous everyday.. how you will ever figure that openOffice is broken > if you dont include the binaries ? Oh please. The meaning was extremely clear and obvious. It was _well known_ that the package X (in this case, openoffice) was broken, meaning every person who used it came across had the same issues. Wasn't able to use it. Had to search for search for a bug report, see that it's been confirmed a dozen times. Nobody is saying that things need to be perfect, but what we are saying is to not waste our time with things already known. These packages should lie in some sort repository intended for developers of the package until you believe that it actually requires _testing_. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

5 14

Re: [opensuse-project] Boxed editions slipping on release dates (3 weeks in some cases)
by Eric Springer 08 Jan '09

08 Jan '09

On Wed, Jan 7, 2009 at 12:33 AM, jdd <jdd(a)dodin.org> wrote: > > knowing what kde or gnome version we have is plain ridiculous if we > can't have a working computer... > Absolutely -- it's seriously a major issue for openSUSE. I haven't encountered anything nearly as bad with other distros (or even bsd for that matter). Anyone want to put forward a concrete plan/proposal that we can hopefully discuss/vote/implement? -- Eric Springer (Erikina) -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

5 4

[opensuse-project] release as an add-on?
by James Tremblay aka SLEducator 07 Jan '09

07 Jan '09

Hey guys, What are the obstacles to the idea of marketing a full release at X.0 and then releasing\marketing "patch CD updates" instead of full community sub-releases(still a fully installable dvd if desired, specifically for the x.3)? We would definitely be doing something different than the rest of the distro's (good PR) and if the patch cd could accomplish the same kinds of updates that we offer in our current sub-releases with less work and more stability for the end user, it would be a win\win\win: openSUSE team gets to show off YaST and Build Service, marketing gets to differentiate openSUSE, the end users need for a fresh install could be reduced. Extra possible "win" - "long term support "could more easily be moved to x.3 releases citing the x.1\x.2 as support levels for x.0. with the bonus side effect of reducing update channel bandwidth. i.e. security only on x.0 then nothing unless x.1 is applied (This is nothing new to major software vendors, can't tell you how many times I've heard "we only support that product at x.1.2.3, please upgrade.") then x.3s could also be easily translated to SLEs. It seems a waste that SuSE built YaST with all this functionality to not let openSUSE benefit from it's heritage. Any way , openSUSE is yet again filled with many exciting things while still delivering the hope of many more. I'm happy to play with 11.1, while drooling for 11.2 , just as I was the day after 11.0 released. Thanks for all the fun! JT -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

11 20

[opensuse-project] Boxed editions slipping on release dates (3 weeks in some cases)
by Kevin Dupuy 07 Jan '09

07 Jan '09

Starting last night I've begun to see people on both the support mailinglist and the forums complain they've received an email from the Novell Shop telling them their pre-ordered boxed editions won't ship until January 5th. Does anyone know what's going on? I've seen this happen with previous versions of openSUSE, but I thought there was something done to correct the problem. It seems to me people paying $60USD then not receiving their product until 3 weeks after the free download will think twice about buying the box again. -- Kevin "Yeaux" Dupuy - openSUSE Member Public Mail: <kevin.dupuy(a)opensuse.org> Merry Christmas & Happy Holidays from the Yeaux! -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

31 155

[opensuse-project] Release Cycle Changes
by James Tremblay aka SLEducator 06 Jan '09

06 Jan '09

Sorry For the double post, I wanted to start a new thread. What if? The system was, "11 boxed" (SLE11rc1) and openSUSE 12.0 where the same ISO (with branding and repo changes), I'm suggesting three layers of release; dev, tester , "Joe Plumber"\SLE. For all Novell Linux "Nightly" repo would be for internal development - aka unstable "Factory" could be the community "devs" repo and provide 12.0.X, 12.1.X, etc. released quarterly and the only place to include new kernel and desktop changes but never in X.3.X A "tester", could install with the 12 ISO which had "factory-update" as its repo, then 12.1 would be an update\add-on\upgrade, the same for 12.2, etc. preferably still on 9 month cycle and released as a delta iso (smaller bandwidth) Using a "Delta" or cumulative type release format could take most of the work out of bug-fixing the "boxed" release. Joe, doesn't have to think much , he goes straight for "11 boxed" and can stay there until "13 boxed"(or "12 boxed" if he really wants an upgrade), otherwise grab 12.x iso and work with us. I think we can all agree that the initial install is what the community(aka "joe" and some testers)most dislike, I am told this is mostly do to kernel and major desktop changes. By scheduling these things early in our release development and with the "boxed" being built from a known kernel and desktop, this issue should disappear. Yes? When applications fail during release it's usually because there wasn't enough testing. Yes? I believe it's causing to many issues to add or wait to add a new kernel or desktop release just because it happens to be close to our next release. These need to done in the early (i.e.12.0.x-12.1.x)releases. The goal for boxed is for "Joe" who simply wants to replace Windows with ease.( a growing group of people according to Apples sales numbers). He doesn't care about a stale Gnome,KDE or openOffice if it works. He does care that if his HD dies he can reinstall everything including peripheral applications provided for, but not included in, the distro. By Defining a "dev" level, we invite people who literally develop openSUSE and components specific to openSUSE to contribute to sub-releases, which lets them test small changes on a faster pace. By defining a layer as "tester", we invite those who want to be part of the development and expect issues. Sysadmins and Application Engineers looking to make a specific application work better. By defining a "Boxed" version, we invite more of the general public to use openSUSE with confidence. By making these definitions clear, we take away the reviewers ability to complain about our missteps if he is reviewing "tester" or "dev" releases. Changing the release cycle and the release itself to a more reliable and consistent product would look like this: 12.0 -security fixes until 12.1 there is no need to support the testing layer any longer than the next release. 12.0.X - no more than 3 months and no less then 1.5 months from 12.0 - Repo only - no patches provided. (Quarterly releases) 12.1 - no more then 9 months from 12.0 - Repo and "Add-On"\Patch CD\Delta ISO - same support as 12.0 12.2 - "" 18 months"" 12.3 - ""24 months"" 12 "boxed" \ openSUSE 13- no more then 27 months from 12.0 - ISO and retail box - subscription updates and installation support for no less than 24 months. Realistically not a big change, but the change to a structured cumulative development cycle with early kernel and desktop updates as well as 3 months dedicated to "boxing" would go a long way politically. -- James Tremblay openSIS Product Specialist http://www.os4ed.com CNE 3,4,5 MCSE w2k CLE in training Registered Linux user #440182 http://en.opensuse.org/education -- James Tremblay openSIS Product Specialist http://www.os4ed.com CNE 3,4,5 MCSE w2k CLE in training Registered Linux user #440182 http://en.opensuse.org/education -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

1 0

[opensuse-project] Buildserver for OSS on AIX
by Hans-Joachim Ehlers 05 Jan '09

05 Jan '09

Hi, sorry for jumping in with a pretty off topic question but at least it’s a place to start. I would like to create a build server for OSS running on AIX since the support from IBM for OSS on AIX is pretty marginal. The software versions build for AIX shall be equal to a given SLES version. This gives the opportunity to run the same software on AIX and Linux. An AIX server and compiler are available and reachable via the internet. So the question I have: - Is this the right group to ask question about the OpenSuse Build server and services ? - Is there any documentation about the Suse Build Service ? - Does the OpenSuse build system is sutiable /usable for such a task ? tia Hajo -- Hans-Joachim Ehlers Unix System Engineer

2 1

[opensuse-project] GCC RPMs and symbolic links
by Ian Nelson 05 Jan '09

05 Jan '09

I see that the GCC package installs binaries with a version suffix and creates a link. gcc43 install /usr/bin/gcc-4.3 and gcc-4.3 installs the symbolic link gcc->gcc-4.3. I've been hacking on an RPM for LLVM 2.4 and Ada has been giving me some issues, gnatmake and gnatlink and gnatbind are installed with a suffix but no link and the GCC frontend configure script doesn't work with that. Is this a defect? Against which package? It seems as if it is but I know that probably isn't that popular. Ian -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

2 1