[Debian-olpc-devel] How _should_ we import new changes into git?

Luke Faraone luke.faraone at gmail.com
Tue Jan 13 16:33:07 UTC 2009

On Tue, Jan 13, 2009 at 9:46 AM, Jonas Smedegaard <dr at jones.dk> wrote:

> I reverted because you updated from stable to unstable branch.
> Current packaging does not handle multiple concurrent branches. As long
> as we only handle a single branch, I want it to be the latest stable
> branch, and thus avoid unstable branches completely.
> I suggest leave the "trivial" packaging of core sugar parts to me for
> now. With "trivial" i mean things like keeping in sync with upstream.
> I suggest that you work on packaging more activities, and on finding and
> squashing bugs - also bugs in the core Sugar packages.

Many of the bugs are fixed in later sugar releases, and the current upcoming
sugar release (Jan 16, 0.83 Beta 1) is a feature freeze (and beta1), after
which only bugfixes will be made (and is "almost" stable) until post-final
release of the 0.84 series.

I will see what I can do to migrate some of the activities in Ubuntu but not

Luke Faraone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/debian-olpc-devel/attachments/20090113/cab4d733/attachment.htm 

More information about the Debian-olpc-devel mailing list