Re: [opensuse-factory] Bug Day/s Lets Get it going.

2007-06-04 Thread jdd

Andreas Jaeger wrote:


Do we need to write some policies for this?  Or is what we have
sufficient?


"scan the bug list right now and add you as bugs mail recipient (fix 
this sentence, I don't know the exact wording) to be up and running 
when the day begin"


jdd

--
http://www.dodin.net
http://gourmandises.orangeblog.fr/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] Bug Day/s Lets Get it going.

2007-06-04 Thread Magnus Boman
On Mon, 2007-06-04 at 14:47 +0200, Andreas Jaeger wrote:
> "Francis Giannaros" <[EMAIL PROTECTED]> writes:
> 
> > To the right list this time; this reply-to business will really be
> > the death of me ;)
> >
> > On 6/4/07, Andreas Jaeger <[EMAIL PROTECTED]> wrote:
> >>
> >> So, what needs to be done to get this going (besides announcing a day)?
> >>
> >> I'm in favor of doing it soon - and repeat if needed ;-)
> >>
> >> Andreas
> >
> > After speaking quickly to a few people on IRC we're thinking of the
> > weekend on the 16-17 of June. This is only one day after alpha5, but
> > I'm not sure we should wait a whole week later for the next weekend.
> >
> > So, to sum up, the plan would be:
> > * Have one bug day for clearing out old bugs (say, from 10.1) which
> > would be just after alpha5 time. Also encourage users to file
> > enhancement requests for 10.3 at this time, otherwise they may not be
> > implementable later.
> >
> > * Have another bug day after beta1 time (we don't have to think about
> > the date yet) for trying to really concentrate on all 10.3 bugs.
> >
> > * Can take place in #opensuse-bugs. bugbot currently reports all
> > openSUSE bug changes in there, but we'll change it at the time to only
> > report _new_ bugs to get the traffic down.
> >
> > I'm thinking we should only announce a day or two before the bug day,
> > so it's fresh in people's minds :).
> 
> Do we need to write some policies for this?  Or is what we have
> sufficient?

I think you made it clear in the status meeting, no? If there's a bug
that we can not decide what to do with it, then we'll assign it to you?
I guess my concern is, what if a bug is already assigned?
As I see it, we have a few options on what to do with each bug;

1. Close it if it's a "silly" bug (who decides what is silly?)
2. Move the bug forward to Factory if we think it's important for the
next version, but to big to be fixed for the current version
3. Ping the assigned developer (if there's an assigned developer. Else,
assign to [EMAIL PROTECTED] and ping)
4. Close bug if people's involved can not reproduce and "need info" has
not been replied to in 1-6 months

> 
> Andreas

I probably missed other scenarios but...

Cheers,
Magnus

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] Bug Day/s Lets Get it going.

2007-06-04 Thread Andreas Jaeger
"Francis Giannaros" <[EMAIL PROTECTED]> writes:

> To the right list this time; this reply-to business will really be
> the death of me ;)
>
> On 6/4/07, Andreas Jaeger <[EMAIL PROTECTED]> wrote:
>>
>> So, what needs to be done to get this going (besides announcing a day)?
>>
>> I'm in favor of doing it soon - and repeat if needed ;-)
>>
>> Andreas
>
> After speaking quickly to a few people on IRC we're thinking of the
> weekend on the 16-17 of June. This is only one day after alpha5, but
> I'm not sure we should wait a whole week later for the next weekend.
>
> So, to sum up, the plan would be:
> * Have one bug day for clearing out old bugs (say, from 10.1) which
> would be just after alpha5 time. Also encourage users to file
> enhancement requests for 10.3 at this time, otherwise they may not be
> implementable later.
>
> * Have another bug day after beta1 time (we don't have to think about
> the date yet) for trying to really concentrate on all 10.3 bugs.
>
> * Can take place in #opensuse-bugs. bugbot currently reports all
> openSUSE bug changes in there, but we'll change it at the time to only
> report _new_ bugs to get the traffic down.
>
> I'm thinking we should only announce a day or two before the bug day,
> so it's fresh in people's minds :).

Do we need to write some policies for this?  Or is what we have
sufficient?

Andreas
-- 
 Andreas Jaeger, Director Platform / openSUSE, [EMAIL PROTECTED]
  SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
   Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


pgp8RFbK167b8.pgp
Description: PGP signature


Re: [opensuse-factory] Bug Day/s Lets Get it going.

2007-06-04 Thread Francis Giannaros

To the right list this time; this reply-to business will really be
the death of me ;)

On 6/4/07, Andreas Jaeger <[EMAIL PROTECTED]> wrote:


So, what needs to be done to get this going (besides announcing a day)?

I'm in favor of doing it soon - and repeat if needed ;-)

Andreas


After speaking quickly to a few people on IRC we're thinking of the
weekend on the 16-17 of June. This is only one day after alpha5, but
I'm not sure we should wait a whole week later for the next weekend.

So, to sum up, the plan would be:
* Have one bug day for clearing out old bugs (say, from 10.1) which
would be just after alpha5 time. Also encourage users to file
enhancement requests for 10.3 at this time, otherwise they may not be
implementable later.

* Have another bug day after beta1 time (we don't have to think about
the date yet) for trying to really concentrate on all 10.3 bugs.

* Can take place in #opensuse-bugs. bugbot currently reports all
openSUSE bug changes in there, but we'll change it at the time to only
report _new_ bugs to get the traffic down.

I'm thinking we should only announce a day or two before the bug day,
so it's fresh in people's minds :).

Thoughts?

Regards,
--
Francis Giannaros   http://francis.giannaros.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [opensuse-factory] Bug Day/s Lets Get it going.

2007-06-04 Thread Andreas Jaeger

So, what needs to be done to get this going (besides announcing a day)?

I'm in favor of doing it soon - and repeat if needed ;-)

Andreas
-- 
 Andreas Jaeger, Director Platform / openSUSE, [EMAIL PROTECTED]
  SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
   Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


pgp5abZvhMvnD.pgp
Description: PGP signature


Re: [opensuse-factory] Installing openSUSE with from internet with rp-pppoe

2007-06-04 Thread Andreas Jaeger
"Vincenzo Barranco" <[EMAIL PROTECTED]> writes:

> Hi,
> So, I want to install openSUSE with the
> "openSUSE-10.2-GM-i386-mini.iso", now is possible to installing it
> using pppoe for retreiving the packages from the net?

This is not working - you need a router to do this,

Andreas
-- 
 Andreas Jaeger, Director Platform / openSUSE, [EMAIL PROTECTED]
  SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
   Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


pgpT66GEShQ6P.pgp
Description: PGP signature


Re: [opensuse-factory] Pushing AppArmor into the mainline kernel

2007-06-04 Thread Andreas Jaeger
"Alexey Eremenko" <[EMAIL PROTECTED]> writes:

> hi all !
>
> I would like to ask if there is an effort to push AppArmor into the
> mainline kernel ?

Yes - we do have some developers working on this and they went through
several cleanups already.

For example see  the emails on lkml starting on the 14th of May:

http://www.uwsg.iu.edu/hypermail/linux/kernel/0705.1/3048.html

> I know SELinux is already there, so I don't know if it's possible to
> push AppArmor too...

Andreas
-- 
 Andreas Jaeger, Director Platform / openSUSE, [EMAIL PROTECTED]
  SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
   Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


pgpDMtb1kt745.pgp
Description: PGP signature