You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Rob S." <rs...@home.com> on 2000/08/25 06:29:20 UTC
last call! tomcat-apache-howto.html
Here it is, I'm leaving revise mode and entering, "bum around before next
semester" mode ;) Thanks to Mike Bremford for sending in a much needed
beefing up to the Virtual Host section.
http://fuzz.cx/~rslifka/tomcat-apache-howto.html
- r
> -----Original Message-----
> From: Rob S. [mailto:rslifka@home.com]
> Sent: August 22, 2000 8:31 PM
> To: tomcat-dev@jakarta.apache.org; Tomcat-User@Jakarta. Apache. Org
> Subject: tomcat-apache-howto.html - first pass
>
>
> http://fuzz.cx/~rslifka/tomcat-apache-howto.html
>
> Some of the formatting is off (FrontPage, bleh), and there are a
> few incomplete sections towards the bottom. I'd like to get
> end-user feedback while I'm still in revise mode, which is why
> I'm cross-posting as well.
>
> Any and all suggestions welcome, please email privately or post
> to the tomcat-dev@jakarta.apache.org list. TIA! ;)
>
> - r
>
> p.s. I'm not a committer, but Alex is helping me in case anyone
> was wondering =)
>
Re: [BUG REPORTING] Usage Policy -- please read
Posted by Nick Bauman <ni...@cortexity.com>.
I don't think there is a way to unclose a bug report without converting it
to a bug first. :( grrrrr.
I can go into the backend and unopen it with an SQL update, if it's that
important.
On Fri, 25 Aug 2000, Geoff Soutter wrote:
> Nick,
>
> Any idea how to un-close a bug report (as apposed to a bug)?
>
> geoff
>
> ----- Original Message -----
> From: "Nick Bauman" <ni...@cortexity.com>
> To: <to...@jakarta.apache.org>
> Sent: Friday, August 25, 2000 2:02 PM
> Subject: [BUG REPORTING] Usage Policy -- please read
>
>
> > This is now in HTML format at znutar.cortexity.com:
> >
> > Proper Use Guidelines For Jakarta BugRat
> >
> > 1. Do report a bug with complete information. Four rules of thumb:
> >
> > Describe the bug
> > Describe the environment
> > Describe how to reproduce
> > Describe how to work around the bug (if posible)
> >
> > While these things are tecnically optional in BugRat, if yuou don't fill
> > them in with enough information, you bug may get your bug closed with "not
> > enough information"
> > as the reason.
> >
> > 2. Don't close a bug without a reason why it was closed.
> >
> > Follow these steps when closing a bug:
> >
> > click "admin"->click "View Bug By Id"->(Fill In Bug Number)->submit->click
> > "Assign New Comment To This Bug"->(Fill in comment)->submit->click "Close
> > This
> > Bug"
> >
> > Bugs closed without comment as to what action was necessary to close them
> > will be reopened. A good comment reason example to close a bug (or bug
> > report) is "Not a bug: a bad practice" or "Bug fixed in nightly build
> > 10-15-01".
> >
> > 3. If you aren't sure how to proceed, ask nick@cortexity.com.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
Re: [BUG REPORTING] Usage Policy -- please read
Posted by Geoff Soutter <ge...@whitewolf.com.au>.
Nick,
Any idea how to un-close a bug report (as apposed to a bug)?
geoff
----- Original Message -----
From: "Nick Bauman" <ni...@cortexity.com>
To: <to...@jakarta.apache.org>
Sent: Friday, August 25, 2000 2:02 PM
Subject: [BUG REPORTING] Usage Policy -- please read
> This is now in HTML format at znutar.cortexity.com:
>
> Proper Use Guidelines For Jakarta BugRat
>
> 1. Do report a bug with complete information. Four rules of thumb:
>
> Describe the bug
> Describe the environment
> Describe how to reproduce
> Describe how to work around the bug (if posible)
>
> While these things are tecnically optional in BugRat, if yuou don't fill
> them in with enough information, you bug may get your bug closed with "not
> enough information"
> as the reason.
>
> 2. Don't close a bug without a reason why it was closed.
>
> Follow these steps when closing a bug:
>
> click "admin"->click "View Bug By Id"->(Fill In Bug Number)->submit->click
> "Assign New Comment To This Bug"->(Fill in comment)->submit->click "Close
> This
> Bug"
>
> Bugs closed without comment as to what action was necessary to close them
> will be reopened. A good comment reason example to close a bug (or bug
> report) is "Not a bug: a bad practice" or "Bug fixed in nightly build
> 10-15-01".
>
> 3. If you aren't sure how to proceed, ask nick@cortexity.com.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
[BUG REPORTING] Usage Policy -- please read
Posted by Nick Bauman <ni...@cortexity.com>.
This is now in HTML format at znutar.cortexity.com:
Proper Use Guidelines For Jakarta BugRat
1. Do report a bug with complete information. Four rules of thumb:
Describe the bug
Describe the environment
Describe how to reproduce
Describe how to work around the bug (if posible)
While these things are tecnically optional in BugRat, if yuou don't fill
them in with enough information, you bug may get your bug closed with "not
enough information"
as the reason.
2. Don't close a bug without a reason why it was closed.
Follow these steps when closing a bug:
click "admin"->click "View Bug By Id"->(Fill In Bug Number)->submit->click
"Assign New Comment To This Bug"->(Fill in comment)->submit->click "Close
This
Bug"
Bugs closed without comment as to what action was necessary to close them
will be reopened. A good comment reason example to close a bug (or bug
report) is "Not a bug: a bad practice" or "Bug fixed in nightly build
10-15-01".
3. If you aren't sure how to proceed, ask nick@cortexity.com.