You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Henning Schmiedehausen (JIRA)" <ji...@apache.org> on 2006/09/28 01:17:50 UTC
[jira] Created: (INFRA-962) Close Velocity Bugzilla / make it read
only.
Close Velocity Bugzilla / make it read only.
--------------------------------------------
Key: INFRA-962
URL: http://issues.apache.org/jira/browse/INFRA-962
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Reporter: Henning Schmiedehausen
Someone just opened a ~ 2 years old bug with the Bugzilla. As we moved to Velocity quite a while ago, that really surprised me.
(http://issues.apache.org/bugzilla/show_bug.cgi?id=28308)
Is it possible to make the Bugzilla for Velocity "read only" for historical documentation or plainly remove it? (I don't know if the bugs are liked somewhere outside but I doubt it).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (INFRA-962) Close Velocity Bugzilla / make it read
only.
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-962?page=all ]
Henri Yandell updated INFRA-962:
--------------------------------
Component/s: Bugzilla
> Close Velocity Bugzilla / make it read only.
> --------------------------------------------
>
> Key: INFRA-962
> URL: http://issues.apache.org/jira/browse/INFRA-962
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Bugzilla
> Reporter: Henning Schmiedehausen
>
> Someone just opened a ~ 2 years old bug with the Bugzilla. As we moved to Velocity quite a while ago, that really surprised me.
> (http://issues.apache.org/bugzilla/show_bug.cgi?id=28308)
> Is it possible to make the Bugzilla for Velocity "read only" for historical documentation or plainly remove it? (I don't know if the bugs are liked somewhere outside but I doubt it).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-962) Close Velocity Bugzilla / make it
read only.
Posted by "Will Glass-Husain (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-962?page=comments#action_12438252 ]
Will Glass-Husain commented on INFRA-962:
-----------------------------------------
I think you mean "moved to JIRA". just a clarification.
> Close Velocity Bugzilla / make it read only.
> --------------------------------------------
>
> Key: INFRA-962
> URL: http://issues.apache.org/jira/browse/INFRA-962
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Reporter: Henning Schmiedehausen
>
> Someone just opened a ~ 2 years old bug with the Bugzilla. As we moved to Velocity quite a while ago, that really surprised me.
> (http://issues.apache.org/bugzilla/show_bug.cgi?id=28308)
> Is it possible to make the Bugzilla for Velocity "read only" for historical documentation or plainly remove it? (I don't know if the bugs are liked somewhere outside but I doubt it).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-962) Close Velocity Bugzilla / make it
read only.
Posted by "Henning Schmiedehausen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-962?page=comments#action_12438310 ]
Henning Schmiedehausen commented on INFRA-962:
----------------------------------------------
Yeah, thanks. It was already getting late here... :-)
> Close Velocity Bugzilla / make it read only.
> --------------------------------------------
>
> Key: INFRA-962
> URL: http://issues.apache.org/jira/browse/INFRA-962
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Reporter: Henning Schmiedehausen
>
> Someone just opened a ~ 2 years old bug with the Bugzilla. As we moved to Velocity quite a while ago, that really surprised me.
> (http://issues.apache.org/bugzilla/show_bug.cgi?id=28308)
> Is it possible to make the Bugzilla for Velocity "read only" for historical documentation or plainly remove it? (I don't know if the bugs are liked somewhere outside but I doubt it).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (INFRA-962) Close Velocity Bugzilla / make it read
only.
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henri Yandell closed INFRA-962.
-------------------------------
Resolution: Won't Fix
My understanding is that you can stop new entries in Bugzilla, but you can't stop people commenting on the ones that are there. When that happens in Commons, we just post to the issue with a link to the JIRA issue and either giving them an update or asking them to use the JIRA issue instead.
> Close Velocity Bugzilla / make it read only.
> --------------------------------------------
>
> Key: INFRA-962
> URL: https://issues.apache.org/jira/browse/INFRA-962
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Bugzilla
> Reporter: Henning Schmiedehausen
>
> Someone just opened a ~ 2 years old bug with the Bugzilla. As we moved to Velocity quite a while ago, that really surprised me.
> (http://issues.apache.org/bugzilla/show_bug.cgi?id=28308)
> Is it possible to make the Bugzilla for Velocity "read only" for historical documentation or plainly remove it? (I don't know if the bugs are liked somewhere outside but I doubt it).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira