Hi,
> What I'm most unhappy about is that we have 783 bugs in New,
> Assigned, Reopened, NeedInfo... that seems like quite a lot. Perhaps
Then let's start and solve two of the 783 so we can these cross off the list
+---+
Hi,
> What I'm most unhappy about is that we have 783 bugs in New,
> Assigned, Reopened, NeedInfo... that seems like quite a lot. Perhaps
Then let's start and solve two of the 783 so we can these cross off the list
+---+
lör 2007-01-13 klockan 01:06 +0100 skrev Ruediger Pluem:
> This could be modified to:
>
> 1. Fix on trunk => Change state in "Resolved, fixed" and add a comment with
> revision
>of fix.
> 2. Proposed for backport => Leave state in "Resolved, fixed" and add a
> comment with
>revision of
On Fri, Jan 12, 2007 at 11:33:45AM +, Joe Orton wrote:
> What is the difference between a "RESOLVED" bug and a "CLOSED" one? Is
> it not possible to re-open/add comments to CLOSED reports or something?
> It's always seemed like a meaningless distinction to me, going through
> marking stuff
On 01/12/2007 11:14 PM, Sander Temme wrote:
>
> On Jan 12, 2007, at 1:04 PM, Roy T. Fielding wrote:
>
>> On Jan 12, 2007, at 3:33 AM, Joe Orton wrote:
>>
>>> What is the difference between a "RESOLVED" bug and a "CLOSED" one? Is
>>> it not possible to re-open/add comments to CLOSED reports or
On Jan 12, 2007, at 1:04 PM, Roy T. Fielding wrote:
On Jan 12, 2007, at 3:33 AM, Joe Orton wrote:
What is the difference between a "RESOLVED" bug and a "CLOSED"
one? Is
it not possible to re-open/add comments to CLOSED reports or
something?
It's always seemed like a meaningless distinction
Joe Orton wrote:
> On Thu, Jan 11, 2007 at 10:11:18PM -0800, Sander Temme wrote:
>>
>> Yes, Closed should be the final resting place for bug reports, for
>> good or for bad.
>
> What is the difference between a "RESOLVED" bug and a "CLOSED" one? Is
> it not possible to re-open/add comments to
On Jan 12, 2007, at 3:33 AM, Joe Orton wrote:
What is the difference between a "RESOLVED" bug and a "CLOSED"
one? Is
it not possible to re-open/add comments to CLOSED reports or
something?
It's always seemed like a meaningless distinction to me, going through
marking stuff CLOSED seems like
On Jan 12, 2007, at 3:33 AM, Joe Orton wrote:
Yes, Closed should be the final resting place for bug reports, for
good or for bad.
What is the difference between a "RESOLVED" bug and a "CLOSED"
one? Is
it not possible to re-open/add comments to CLOSED reports or
something?
It's always se
On Thu, Jan 11, 2007 at 10:11:18PM -0800, Sander Temme wrote:
>
> On Jan 11, 2007, at 1:40 PM, Ruediger Pluem wrote:
>
> >A week sounds good to me. I guess some of them are my fault as I only
> >set them to resolved fixed and never visited them again as I thought
> >that they reached their fina
On Jan 11, 2007, at 1:40 PM, Ruediger Pluem wrote:
A week sounds good to me. I guess some of them are my fault as I
only set
them to resolved fixed and never visited them again as I thought
that they reached
their final state. Now I found out that you only have the option to
close it once
On 01/11/2007 10:22 PM, William A. Rowe, Jr. wrote:
> Ruediger Pluem wrote:
>
>>Hi,
>>
>>could someone please add version 2.2.4 to the product Apache httpd-2 in
>>bugzilla?
>>Are there any ideas how we can document / automate this as part of the
>>release process?
>>This issue pops up regulary
On 01/11/2007 10:12 PM, Sander Temme wrote:
>
> On Jan 11, 2007, at 12:42 PM, Ruediger Pluem wrote:
>
>> could someone please add version 2.2.4 to the product Apache httpd-2
>> in bugzilla?
>
>
> Done.
Thanks.
>
>> Are there any ideas how we can document / automate this as part of
>> the
Ruediger Pluem wrote:
> Hi,
>
> could someone please add version 2.2.4 to the product Apache httpd-2 in
> bugzilla?
> Are there any ideas how we can document / automate this as part of the
> release process?
> This issue pops up regulary after each release.
My bad, sorry, it's already been done
On Jan 11, 2007, at 12:42 PM, Ruediger Pluem wrote:
could someone please add version 2.2.4 to the product Apache
httpd-2 in bugzilla?
Done.
Are there any ideas how we can document / automate this as part of
the release process?
This issue pops up regulary after each release.
Hard to au
Hi,
could someone please add version 2.2.4 to the product Apache httpd-2 in
bugzilla?
Are there any ideas how we can document / automate this as part of the release
process?
This issue pops up regulary after each release.
Regards
Rüdiger
16 matches
Mail list logo