[IAEP] What to report where - Was Re: Sugar on a Stick switches to a new Bug Tracker
tomeu at sugarlabs.org
Sun Aug 23 03:06:28 EDT 2009
On Sat, Aug 22, 2009 at 16:03, Caroline Meeks<caroline at solutiongrove.com> wrote:
> hmm ok let me see if I understand.
> Teachers, parents etc. who may have a hard time understanding whether they
> are reporting a bug on Sugar, Sugar on a Stick or an activity should use
> SoaS Development team will use launch pad.
> People doing QA should put bugs into dev unless its a sugar on a stick
> only issue.
Are we sure about this? Some bugs won't be clear where do they really
belong until a developer looks at it, and SoaS people may also like
tracking sugar-only bugs on their bugtracker. For example, Ubuntu
tracks Debian bugs on their bugtracker and Fedora tracks GNOME, X,
Also, normally a bug in a downstream is not closed when upstream fixes
it, but when it gets into a release on that downstream. Which is the
biggest reason for splitting bug trackers, IMO.
> Is that a correct restatement of what you want?
> I wonder if all questions should just go to GetSatisfaction. Is there an
> advantage to the LaunchPad questions section?
> I wonder if we are doing the right thing, is GetSatsfaction solving enough
> problems for us to be worth it? Its nice but it is yet another site...Does
> Launchpad have a Spanish UI available?
> On Sat, Aug 22, 2009 at 9:51 AM, Sebastian Dziallas <sebastian at when.com>
>> Hi Caroline,
>> here's what I discussed with Luke over IRC.
>> * Questions related to SoaS: Launchpad Answers Section
>> * Issues encountered on SoaS (stressing "issues" here): Launchpad Bug
>> Tracker (we can link a bug also to reports at other bug trackers!)
>> * Feature Requests which target Sugar directly should go to
>> Following this strategy, GetSatisfaction would be more intended for
>> general end-user support, meaning people who run Sugar on
>> no-matter-which-platform-or-distro. Launchpad should be SoaS-specific.
>> I'll take some time today to put bugs into Launchpad and to migrate our
>> feature list for v2 over there, too.
>> Caroline Meeks wrote:
>>> Where do you want teachers interacting with you? Do you want me, and
>>> people I give clues to, to put questions into Launchpad or
>>> Do you want me
>>> and others to try to guess if a bug is SoaS or Sugar or should we enter
>>> into Launchpad
>>> if we are using SoaS and let you decide to move it?
>>> What about activity related issues?
>>> What about activity related issues on SoaS, like an activity not scaling.
>>> On Thu, Aug 20, 2009 at 2:32 PM, Sebastian Dziallas <sebastian at when.com
>>> <mailto:sebastian at when.com>> wrote:
>>> Hi everybody,
>>> with the imminent release of the SoaS v2 Beta in just ten days, I
>>> like to announce the switch to Launchpad as our bug tracker.
>>> We have been evaluating an instance Luke Faraone set us up with lately
>>> and are confident that it will fit our needs. The upcoming beta
>>> is the first one intended to be used with this instance. More
>>> we will use it to track bugs, as well as new features.
>>> Note that this change only affects Sugar on a Stick, while the core
>>> Sugar bug tracker stays at dev.sugarlabs.org
>>> You can access and explore it here: https://launchpad.net/soas
>>> --Your SoaS Team
>>> IAEP -- It's An Education Project (not a laptop project!)
>>> IAEP at lists.sugarlabs.org <mailto:IAEP at lists.sugarlabs.org>
>>> Caroline Meeks
>>> Solution Grove
>>> Caroline at SolutionGrove.com
>>> 617-500-3488 - Office
>>> 505-213-3268 - Fax
> Caroline Meeks
> Solution Grove
> Caroline at SolutionGrove.com
> 617-500-3488 - Office
> 505-213-3268 - Fax
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
«Sugar Labs is anyone who participates in improving and using Sugar.
What Sugar Labs does is determined by the participants.» - David
More information about the IAEP