-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rob Weir wrote:
> Something to consider for AOO 4.1 is the value of a broad public beta
> program to solicit early feedback on builds. This could be a good
> complement to our formal QA efforts.
+1
I was thinking about it, long time ago.
- --
Albi
Am 06/13/2013 10:20 AM, schrieb Rory O'Farrell:
On Thu, 13 Jun 2013 10:06:49 +0200
Andre Fischer wrote:
On 12.06.2013 21:32, Andrea Pescetti wrote:
On 12/06/2013 Rob Weir wrote:
Something to consider for AOO 4.1 is the value of a broad public beta
program to solicit early feedback on builds.
On Thu, 13 Jun 2013 10:06:49 +0200
Andre Fischer wrote:
> On 12.06.2013 21:32, Andrea Pescetti wrote:
> > On 12/06/2013 Rob Weir wrote:
> >> Something to consider for AOO 4.1 is the value of a broad public beta
> >> program to solicit early feedback on builds. This could be a good
> >> complemen
On 12.06.2013 21:32, Andrea Pescetti wrote:
On 12/06/2013 Rob Weir wrote:
Something to consider for AOO 4.1 is the value of a broad public beta
program to solicit early feedback on builds. This could be a good
complement to our formal QA efforts.
I totally agree that we should do so. In retro
Am 06/12/2013 08:50 PM, schrieb Rob Weir:
On Wed, Jun 12, 2013 at 2:36 PM, Donald Whytock wrote:
On Wed, Jun 12, 2013 at 2:22 PM, Rory O'Farrell wrote:
On Wed, 12 Jun 2013 13:35:23 -0400
Rob Weir wrote:
Something to consider for AOO 4.1 is the value of a broad public beta
program to solic
On Wed, 12 Jun 2013 20:50:12 +0200
RGB ES wrote:
> 2013/6/12 Donald Whytock
>
> > On Wed, Jun 12, 2013 at 2:22 PM, Rory O'Farrell wrote:
> >
> > > On Wed, 12 Jun 2013 13:35:23 -0400
> > > Rob Weir wrote:
> > >
> > > > Something to consider for AOO 4.1 is the value of a broad public beta
> > >
On 12/06/2013 Rob Weir wrote:
Something to consider for AOO 4.1 is the value of a broad public beta
program to solicit early feedback on builds. This could be a good
complement to our formal QA efforts.
I totally agree that we should do so. In retrospective, it would have
been good to do it f
2013/6/12 Donald Whytock
> On Wed, Jun 12, 2013 at 2:22 PM, Rory O'Farrell wrote:
>
> > On Wed, 12 Jun 2013 13:35:23 -0400
> > Rob Weir wrote:
> >
> > > Something to consider for AOO 4.1 is the value of a broad public beta
> > > program to solicit early feedback on builds. This could be a good
On Wed, Jun 12, 2013 at 2:36 PM, Donald Whytock wrote:
> On Wed, Jun 12, 2013 at 2:22 PM, Rory O'Farrell wrote:
>
>> On Wed, 12 Jun 2013 13:35:23 -0400
>> Rob Weir wrote:
>>
>> > Something to consider for AOO 4.1 is the value of a broad public beta
>> > program to solicit early feedback on build
On Wed, Jun 12, 2013 at 2:22 PM, Rory O'Farrell wrote:
> On Wed, 12 Jun 2013 13:35:23 -0400
> Rob Weir wrote:
>
> > Something to consider for AOO 4.1 is the value of a broad public beta
> > program to solicit early feedback on builds. This could be a good
> > complement to our formal QA efforts
Hi Rory
Am 12.06.13 20:22, schrieb Rory O'Farrell:
On Wed, 12 Jun 2013 13:35:23 -0400
Rob Weir wrote:
Something to consider for AOO 4.1 is the value of a broad public beta
program to solicit early feedback on builds. This could be a good
complement to our formal QA efforts.
A beta program c
On Wed, 12 Jun 2013 13:35:23 -0400
Rob Weir wrote:
> Something to consider for AOO 4.1 is the value of a broad public beta
> program to solicit early feedback on builds. This could be a good
> complement to our formal QA efforts.
>
> A beta program could be set up like this:
>
> 1) After featu
Something to consider for AOO 4.1 is the value of a broad public beta
program to solicit early feedback on builds. This could be a good
complement to our formal QA efforts.
A beta program could be set up like this:
1) After feature freeze, and after smoke tests pass on the 3 major
platforms, we
13 matches
Mail list logo
