RE: Jonathan Thomas (JontheEchidna) is a MOTU

[Christopher Swift]

Congratulations Jonathan on your MOTUship! It's nice to see people taking risks 
by approaching the kUbuntu ninjas :).

-Original Message-
From: Nathan Handler 
Sent: 28 January 2009 12:05
To: Submit and discuss any Ubuntu related news stories 

Cc: Masters of the Universe ; Jonathan Thomas 

Subject: Re: Jonathan Thomas (JontheEchidna) is a MOTU

On Wed, Jan 28, 2009 at 12:00 AM, Emmet Hikory  wrote:
>I'm pleased to annouce that Jonathan Thomas has become a MOTU.
> Jonathan has been working extensively with the Kubuntu Ninjas, and is
> firmly amoung those to thank for both the effective management of
> Kubuntu bugs and rapid release of available KDE updates.  Please
> welcome him to the team.

Congrats Jonathan! Welcome to the team.

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu



-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: motu-release team needs members

[Iulian Udrea]

2009/1/28 Stefan Potyra 

> Hi,
>

Hello


> Now looking that [1], I see that we've only 3 members left, so I guess
> motu-release could need at least one or better yet two more members.
>


I would like to join the MOTU Release team, so please consider this
my application to become a MOTU Release member.

My name is Iulian Udrea and I'm seventeen year old.  I am both an Ubuntu
and a FOSS Developer.  Before I got the MOTU status I was interested in
working with the MOTU release team.  Now that I am a MOTU I would like
to give a hand and work with the MOTU Release.

In two release cycles I saw how the team really work, how they deal with
bug fixes, new upstream releases and so forth.

I read [0] and everything is understood, I have no questions about it.

Launchpad page: https://launchpad.net/people/iulian
Wiki page: https://wiki.ubuntu.com/IulianUdrea

[0] https://wiki.ubuntu.com/FreezeExceptionProcess

Thank you for your consideration.

--
Iulian Udrea
iul...@ubuntu.com
-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Jonathan Thomas (JontheEchidna) is a MOTU

[Nathan Handler]

On Wed, Jan 28, 2009 at 12:00 AM, Emmet Hikory  wrote:
>I'm pleased to annouce that Jonathan Thomas has become a MOTU.
> Jonathan has been working extensively with the Kubuntu Ninjas, and is
> firmly amoung those to thank for both the effective management of
> Kubuntu bugs and rapid release of available KDE updates.  Please
> welcome him to the team.

Congrats Jonathan! Welcome to the team.

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: R: motu-release organisational meeting

[Emmet Hikory]

norse...@alice.it wrote:
> Unfortunately, I'm rather busy at the moment and won't be able to
> contribute much for this (and I'm afraid also next) release, certainly
> not as a motu-release member. Please remove me from the team, if any
> volunteer want to step in to fill the post please do so.

Thank you for your past work to help ensure the quality of the
previous releases.  I've removed you from the team in launchpad, and
updated the MOTU Leaders wiki page.

-- 
Emmet HIKORY


-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: motu-release team needs members

[Emmet Hikory]

Stefan Potyra wrote:
> Now I completely forgot what the policy to add more members to key teams was, 
> but I vaguely recall that it started with asking for applicants on this list. 
> So that's what I'm doing right now.

The policy for membership in motu-release is detailed in the wiki
(1).  A call for applications is indeed the first step when a team is
undersized.

1: https://wiki.ubuntu.com/MOTU/Teams/KeyTeamPolicy

-- 
Emmet HIKORY

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: Early backports to reduce post-release fixes

[Emmet Hikory]

Reinhard Tartler wrote:
> Luca Falavigna writes:
> 
>> How can we help motu-sru to avoid some SRU requests for trivial tasks,
>> allowing a greater audience to test packages without the need to
>> upgrade? My proposal is to prepare early backports of the most commonly
>> used packages in Universe. Starting from Feature Freeze, we could
>> identify some packages with high popcon and determine if it's worth to
>> prepare a backport for current stable release (new upstream releases,
>> new features to be tested, and so on), so the main part of the Ubuntu
>> users can effectively test packages and report issues, so they can be
>> fixed in time for the release.
> 
> Short: I like the idea.
> 
> I could imagine a lightweight approach: Activate the ~ubuntu-dev (or
> ~motu) PPA, and use it as "backports-staging" archive. Proposed policy:
> 
> - proposed package backports should be tracked via a malone bug
> - any motu may upload there if he feels that a package should be
>   backported, mentioning the LP bug number
> - the backport teams tracks these bugs and approves backports if
>   "enough" positive feedback from users has been given in the LP bug

After reviewing the backports process (1), I don't think we need an
even lighter-weight process to handle these.  From my reading, it only
takes a few people to say it works to be backported.  If these initial
reports are negative, then the package ought be fixed in the development
release anyway.

Despite the process, I don't think this will actually help with the
problem at hand.  In my experience, the majority of packages that fail
to work at all (or perhaps even install) suffer from one of three
problems: 1) they missed a library transition (perhaps even an informal
one), 2) they need to be built against a newer version of the build
tools because they failed to include some change that was done at a
lower level, or 3) they have some incompatibility with some other change
in the distribution that went untested during the cycle.

