[Tracker-discuss] Feature/Change request handling procedure

[Stefan Seefeld]

Martin v. Löwis wrote:
> Erik Forsberg schrieb:
>> I fully agree that you should be able to turn a feature request into a
>> bug very easily, and that is exactly why I think the main class should
>> not be named "bug". I don't want another class for feature requests, I
>> want the main class to cover as many types of issues (see, there it is
>> again, the perfect word for it! :) as possible. 
> 
> I may have missed some discussion; IMO, to the end user, the name
> of the main class should be invisible. It can be called "bug", "issue",
> "contribution", or "jabberwocky". As an end user, I don't want to have
> to type the name of the main class into the computer, ever. In
> particular, I hope that I can refer to some issue as
> bugs.python.org/<issue>.

Well, by default, <issue> in roundup is spelled <issue_class_name><id>

i.e. 'issue35', or 'bug266'. If you don't want that we have to play with
apache rewrite rules.

Regards,
		Stefan

-- 

      ...ich hab' noch einen Koffer in Berlin...