Are we getting the Edgy version of Gimp without Tango for Feisty?

[Joel Bryan Juliano]

On 3/10/07, Matt Zimmerman <mdz at ubuntu.com> wrote:
> On Sat, Mar 10, 2007 at 05:00:33AM +0800, Joel Bryan Juliano wrote:
> > On 3/10/07, Matt Zimmerman <mdz at ubuntu.com> wrote:
> > > Because it hasn't changed in Debian unstable since then, and for most
> > > packages, we incorporate new upstream releases from Debian unstable.
> >
> > I guess it's not possible to use the experimental repository for Feisty.
> >
> > but the 2.3 version is been with the branch for more than a year since Dec 2005.
> >
> > I'm wondering what's the difference between OpenOffice.org 2.2 and
> > Gimp 2.3.15...
>
> Ubuntu is a distribution based on Debian.  This means that, except where
> special attention is devoted to a package by Ubuntu developers, we use
> Debian's package from unstable.  Therefore, Gimp is the same version as the
> one in Debian unstable.
>
> The new OpenOffice.org 2.2 has been brought in from Debian experimental by
> Matthias Klose periodically during the development of Feisty, with
> appropriate care and testing.
>
> I hope this clarifies the difference for you.
>

Yes, it does! thank you for the clarification!

I really think that there must some really important implementations
regarding the management of an experimental packages or any package at
all.

Like a formation of a team, that specifically handles the important
package from experimental/unstable, this will be a great help for
stabilization of a certain packages, or by just providing attention to
that certain package.

I think it's important that every people involved with -devel and
Ubuntu should consider building up a team or being a part of a team.
Because this brings up alot of advantages, like being a team will
ensures somebody will still takes over a package when one or two
members of the team isn't available, i.e. Ekiga takeover.

The question is how to form the team? On what respect.

Supposed that Ubuntu has a 70/20/10 model approach (just borrowed from
google for this example), where 70% of it's energy and resources is
focused on important things, like support, desktop and main, 20% is
for other interesting stuff, probably some from main and universe, and
10% really means other.

The 70% team will be focusing on desktop applications, and things that
will be included in Ubuntu, i.e. "Accessories Team", "Sound & Video
Team", "Internet Team", "Office Team", "Help and Support Team", etc.

Decisions can also be based upon, probably with the help of statistics
like popularity-contest, wiki documentation popularity, bugs
statistics, etc.

And it's really important to analyze what are the bottlenecks, what
part of the team is really getting some trouble. Those can be included
on the 70% of things.

And what about daily-push for -devel/MOTU? anyone?

Just my thoughts.

-- 
Stay away from Piracy, use Open Source.