From: Alexei_Roudnev (Alexei_Roudnev_at_exigengroup.com)
Date: Wed Apr 11 2007 - 23:58:57 CEST
Message-ID: <1b0f01c77c84$9a860470$6f31a8c0@sjc.exigengroup.com> From: "Alexei_Roudnev" <Alexei_Roudnev@exigengroup.com> Date: Wed, 11 Apr 2007 14:58:57 -0700 Subject: Re: [suse-sles-e] SLES10 SP1 in public beta. My congratulations to SuSe team!
Just one example.
SLES10 don't work with iSCSI on multiport filers without few hacks (some not
obvious).
On the other hand, it is pretty simple to adjust service dependencies,
correct few minor problems in config files, and magically everything will
work. It can be done not only by developers but by beta testers too, in some
cases. Alternative can be to create a documenbt explaining how to configure
it. Again, it can be done outside of main SuSe team, and it can improve
system usability (for now, using iSCSI in multipath configurration became a
big challenge requiring serious linux understanding, in comparison to SLES9
when irt was well adjusted and documented).
----- Original Message -----
From: "Rasmus Plewe" <rplewe@suse.de>
To: <suse-sles-e@suse.com>
Sent: Wednesday, April 11, 2007 2:22 PM
Subject: Re: [suse-sles-e] SLES10 SP1 in public beta. My congratulations to
SuSe team!
> On Wed, Apr 11, 2007 at 12:36:07PM -0500, Peter Van Lone wrote:
> > On 4/11/07, Alexei_Roudnev <Alexei_Roudnev@exigengroup.com> wrote:
> > >
> > >Yes, but you got a chance to find a critical failures BEFORE you
released
> > >final version. For the zero price.
> >
> > yep ... it just seems more like what an OSS company would do
>
> Probably it wasn't clear what I meant: If you release a beta version,
> the expectation you set is that feedback will lead to changes in the
> system. While this is true for beta, it mostly isn't for RC. I believe
> that it does more harm than good releasing RC versions as "public
> beta". OTOH, releasing a beta/RC version as "preview" (like we did for
> Brainshare) is different.
>
> > >O.B. != 'you can go and download', it is at least 'anyone woth
subscription
> > >can request access, explaining what exactly he is going to test'.
> >
> > I also agree with this ... it really seems to me that a much broader
> > beta cycle would be good for all concerned. Do you have any
> > suggestions, Rasmus, as to whom it would be most effective to contact,
> > in order to encourage this change in beta process?
>
> As usual, it comes down to resources. Our resources are limited, and we
> try to use them as effectively as possible. We have the closed beta
> program, not because our OpenSource code is so very secret, but because
> we need to control the load. Doubling the number of beta testers does
> not give you twice as many discovered bugs, but an increased number of
> duplicates, false alarms, of administration and communication.
> So we need to balance the additional coverage against the additional
> overhead, with our finite resources.
>
> I guess most effective would be Product Management, as they are the ones
> collecting the needs of our customers, and allocating resources to
> fulfill them.
>
>
> Regards,
> Rasmus
> --
> Rasmus Plewe --- Linux Beta Test Coordinator
> SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
> Maxfeldstrasse 5, D-90409 Nuernberg
> tel.: +49-911-74053-644 fax: +49-911-74053-483
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
> For additional commands, e-mail: suse-sles-e-help@suse.com
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Thu Apr 12 2007 - 02:05:22 CEST