[Deploying Sakai] Shouldn't bug reports be easier to read for humans?

Jean-Francois Leveque jean-francois.leveque at upmc.fr
Wed Jul 17 01:19:53 PDT 2013

I'm personally not aware or reasons to preserve the old values, that's 
why I was asking. Unless I get answers from people who need the old 
values to be kept, I won't.

I'm adding the production list now to reach a larger audience who might 
need the old values.

Unless this part of the code is subject to review like kernel because 
changes are known to be risky, I think I can handle it myself.

On 17/07/2013 04:12, Matthew Jones wrote:
> Agreed. If it's important to you, submit a patch or contract with a
> developer/commercial affiliate to have it resolved. Would be a few lines
> of code and a few new message strings.
> The code is somewhere in
> portal/portal-util/util/src/java/org/sakaiproject/portal/util/ErrorReporter.java
> I think you'd want to preserve the old values in-case anyone is using
> them and append new values like Created (formatted)
> Unless it's a high priority bug (breaks tool functionality) or a desired
> local feature, generally it could take a while until it gets resolved.
> On Tue, Jul 16, 2013 at 9:17 PM, Poindexter, David Ray
> <davpoind at iupui.edu <mailto:davpoind at iupui.edu>> wrote:
>     Dev resources, I'm guessing.
>     --
>     David Poindexter
>     Sent from my mobile
>     On Jul 16, 2013, at 10:49 AM, "Jean-Francois Leveque"
>     <jean-francois.leveque at upmc.fr
>     <mailto:jean-francois.leveque at upmc.fr>> wrote:
>      > Hi,
>      >
>      > I've created https://jira.sakaiproject.org/browse/SAK-22022 as a
>     feature
>      > request some time ago.
>      >
>      > Do we have reasons not to do this?
>      >
>      > Cheers,
>      > J-F

More information about the production mailing list