[SoaS] [Sugar-devel] Sugar 0.88 packages

Tomeu Vizoso tomeu at tomeuvizoso.net
Thu May 13 13:30:15 EDT 2010

On Thu, May 13, 2010 at 18:47, Bernie Innocenti <bernie at codewiz.org> wrote:
> El Wed, 12-05-2010 a las 14:24 -0300, Daniel Drake escribió:
>> On 11 May 2010 20:23, Bernie Innocenti <bernie at codewiz.org> wrote:
>> > Would you like me to go on and apply any relevant patches also to the
>> > devel and F-13 branches in CVS? Let me know if you'd rather want me to
>> > run each individual patch through you instead of committing them
>> > directly. Either way is equally fast and easy on my side.
>> Can't you do it properly by committing the patches and releasing new tarballs?
>> No need to lock up the fixes.
> I'm posting all my patches to sugar-devel@, attaching them to tickets
> and ping individual people on IRC.

Are your patches in this queue?


If not, please read the code review process in the wiki and make sure
you follow it.

Also, today I tried to review a patch of you in trac that had
bitrotten because you hadn't updated it after review on the ml. Please
make sure this doesn't happen by updating the attached patches or by
pasting a link to the thread in archives.

> It's taking a lot of time because we have few active maintainers with
> privileges to ack patches. Regarding releasing official tarballs, the
> release manager position is currently vacant so don't expect them
> anytime soon.

There's quite a bit of things that non-maintainers can do to speed up
this process, but unfortunately my last call for help was ignored. If
people really care about this, please do reviews so that when the
maintainer gets to it it can just make a quick read and set the flag
to r+. It would also helped if submitters read the code guidelines in
the first place, of course.

Note that I'm still waiting for your replies to the comments on your
post "[PATCH 1/2] This fixes part of
http://bugs.sugarlabs.org/ticket/1876". (And again, make sure that
trac has a reference to the outcome of that review).

> While we're working to fix our review process, it makes sense for
> downstream projects on a tight schedule to apply obvious bugfix patches
> directly to their packages.

But in this case, there may be better alternatives.

> Ideally, some of the existing contributors would step up and become
> maintainers of specific modules or releases. I'm available to maintain
> the 0.88 branch unless someone else wants to and I offered to become a
> review peer for all the sugar-* modules.

Thank you, that's a very generous offer. Why don't you start by
pre-reviewing the patches in the queue so current maintainers see you
have the required experience? That way you win twice: speed up the
queue and become a maintainer yourself.

> BTW: I did some testing yesterday with F11-XO1-0.88 and results are very
> encouraging. I'm seeing some issues related to font-size and window
> borders. We need to figure out why these things work well in
> sugar-emulator in 1200x900 and not on the XO-1. I tried upgrading
> Metacity, but it did not seem to help.

Can you get some screenshots? (But please create a new thread)



> --
>   // Bernie Innocenti - http://codewiz.org/
>  \X/  Sugar Labs       - http://sugarlabs.org/
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

More information about the SoaS mailing list