-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Janne Karhunen wrote:

On Thursday 13 October 2005 21:35, Christoph Thiel wrote: ...

...

The decision-making authority on what's distributed via YOU is held by the project managers for SUSE Linux. Basically the policy is to distributed security fixes and fixes for "serious" bugs. If there are user-contributed fixes for bugs that are qualifyed as "serious" (by the project managers), than we will of course publish an update via YOU. We normally don't do updates to add extra features, etc.

Any chances we could set up a BZ voting system for these? It would probably serve as a good input to SUSE managers as what is considered as 'serious' by the users.

That's not the idea. At least not at the moment. IMHO. As far as YOU is concerned, it's "only" to distribute security fixes and severe bugfixes. But I suppose that you mean "in general", not just YOU. "SUSE Linux" is the Linux distribution and package selection as decided by the SUSE project and/or product managers because they offer support for those packages. If you would like to have another package selection, then make your own, based on the packages available in SUSE Linux OSS, but that won't be "SUSE Linux". Christoph, AJ, Adrian: please correct me if I'm wrong ;) As an example, have a look at SUPER, SLICK, etc...: http://www.opensuse.org/1_CD_install#How_to_create_your_own_1_CD_install http://www.opensuse.org/SUPER http://www.opensuse.org/SLICK Note that the SUSE staff has some great ideas to "solve" those "issues", namely the Build Servers. There isn't much information that can be disclosed as of now, just because I think the concept has to go through some more reviews and prototyping before it can be announced to the community in a detailed way. Well, at least, that's my opinion about it, I don't work for Novell/SUSE, so... I'll leave that decision (when to give details about the build servers) to AJ, Adrian, Christoph, ... ;) Basically, without getting into the details, what is trying to be achieved is that you could (if it is technically feasible) create your distribution based on a package selection of yours, pretty much "à la carte". Yes, with tool support. And yes, the package selection will include packages maintained by community packagers (i.e. packagers not employed by Novell, like Packman, me, ...). At least that's the plan ;) And if you have software that's not packaged on SUSE Linux, have a look at the 3rd party packagers' repositories. And if it's still not there, either package them yourselves (e.g. join Packman to maintain them) or ask the Packman team, me, or another community packager whether he has the time to make and maintain RPMs of it. The list of repositories is available here: http://www.opensuse.org/YaST_package_repository cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFDT1B6r3NMWliFcXcRAq1mAJ9odK6sbk39fd3A5ydo7478tgIH/QCbBOd1 DKKojtKJEdDrd36NG7ZiXhA= =WaRs -----END PGP SIGNATURE-----

On Fri, Oct 14, 2005 at 10:01:53AM +0300, Janne Karhunen wrote:

On Friday 14 October 2005 09:30, Pascal Bleser wrote:

...

...

Any chances we could set up a BZ voting system for these? It would probably serve as a good input to SUSE managers as what is considered as 'serious' by the users.

That's not the idea. At least not at the moment. IMHO.

Problem is that users might be slightly less motivated about bug reporting if they never see the fixes. AFAIK even Fedora manages to distribute fixes back to community. But then again, it's much more buggy to begin with ;)

Did you run YOU on 10.0 yet? Quite a large number of fixes already ;)

...

As far as YOU is concerned, it's "only" to distribute security fixes and severe bugfixes. But I suppose that you mean "in general", not just YOU.

What is consicered as severe always depends on whom you ask. For me, now i'd appreciate if growisofs worked ./

It works for a lot of people. What is your bugnr? Ciao, Marcus

Hi, On Friday, October 14, 2005 at 10:01:53, Janne Karhunen wrote:

On Friday 14 October 2005 09:30, Pascal Bleser wrote:

...

...

Any chances we could set up a BZ voting system for these? It would probably serve as a good input to SUSE managers as what is considered as 'serious' by the users.

That's not the idea. At least not at the moment. IMHO.

Problem is that users might be slightly less motivated about bug reporting if they never see the fixes. AFAIK even Fedora manages to distribute fixes back to community. But then again, it's much more buggy to begin with ;)

