"Francis Giannaros" <francisg@gmail.com> writes:
....To the right list this time; this reply-to business will really be the death of me ;)
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 :).
Do we need to write some policies for this? Or is what we have sufficient? Andreas -- Andreas Jaeger, Director Platform / openSUSE, aj@suse.de 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