On 6/4/07, Andreas Jaeger aj@suse.de 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,
On Mon, 2007-06-04 at 13:06 +0100, Francis Giannaros wrote:
On 6/4/07, Andreas Jaeger aj@suse.de 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?
We should announce it well in advance as you just did now, and then send out a reminder probably a day or two in advance.
I like the idea of starting with 10.1 bugs and move from there. We want to catch bugs that's annoying to people but have not yet been fixed. We also want to catch RFE bugs that people are passionate about and move them forward to 10.3 to make sure we fix them there.
Thanks Francis for taking a lead on this.
Regards,
Cheers, Magnus
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Il giorno lun, 04/06/2007 alle 22.18 +1000, Magnus Boman ha scritto:
Francis' plan of action is great.
We should announce it well in advance as you just did now, and then send out a reminder probably a day or two in advance.
Yes, I agree. In this way people can organise their time and more of them probably will be able to take part to the meeting.
I like the idea of starting with 10.1 bugs and move from there. We want to catch bugs that's annoying to people but have not yet been fixed. We also want to catch RFE bugs that people are passionate about and move them forward to 10.3 to make sure we fix them there.
Yes! :-)
Alberto
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Monday 04 June 2007 14:06:16 Francis Giannaros wrote:
I'm thinking we should only announce a day or two before the bug day, so it's fresh in people's minds :).
Nice, i will setup a wiki page for it soon (this week i hope) for some guidelines etc. (i already made this for the internal bugzilla screeners).
Added to the meeting tomorrow ...
On 6/4/07, Francis Giannaros francisg@gmail.com wrote:
On 6/4/07, Andreas Jaeger aj@suse.de 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 :).
Unfortunately bugzilla will be down for hours on Saturday since it's undergoing an upgrade, and I think it's important to really not have people hanging around, willing to help, while they can't do anything. Also, this being the first such organised day, it's important to keep the momentum going when it happens, so that's why we've decided to postpone the bugslashing until the next weekend -- that will be the 23-24th of June.
A full announcement with a wiki page entry will be posted sooner to the time as well.
Kind thoughts,
I was wondering if there is a module or command line tool that will strip the host name and reset the yast-installer module to ask for it's replacement on the next boot? I am looking for a tool similar to "sysprep" from m$. JT
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Fri, 2007-06-15 at 07:29 -0400, James Tremblay wrote:
I was wondering if there is a module or command line tool that will strip the host name and reset the yast-installer module to ask for it's replacement on the next boot? I am looking for a tool similar to "sysprep" from m$. JT
And i was wondering if you could get a clue about how mailing list work and could stop posting crap all over the place ...
-
Alberto Passalacqua -
Francis Giannaros -
James Tremblay -
Jonathan Arsenault -
Magnus Boman -
Martin Lasarsch