There you have to understand the concept of how openSUSE developes distributions. Let me explain. We have a "code stream" that is constantly developed. Its called EDGE. Everytime a packager submits a fix, version update, new feature, new package its build in EDGE. You find EDGE as an installation repository here [1]. Then from time to time we "freeze" the EDGE stream and allow only fixes to go in. No new features, no version updates, no new packages. On fixed dates (usually every second thursday) we build installable medias from the EDGE stream so people can test the same "state" of the "frozen" EDGE stream together. First they are called previews which then lead to betas which lead to release candidates which lead to a gold master. Once we have a goldmaster we "copy" the frozen stream to another location and unfreeze the EDGE stream again. Then you have 2 streams: - "unfrozen" EDGE that recives: * fixes * new packages * new features * new versions of packages - A released product (like 10.0) that recives: * Security fixes * fixes for serious bugs So the direct impact of your fixes, package wishes or the results of your bugreports you _always_ find in EDGE. Henne [1] EDGE installation repository: http://download.opensuse.org/distribution/SL-OSS-edge/inst-source/ -- Henne Vogelsang, Subsystems "Rules change. The Game remains the same." - Omar (The Wire)

On 14/10/05, Henne Vogelsang wrote:

Once we have a goldmaster we "copy" the frozen stream to another location and unfreeze the EDGE stream again. Then you have 2 streams:

Is this true? That it is not until GM that the split is from the EDGE stream? So there is a period where there is no branch taking new features? When we saw that 10.1 Alpha came out before 10.0 GM, is that only because the final release is delayed by production? Pflodo

Hello, Does the EDGE repository also include security updates? I have 10.0.42 installed, and so far that is the only installation source that YaST has accepted. Thanks, Andy Henne Vogelsang wrote: <snipped>

- "unfrozen" EDGE that recives: * fixes * new packages * new features * new versions of packages

- A released product (like 10.0) that recives: * Security fixes * fixes for serious bugs

So the direct impact of your fixes, package wishes or the results of your bugreports you _always_ find in EDGE.

Henne

[1] EDGE installation repository:

http://download.opensuse.org/distribution/SL-OSS-edge/inst-source/

On Sun, Oct 16, 2005 at 09:48:12AM -0500, Andy Smith wrote:

Hello,

Does the EDGE repository also include security updates? I have 10.0.42 installed, and so far that is the only installation source that YaST has accepted.

Security bugs will be fixed ... in the next snapshot. (or when continuois syncing is done, as soon as it is checked in.) Several security updates like for the released products will not be done. Ciao, Marcus

On Mon, Oct 17, 2005 at 07:16:09AM +1000, Peter Flodin wrote:

On 17/10/05, Marcus Meissner wrote:

...

Security bugs will be fixed ... in the next snapshot. (or when continuois syncing is done, as soon as it is checked in.)

Several security updates like for the released products will not be done.

Ciao, Marcus

Ok just some clarification (last time and I will update the wiki and don't want to get it wrong :-)

If we take the current state where we have a released 10.0 and 10.1 in alpha.

1. All fixes/updates in upstream packages are evaluated and applied to the EDGE stream.

Yes.

2. Security fixes that are severe (like Firefox 1.07) are also applied to released 10.0 and published as an update. a) Is there any guideline on the selection criteria (or does 'severe' sum it up?)

Hmm? Nothing has changed from 9.x to 10.0, security updates happen as before.

b) For how long are severe security fixes applied to Released? 6 months until the next GM release?

This happens like it was for the last years. For box releases we usually do that for 2 years. If EDGE still gets frozen and released every 6 months there is probably no need to change that cycle and currently no one has stepped up to me and told me that this will change. Ciao, Marcus (SUSE Security Teamlead)

Hello, Am Freitag, 14. Oktober 2005 10:52 schrieb Jorge Luis Arzola: [...]

Hey, I have lost of cool stuff packaged here I would like to share. I would like, for exemple, to join the packman team or any other to serve the comunity :) I've been the packager of some projects ocasionally. I was the initial packager of ktts and some other kde related projects, and know rpm's insides descently. So which team would like me? I am at the comunity's orders ;-)

so please tell me what should I do to join one of such packager teams, because it's a pity I allways make packages of the newest stuff just for myself and a few friends here.

I just wonder why nobody has answered your mail yet ;-) If you want to join packman, have a look at the FAQ on packman.links2linux.de or write a mail to packman@links2linux.de. If you want your own repository on gwdg.de (suser-*), send a mail to Eberhard Moenkeberg. The opensuse-packaging mailinglist could also be interesting for you ;-) Regards, Christian Boltz PS: No, I'm not a packman or suser-* packager. The only program I maintain as RPM (and help to develop) is "Fontlinge". -- .tsi neshcaweg lebanhcS red mhi eiw ,nebierhcs os redej run lloS senie nebatshcuB netsre ned hcodej nnad uD tsetllos esiewretneuqesnoK .nereileksunim seztaS [Andreas Kneib in suse-linux]