[Sugar-devel] [Spam] Re: Add more components to bugs.sl.org
tony_anderson at usa.net
Tue Oct 13 16:17:29 EDT 2015
I think it would be desirable to have a separation of trac tickets for
each Sugar Activity. They are not a part of Sugar (except perhaps the
Journal Activity). Combining
all of the tracs in one makes it hard to find tracs that pertain to a
specific version of a specific Sugar Activity (e.g. tux-math).
On 10/13/2015 03:43 PM, James Cameron wrote:
> Taking a position I do not hold: the only reason I can think of is so
> that the git repository name relates to the component as a one to one.
> I don't think that is necessary, but that's what the original poster
> was asking.
> My other suggestions are unchanged.
> On Tue, Oct 13, 2015 at 07:18:03AM -0300, Gonzalo Odiard wrote:
>> In the past, we had a component for every sugar module (sugar-artwork, sugar,
>> sugar-toolkit, sugar-datastore).
>> A few years ago, as maintainership was common, all that components were unified
>> in the 'sugar' component.
>> What is the reason to separate them now?
>> On Sun, Oct 11, 2015 at 5:37 PM, James Cameron <quozl at laptop.org> wrote:
>> Yes, the Components and Versions lists in trac are out of date.
>> No, we can't expect or ask for users to choose between artwork,
>> toolkit, and jarabe. Users will get this wrong. I'm fine with just
>> Other suggestions:
>> 1. remove the 0.102.0 Milestone,
>> 2. add Versions for 0.100, 0.102, 0.104, 0.106,
>> 3. remove Versions before 0.98,
>> 4. make sure every activity in the Ubuntu or Fedora builds is listed
>> in the Component list.
>> James Cameron
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> Gonzalo Odiard
>>  mailto:quozl at laptop.org
>>  http://quozl.linux.org.au/
>>  mailto:Sugar-devel at lists.sugarlabs.org
>>  http://lists.sugarlabs.org/listinfo/sugar-devel
More information about the Sugar-devel