On Fri, Jun 15, 2012 at 05:50:37PM +0200, Bjoern Michaelsen wrote:
> Hi all,
>
> here are the minutes of todays QA call.
>
> community building/communication (Cor?):
>- beta testers for 3.6.0 beta 1
>- 3.6.0 beta 1 available in ppa (Bjoern)
> - Wheres a good howto? (Florian)
>
El 15/06/12 13:27, Petr Mladek escribió:
Hi Florian,
On Thu, 2012-06-14 at 10:07 +0200, Florian Reisinger wrote:
Hi!
I am not sure anyone has seen my suggestion:
Alpha 1: 3.6.0a1
Beta 1: 3.6.0b1
RC 1: 3.6.0r0
RC 2: 3.6.0r1
Ah, this does not work because we could not mention "r" (same as "r
Hi all,
some of your messages you write as an answer to other messages are
rejected, currently I can't find out why.
In my details view the Subject line is scrambled, looks like "Subject:
=?windows-1252?Q?Re=3A_=5BLibreoffice-qa=5D_New_Bugzilla_?=
=?windows-1252?Q?Version_Picker_items_=96_2
I agree with the save comment, I'll change that right now. Also
realized I didn't put a note in for regressions so I added to the
bottom notes:
**Regressions**
Special attention should be paid to regressions. In most cases a
regression calls for an increase in priority but in some cases it will
no
Joel Madero píše v Po 18. 06. 2012 v 09:32 -0700:
> Version 2, changed orientation and tried to take comments into
> account. Let me know what you all think.
It is much better readable. I finally got a better picture :-)
Well, I think that it still need some thinking. You set "inability to
safe"
Rainer Bielefeld píše v Po 18. 06. 2012 v 17:16 +0200:
> Hi all,
>
> I am happy to see that we have a solution for the general problem, I
> will change picker texts with 3.6.0.0.beta2
>
> The remaining problem is what we will do with
Ah, I forgot this ;-)
> 3.7.0.0.alpha1+daily
> 3.7.0.0.a
Joel Madero píše v Po 18. 06. 2012 v 07:04 -0700:
> I'll modify the orientation today or tomorrow and try to see where
> regression should fit. I think that it has to go in Priority and not in
> Severity.
Makes sense.
> As for how devs use it, I agree completely that right now it's
> almost u
Hi all,
I am happy to see that we have a solution for the general problem, I
will change picker texts with 3.6.0.0.beta2
The remaining problem is what we will do with
3.7.0.0.alpha1+daily
3.7.0.0.alpha2+daily
3.7.0.0.beta1+ daily
3.7.0.0.beta2+ daily
3.7.1.0.alpha1+daily
3
Rainer Bielefeld píše v Po 18. 06. 2012 v 13:21 +0200:
> Joel Madero schrieb:
> > I brainstormed a bit today and I came up with this flowchart.
>
>
> Hi Joel,
>
> great to see that all in a chart, your conclusions and definitions seem
> plausible.
>
> But the chart also shows the limitations o
I'll modify the orientation today or tomorrow and try to see where
regression should fit. I think that it has to go in Priority and not in
Severity. As for how devs use it, I agree completely that right now it's
almost useless but maybe if it becomes more uniform and it actually
provides some i
Joel Madero schrieb:
I brainstormed a bit today and I came up with this flowchart.
Hi Joel,
great to see that all in a chart, your conclusions and definitions seem
plausible.
But the chart also shows the limitations of that concept: It's really
sophisticated, and no developer will sit at
Hi all,
unfortunately I still was too lazy to learn enough concerning
bibisecting, but it would be great if those who already have some
experience would do some bibisecting for Bugs where that seems useful:
- LibO 3.5 or later
- Reproduced for Linux
I created a new Whiteboard key word *bibise
Petr Mladek píše v Čt 14. 06. 2012 v 16:40 +0200:
> What about the following scheme?
>
> Help / AboutBugzilla Picker Info
> --
> 3.6.0.0.alpha13.6.0.0.alpha1
> 3.6.0.0.beta1 3.6.0.0.beta1
> 3.6.0.0.be
Joel Madero píše v Pá 15. 06. 2012 v 23:09 -0700:
> I brainstormed a bit today and I came up with this flowchart. Looking
> for input. I read through email threads and see that prioritizing bugs
> has been an interesting discussion but as of now looks to be pretty
> unsettled. I'm going to make a s
Hi Joel,
On 2012-06-15 at 23:09 -0700, Joel Madero wrote:
> I brainstormed a bit today and I came up with this flowchart. Looking
> for input. I read through email threads and see that prioritizing bugs
> has been an interesting discussion but as of now looks to be pretty
> unsettled. I'm going t
15 matches
Mail list logo
