Hi Rainer,
Rainer Bielefeld wrote (18-08-11 11:57)
This explanation still does not cover the case where a bug ís fixed in
master, but not in the release A branch, where it is listed as annoying.
Having is stricken out, cause of the fix in master, erroneously gives
the impression that it is fixe
Bjoern Michaelsen wrote (18-08-11 12:09)
On Thu, 18 Aug 2011 11:39:01 +0200
Cor Nouws wrote:
This explanation still does not cover the case where a bug ís fixed
in master, but not in the release A branch, where it is listed as
annoying. Having is stricken out, cause of the fix in master,
erron
On Thu, 2011-08-18 at 12:09 +0200, Bjoern Michaelsen wrote:
> The solution to that is simple: Before adding a bug to the "most
> annoying for 3.4" bug is has to have a 3.4 target. If it has not, I
> should not be added there.
This thread starts to look like noise. Is there a concrete inst
On Thu, 18 Aug 2011 11:39:01 +0200
Cor Nouws wrote:
> This explanation still does not cover the case where a bug ís fixed
> in master, but not in the release A branch, where it is listed as
> annoying. Having is stricken out, cause of the fix in master,
> erroneously gives the impression that it
Noel Power wrote (18-08-11 11:54)
Well I wasn't really trying to answer that question but more give the
developer-centric detail about getting a patch into the dev/release
branches. But... it f the bug has been fixed, it is fixed right, it has
to be marked as such, and in this case approval is as
Hi Lionel, all,
On Wed, 17 Aug 2011 20:49:43 +0200
Lionel Elie Mamane
wrote:
> Hi,
>
> I don't see any way in bugzilla to say things like:
> bug present / not present in master / libreoffice-3.4, ...
> bug fixed / not fixed in master / libreoffice-3.4, ...
>
> There is only *one* version fie
Michael Meeks wrote (18-08-11 11:49)
On Wed, 2011-08-17 at 22:49 +0200, Cor Nouws wrote:
Shouldn't it be backported in this case? ...
That is a separate decision. And if the choice is no, there still is the
problem: bug fixed in master, and is tricked out in most annoying for
3.4.x ..
On 18/08/11 10:39, Cor Nouws wrote:
Noel Power wrote (18-08-11 11:16)
For example, bug #40079; it is fixed in master, so I closed it. But
now it shows up as not blocking "LibreOffice 3.4 most annoying bugs"
anymore (it is striked out),
when we want a bug to be fixed in the 3.4 release then we
Hi Cor,
On Wed, 2011-08-17 at 22:49 +0200, Cor Nouws wrote:
> > Shouldn't it be backported in this case? ...
>
> That is a separate decision. And if the choice is no, there still is the
> problem: bug fixed in master, and is tricked out in most annoying for
> 3.4.x ..
Ah - but if it is
Noel Power wrote (18-08-11 11:16)
For example, bug #40079; it is fixed in master, so I closed it. But
now it shows up as not blocking "LibreOffice 3.4 most annoying bugs"
anymore (it is striked out),
when we want a bug to be fixed in the 3.4 release then we need to get
the patch into the gener
Hi,
I think Kohei has covered most of the questions below but..
On 17/08/11 19:49, Lionel Elie Mamane wrote:
Hi,
[...]
So I don't know when to close a bug. When it is fixed in master?
yes, and normally the committer does that, is it a rule? I don't know,
it's just what I and at least I know o
Hi Lionel,
On Wed, Aug 17, 2011 at 2:49 PM, Lionel Elie Mamane wrote:
> Hi,
>
> I don't see any way in bugzilla to say things like:
> bug present / not present in master / libreoffice-3.4, ...
> bug fixed / not fixed in master / libreoffice-3.4, ...
So, a rule of thumb I follow is, put the ver
Joop Kiefte wrote (17-08-11 22:08)
2011/8/17 Lionel Elie Mamane mailto:lio...@mamane.lu>>
So I don't know when to close a bug. When it is fixed in master? When
it is fixed in all branches where we want it fixed?
For example, bug #40079; it is fixed in master, so I closed it. But
Shouldn't it be backported in this case? ...
2011/8/17 Lionel Elie Mamane
> Hi,
>
> I don't see any way in bugzilla to say things like:
> bug present / not present in master / libreoffice-3.4, ...
> bug fixed / not fixed in master / libreoffice-3.4, ...
>
> There is only *one* version field, a
Hi,
I don't see any way in bugzilla to say things like:
bug present / not present in master / libreoffice-3.4, ...
bug fixed / not fixed in master / libreoffice-3.4, ...
There is only *one* version field, and *one* status field, not one per
branch.
So I don't know when to close a bug. When it
15 matches
Mail list logo
