Yes! I agree.
On Thursday, 10 April 2014, Walter Bender walter.ben...@gmail.com wrote:
On Wed, Apr 9, 2014 at 9:21 PM, Daniel Narvaez
dwnarv...@gmail.comjavascript:;
wrote:
Something else to consider is what to do with priorities. It might make
sense to set one when confirming bugs, it's
This is probably going to be a bit controversial, but I think if something
is worth marking minor then it's probably not worth tracking. We will never
get to fix the minor but we will waste time triaging and retriaging them.
On Thursday, 10 April 2014, Gonzalo Odiard godi...@sugarlabs.org wrote:
Well, maybe call iy normal or low instead of minor, but we need a way
to separate the tickets we _need_ fix, the tickets we _want_ fix,
and the tickets _would_be_nice_ fix.
We have almost 250 tickets, if we can solve 50 tickets in these 2 months,
is important know what are the best candidates.
On Thu, Apr 10, 2014 at 6:52 AM, Gonzalo Odiard godi...@sugarlabs.org wrote:
Well, maybe call iy normal or low instead of minor, but we need a way
to separate the tickets we _need_ fix, the tickets we _want_ fix,
and the tickets _would_be_nice_ fix.
We have almost 250 tickets, if we can solve
What I'm saying is that the would be nice to fix will never be fixed,
they will keep accumulating and we will waste triage time on them over and
over. Better to just wontfix them, people can always send patches if they
care. Plus we tell them clearly it's up to them to do something if they
need
I disagree.
While is true manage the tickets have cost, is good have a record of things
we want to do,
even when we don't have the resources today to do it. More in the context
of a project
where we have volunteers some times more, some times less.
Just my two cents ...of pesos :)
Gonzalo
On
Yes, things we *want* to do are normal priority, my issue is with things
that would be nice to do :)
Terminology aside, I'm not saying it's bad, just expensive and IMO lower
priority then a lot of other awesome things we could do... But if there are
people interested in keeping records, all the
On Thu, Apr 10, 2014 at 01:27:09PM +0100, Daniel Narvaez wrote:
What I'm saying is that the would be nice to fix will never be
fixed, they will keep accumulating and we will waste triage time on
them over and over. Better to just wontfix them, people can always
send patches if they care. Plus
On 10 April 2014 21:18, James Cameron qu...@laptop.org wrote:
On Thu, Apr 10, 2014 at 01:27:09PM +0100, Daniel Narvaez wrote:
What I'm saying is that the would be nice to fix will never be
fixed, they will keep accumulating and we will waste triage time on
them over and over. Better to
On 10 April 2014 22:08, Daniel Narvaez dwnarv...@gmail.com wrote:
On 10 April 2014 21:18, James Cameron qu...@laptop.org wrote:
On Thu, Apr 10, 2014 at 01:27:09PM +0100, Daniel Narvaez wrote:
What I'm saying is that the would be nice to fix will never be
fixed, they will keep accumulating
Sam sent a pull request to fix this, reviews would be appreciated
https://github.com/sugarlabs/sugar/pull/333
(You might have the honour to empty the review queue for the first time in
a looong while).
On 17 February 2014 12:57, Daniel Narvaez dwnarv...@gmail.com wrote:
Hello,
parsing code
Any ideas what can be the possible reasons behind the following error ? the
sugar build is not running because of the following :
puneet@controller:~/sugar-build$ ./osbuild run
$ sudo broot run osbuild run
Type Shift-Alt-Q inside sugar to close.
Command failed: sugar-runner
Initializing
Hi,
Please check sugar-build/home/dotsugar/default/logs/shell.log
That has the error log
Sam
On Apr 11, 2014 3:06 PM, Puneet Kaur puneet.gk...@gmail.com wrote:
Any ideas what can be the possible reasons behind the following error ?
the sugar build is not running because of the following :
13 matches
Mail list logo
