[Foresight-devel] Re: Upstream Bugs

[Ken VanDine]

This can be complicated, it is hard to know if the bug is upstream or
local to foresight.  Things like this I would tend to think are
upstream bugs.  Plus, we track so close to upstream that many of our
bugs are upstream, so they do really need to be filed there.  However,
it would be very cool if we could track them as well.  If it gets
fixed upstream, but not released for a while we could apply the patch
to Foresight to get the fix out sooner.  So, if the issues could both
be created and reference the upstream issue in jira, that would be
cool.

--Ken


On 4/9/07, Paul Cutler <pcutler at foresightlinux.org> wrote:
> I was chatting with a Foresight user this morning, who is experiencing a
> crash in X-chat (similar to Bertux, who was discussing it yesterday in IRC),
> where Xchat won't start.  Using Bug Buddy, a bug report was filled out on
> GNOME's bugzilla ( http://bugzilla.gnome.org/show_bug.cgi?id=425836), which
> explained why I couldn't find it in JIRA.
>
> More for my education, but I thought I'd ask, what is the proper etiquette
> in filling out a bug report for Foresight?  I know we track as closely to
> upstream as possible, but as I was trying to help, my first instinct was to
> check JIRA rather than GNOME's bugzilla.
>
> The FAQ was a little vague, so I thought I'd ask here, and throw up a page
> on the wiki around bug reporting later this week.
>
> Thanks.
>
> Paul
> _______________________________________________
> Foresight-devel mailing list
> Foresight-devel at lists.rpath.org
> http://lists.rpath.org/mailman/listinfo/foresight-devel
>