Since backports (or PPA builds) are rebuilds, they will mask issues
of the first two types, and since they would be targeted at the previous
release, will not be affected by the third.  With the current situation,
some packages fail, are trivial to fix, and are fixed (albeit perhaps
with some delay for various reasons).  With such a change, we may
instead have a perception of regressions: where a package that is known
to work as a backport suddenly doesn't work in a release users are
likely to be significantly more annoyed than in the case where they
upgraded to something that didn't work.

We would do better to try to close outstanding dependency issues by
reviewing the debcheck output (2), and revitalise the work on automated
installation tests using piuparts, to get that running on some shared
infrastructure with viewable output.  This ought resolve most
installation issues, and with appropriate piuparts scripting, may even
be able to handle many of the cases where a package completely fails to run.

For more comprehensive work towards ensuring that packages work as
expected, it may be sensible to write test cases for the automated
testing framework (3).  This would probably benefit from extensions to
cover a wider variety of software than is currently tested.

1: https://help.ubuntu.com/community/UbuntuBackports
2: http://qa.ubuntuwire.com/debcheck/
3: https://wiki.ubuntu.com/Testing/Automation/Desktop/

-- 
Emmet HIKORY

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

motu-release team needs members

[Stefan Potyra]

Hi,

first of all thanks a lot, Cesare, for your efforts within the motu-release 
team!

Now looking that [1], I see that we've only 3 members left, so I guess 
motu-release could need at least one or better yet two more members.

Now I completely forgot what the policy to add more members to key teams was, 
but I vaguely recall that it started with asking for applicants on this list. 
So that's what I'm doing right now.

If you know the impact of upgrades at late stages, don't shy away from reading 
changelogs and patches, also have the ability to make unliked decisions like 
rejecting freeze exceptions, then motu-release needs you. Please send in your 
application as reply to this thread.

Thanks,
 Stefan.
--
[1]: 


signature.asc
Description: This is a digitally signed message part.
-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

Re: R: motu-release organisational meeting

[Stefan Potyra]

Hi Cesare,

On Wednesday 28 January 2009 11:41:32 norse...@alice.it wrote:
> Unfortunately, I'm rather busy at the moment and won't be able to
> contribute much for this (and I'm afraid also next) release, certainly not
> as a motu-release member. Please remove me from the team, if any volunteer
> want to step in to fill the post please do so.

That's sad to hear.

So the meeting is scheduled for Tuesday, February 3rd, 14.00 UTC.

Cheers,
 Stefan.


signature.asc
Description: This is a digitally signed message part.
-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu

R: motu-release organisational meeting

[norsetto]

Unfortunately, I'm rather busy at the moment and won't be able to contribute 
much for this (and I'm afraid also next) release, certainly not as a 
motu-release member. Please remove me from the team, if any volunteer want to 
step in to fill the post please do so.

Cheers,

norsetto

-Messaggio originale-
Da: ubuntu-motu-boun...@lists.ubuntu.com per conto di Stefan Potyra
Inviato: mar 27/01/2009 12.58
A: ubuntu-motu@lists.ubuntu.com
Oggetto: motu-release organisational meeting
 
Hi motu-release members,

with FeatureFreeze approaching at Feb 19, I guess it'd be good if we schedule 
an organisational meeting. What do you think?

What date would suit you? Maybe this Friday, at 14.00h UTC?

Cheers,
 Stefan.

-- 
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu