Re: Changing defaults for read-only bugs

I am ok with this change.  However,he change log should clearly
reflect the change so admins can revise their configuration if needed

On 10/28/07, Gianluca Sforna <giallu-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> 
wrote:
> On 10/28/07, John Reese <jreese-f2MuJNAWfAzk1uMJSBkQmQ@xxxxxxxxxxxxxxxx> 
> wrote:
> > > AFAICT, a (small) patch to the code is needed for that, isn't it?
> >
> > Well, I just meant that I personally set the read-only thresholds so
> > that anyone could update or add to resolved issues.  I haven't actually
> > modified any of the code to prevent this, and I think the ability should
> > at least stay, as there is always someone who wants/needs it.
>
> Oh sorry, I just misread the bug_is_readonly() code so that I believed
> it had to be patched to allow anybody to post on closed bugs; I am not
> proposing to remove the feature altogether.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> mantisbt-dev mailing list
> mantisbt-dev-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/