[Seaside-dev] Re: [Seaside Issues] Issue 529 in seaside: Pretty print loops

[Julian Fitzell]

We should be a bit careful with these. While they're not, technically,
Seaside bugs, we *are* providing a downloadable distribution on the
website so we need to take a certain level of responsibility for
making sure the distribution works. It may be unreasonable to expect
an average Seaside user to know whether a bug is caused by some part
of our distribution build process or whether it is a bug in the
underlying Pharo image itself. This is one of the issues with choosing
to base our distribution on a moving target.

I'm not saying we shouldn't close these issues, but we should be
careful not to put people off reporting them. Perhaps we should add a
closed status called "Upstream" or something? "Invalid" kind of makes
it sound like the person made a mistake in even letting us know.

Julian

On Fri, Jan 15, 2010 at 11:47 PM,  <seaside at googlecode.com> wrote:
> Updates:
>        Status: Invalid
>
> Comment #1 on issue 529 by renggli: Pretty print loops
> http://code.google.com/p/seaside/issues/detail?id=529
>
> This is not a Seaside bug. This problem has probably already been reported
> and fixed:
> http://code.google.com/p/pharo/issues/detail?id=1435
>
> --
> You received this message because you are listed in the owner
> or CC fields of this issue, or because you starred this issue.
> You may adjust your issue notification preferences at:
> http://code.google.com/hosting/settings
>
> _______________________________________________
> issues mailing list
> To unsubscribe, email issues-leave at lists.seaside.st
> http://lists.seaside.st/listinfo/issues
>