I cross checked and now is disabled:
http://issues.apache.org/bugzilla/enter_bug.cgi?product=Cocoon+1
http://issues.apache.org/bugzilla/enter_bug.cgi?product=Cocoon+2
Thanks for your support!
Best Regards,
Antonio Gallardo.
Yoav Shapira escribió:
Hi,
I just set Cocoon 1 to "closed for bug entry" status. Cocoon 2 was
already set that way. I also verified that the "New Issue" dialog in
Bugzilla doesn't allow either Cocoon 1 or Cocoon 2 as the product for
a new issue. All set?
Yoav
On 3/28/06, Sander Temme <[EMAIL PROTECTED]> wrote:
On Tue, March 28, 2006 8:30 am, Antonio Gallardo said:
I am not aware about the internal configuration in the ASF. I see we
currently use bugzilla 2.18.5. In our company, we use bugzilla 2.20.1.
in the "product" form there is a checkbox called: "Closed for bug entry:
". Bugzilla 2.20.1 has also other benefits as RSS feeds and so on. The
upgrade is pretty straight forward.
WDYT?
It's on my list, but not very high. We are on the latest release of 2.18,
which has closed a couple of security holes. I would like to take a more
detailed look at 2.20 before we upgrade, since it has some features that
we may start using.
The current Bugzilla installation already has the 'closed for bug entry'
checkbox, and whenever a project moves to JIRA, I check that box. It could
bew that this went forgotten for Cocoon, but I have no way to check right
now. I'm in China this week and did not bring the laptop that has all my
ASF stuff on it. Perhaps another Bugzilla Admin can have a look.
The 'closed for bug entry' prevents users from creating new bugs, but I
don't think it prevents users from manipulating or commenting on existing
bugs. If this is what you are concerned about, I currently don't have a
solution.
S.
--
Sander Temme [EMAIL PROTECTED]
Webmail -- no signatures
--
Yoav Shapira
Nimalex LLC
1 Mifflin Place, Suite 310
Cambridge, MA, USA
[EMAIL PROTECTED] / www.yoavshapira.com
