bugs

[Jon Stevens]

someone going to update this with the new information?

http://jakarta.apache.org/site/bugs.html

also, it would be nice if http://nagoya.apache.org had an index.html that
also pointed to the right url to the bug tracking system.

thanks,

-jon


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: bugs

[Ceki Gülcü]

At 23:42 07.02.2001 -0800, you wrote:
>someone going to update this with the new information?
>
>http://jakarta.apache.org/site/bugs.html

I'll handle the above URL. For the link below, you need someone with the appropriate 
rights. I don't have access to nagoya. Ceki


Ceki Gülcü   e-mail: [EMAIL PROTECTED] (preferred)
av. de Rumine 5  [EMAIL PROTECTED]
CH-1005 Lausanne  
SwitzerlandTel: ++41 21 351 23 15


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: bugs

[Ceki Gülcü]

Hi again,

The page http://jakarta.apache.org/site/bugs.html now points to the Apache Bug DB and 
no longer to BugRat. Two questions remain:

1) Who should be contacted in case of problems with ABDB? I have refrained from 
listing Pier's address publicly.

2) Why should a user need to file a bug report with ABDB and post to the corresponding 
developers mailing list? I think that filing a bug report should automatically trigger 
a post to the appropriate dev ML. Another possibility is to *make sure* that the 
concerned developers get notified through e-mail about the bug report. The requirement 
to have the user report bugs twice, once through ABDB and once through a ML is not 
optimal. 

Cheers, Ceki

At 23:42 07.02.2001 -0800, you wrote:
>someone going to update this with the new information?
>
>http://jakarta.apache.org/site/bugs.html
>
>also, it would be nice if http://nagoya.apache.org had an index.html that
>also pointed to the right url to the bug tracking system.
>
>thanks,
>
>-jon


Ceki Gülcü   e-mail: [EMAIL PROTECTED] (preferred)
av. de Rumine 5  [EMAIL PROTECTED]
CH-1005 Lausanne  
SwitzerlandTel: ++41 21 351 23 15


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: bugs

[Jon Stevens]

on 2/8/01 1:19 AM, "Ceki Gülcü" <[EMAIL PROTECTED]> wrote:

> Hi again,
> 
> The page http://jakarta.apache.org/site/bugs.html now points to the Apache Bug
> DB and no longer to BugRat. Two questions remain:

thanks! I'm glad others (especially you!) are helping out with the site now.
:-)

> 1) Who should be contacted in case of problems with ABDB? I have refrained
> from listing Pier's address publicly.

general@ works for me.

> 2) Why should a user need to file a bug report with ABDB and post to the
> corresponding developers mailing list? I think that filing a bug report should
> automatically trigger a post to the appropriate dev ML. Another possibility is
> to *make sure* that the concerned developers get notified through e-mail about
> the bug report. The requirement to have the user report bugs twice, once
> through ABDB and once through a ML is not optimal.

I agree. You can change the wording to be more appropriate.

-jon

-- 
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/> && <http://java.apache.org/turbine/>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: bugs

[James Duncan Davidson]

on 2/8/01 1:19 AM, Ceki Gülcü at [EMAIL PROTECTED] wrote:

> 1) Who should be contacted in case of problems with ABDB? I have refrained
> from listing Pier's address publicly.

webmaster@ -- we need to get some more people behind that address to make
sure that things are handled.

> 2) Why should a user need to file a bug report with ABDB and post to the
> corresponding developers mailing list? I think that filing a bug report should
> automatically trigger a post to the appropriate dev ML. Another possibility is
> to *make sure* that the concerned developers get notified through e-mail about
> the bug report. The requirement to have the user report bugs twice, once
> through ABDB and once through a ML is not optimal.

Agreed. 

-- 
James Duncan Davidson
http://x180.net/ !try; do();


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: bugs

[Pier P. Fumagalli]

I'll work on Nagoya tonight. I have to change a bunch of configurations in
httpd.conf to make it happen :)

Pier

-- 

Pier P. Fumagalli  


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Can't commit any new bugs

[Mark R. Diggory]

I've tried numerous times, but when I try to commit a new bug I never 
get a response from the server, it times out, the bug is not commited.

I'm trying to add one to the

http://issues.apache.org/bugzilla/enter_bug.cgi?product=Commons

product=Commons
version=nightly builds
component=HttpClient
os=all
platform=all
severity=enhancment
initial state=NEW

summary=...
description=...

Thank you,
-Mark Diggory
[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Adminitrivia: Assigning new bugs to the "list"

[Howard M. Lewis Ship]

Currently, new Tapestry bugs are all assigned to me, personally.

I would prefer that new bugs be "assigned" to the Tapestry developer list.

Is there a way to do this cleanly in BugZilla, or do I create a "fake" user
([EMAIL PROTECTED])?


--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Adminitrivia: Assigning new bugs to the "list"

[Craig R. McClanahan]

On Fri, 4 Apr 2003, Howard M. Lewis Ship wrote:

> Date: Fri, 4 Apr 2003 10:44:26 -0500
> From: Howard M. Lewis Ship <[EMAIL PROTECTED]>
> Reply-To: Jakarta General List <[EMAIL PROTECTED]>
> To: Jakarta General List <[EMAIL PROTECTED]>
> Subject: Adminitrivia: Assigning new bugs to the "list"
>
> Currently, new Tapestry bugs are all assigned to me, personally.
>
> I would prefer that new bugs be "assigned" to the Tapestry developer list.
>
> Is there a way to do this cleanly in BugZilla, or do I create a "fake" user
> ([EMAIL PROTECTED])?
>

The latter is how we've done it for several other projects, and seems to
work fine.  You'll probably want to disable the fake user's login after
it's created, so that nobody accidentally uses that account.

Craig

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Adminitrivia: Assigning new bugs to the "list"

[Howard M. Lewis Ship]

Thanks.  My next challenge is to bootstrap this.  I suspect the mail from
bugzilla.org with the password for user "[EMAIL PROTECTED]" is
being eaten by EZLM.  I can't subscribe [EMAIL PROTECTED] to the list,
because EZLM sends a confirmation message to bugzilla that is ignored by
bugzilla.  Catch-22.  Is there a way around this, or must I prostrate myself
before infrastructure?

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry



> -Original Message-
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] 
> Sent: Friday, April 04, 2003 12:07 PM
> To: Jakarta General List
> Subject: Re: Adminitrivia: Assigning new bugs to the "list"
> 
> 
> 
> 
> On Fri, 4 Apr 2003, Howard M. Lewis Ship wrote:
> 
> > Date: Fri, 4 Apr 2003 10:44:26 -0500
> > From: Howard M. Lewis Ship <[EMAIL PROTECTED]>
> > Reply-To: Jakarta General List <[EMAIL PROTECTED]>
> > To: Jakarta General List <[EMAIL PROTECTED]>
> > Subject: Adminitrivia: Assigning new bugs to the "list"
> >
> > Currently, new Tapestry bugs are all assigned to me, personally.
> >
> > I would prefer that new bugs be "assigned" to the Tapestry 
> developer 
> > list.
> >
> > Is there a way to do this cleanly in BugZilla, or do I 
> create a "fake" 
> > user ([EMAIL PROTECTED])?
> >
> 
> The latter is how we've done it for several other projects, 
> and seems to work fine.  You'll probably want to disable the 
> fake user's login after it's created, so that nobody 
> accidentally uses that account.
> 
> Craig
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Adminitrivia: Assigning new bugs to the "list"

[Andrew C. Oliver]

Since I assume you meticulously responded to my email on the list 
adminstrator issue but neglected to reply You should be able to 
create said user, intercept his info when it goes to the list and then 
do an "allow" on the first bug filed...

-Andy

Howard M. Lewis Ship wrote:

Currently, new Tapestry bugs are all assigned to me, personally.

I would prefer that new bugs be "assigned" to the Tapestry developer list.

Is there a way to do this cleanly in BugZilla, or do I create a "fake" user
([EMAIL PROTECTED])?
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Adminitrivia: Assigning new bugs to the "list"

[Andrew C. Oliver]

Since you meticulously reponded to my email months ago about making sure 
you were a remote adminstrator since I'd rather not be, despite not 
having confirmed this to me, its not a problem.  When you get the 
rejection mesage just put "allow"

If my assumption that you meticulously responded to my email was 
incorrect, this presents an opportunity to correct this oversight :-)

-Andy

Howard M. Lewis Ship wrote:

Thanks.  My next challenge is to bootstrap this.  I suspect the mail from
bugzilla.org with the password for user "[EMAIL PROTECTED]" is
being eaten by EZLM.  I can't subscribe [EMAIL PROTECTED] to the list,
because EZLM sends a confirmation message to bugzilla that is ignored by
bugzilla.  Catch-22.  Is there a way around this, or must I prostrate myself
before infrastructure?
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry


 

-Original Message-
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] 
Sent: Friday, April 04, 2003 12:07 PM
To: Jakarta General List
Subject: Re: Adminitrivia: Assigning new bugs to the "list"



On Fri, 4 Apr 2003, Howard M. Lewis Ship wrote:

   

Date: Fri, 4 Apr 2003 10:44:26 -0500
From: Howard M. Lewis Ship <[EMAIL PROTECTED]>
Reply-To: Jakarta General List <[EMAIL PROTECTED]>
To: Jakarta General List <[EMAIL PROTECTED]>
Subject: Adminitrivia: Assigning new bugs to the "list"
Currently, new Tapestry bugs are all assigned to me, personally.

I would prefer that new bugs be "assigned" to the Tapestry 
 

developer 
   

list.

Is there a way to do this cleanly in BugZilla, or do I 
 

create a "fake" 
   

user ([EMAIL PROTECTED])?

 

The latter is how we've done it for several other projects, 
and seems to work fine.  You'll probably want to disable the 
fake user's login after it's created, so that nobody 
accidentally uses that account.

Craig

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]