Mailinglist Archive: opensuse-factory (594 mails)
| < Previous | Next > |
Re: [opensuse-factory] openSUSE 11.2 and maintenance
- From: Dirk Müller <dmueller@xxxxxxx>
- Date: Thu, 10 Sep 2009 17:22:58 +0200
- Message-id: <200909101722.58234.dmueller@xxxxxxx>
On Thursday 13 August 2009, Henne Vogelsang wrote:
I think this is a good idea! I've created a fate for this:
https://features.opensuse.org/307621
I think it is a good idea to vote for the feature :)
So the summary is that we have here Magnus Boman, Petr Uzel and Alexandr
volunteering to review opensuse submissions, which is good news. However, the
actual policy is missing still.
I think it is sensible to require that all the packages have a devel project
assigned and that those devel projects have at least one bugowner and at least
one active maintainer.
That could be a fallback, yes. Who would staff the RRT?
I think the RRT is a good idea to handle whatever devel projects turn
unmaintained (the related community members disappear or are no longer
interested in working on it), but it is a bad idea to start with that setup.
Note that we have 18months to maintain the codebase, this is a long timeframe.
Greetings,
Dirk
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
- package updates can be submitted against openSUSE:11.2:UpdateAdrian can we make this a new request type maybe? Instead of another
webtool i would like to integrate this with the buildservice. Does not
sound too hard to do. Just a submitrequest with additional data attached
which we can later export to swamp. What do you think?
I think this is a good idea! I've created a fate for this:
https://features.opensuse.org/307621
I think it is a good idea to vote for the feature :)
- A group of openSUSE people (both community and Novell internal, IThat should be simple. Is there anyone who would be interested in this?
suggest 5 people) reviews update submissions if they're in line with the
opensuse update policy and coordinates their releases. Unclear how to
bootstrap this group.
So the summary is that we have here Magnus Boman, Petr Uzel and Alexandr
volunteering to review opensuse submissions, which is good news. However, the
actual policy is missing still.
- To ensure timely release of security updates, each devel group for 11.2We don't have this rule for devel projects for factory. As maintenance
must contain at least one Novell employee. We can think about relaxing
this for future openSUSE releases.
for released products is is just another assignment for the devel
projects i think we have to live without this.
I think it is sensible to require that all the packages have a devel project
assigned and that those devel projects have at least one bugowner and at least
one active maintainer.
I understand what you are
trying to achieve (an escalation path for the openSUSE maintenance team
you propose above) but i would rather handle this with a Rapid Response
Team.
That could be a fallback, yes. Who would staff the RRT?
The Rapid Response Team would be the Team the openSUSE Maintenance Team
can escalate updates to that they, for whatever reason, can't get from
the devel project.
I think the RRT is a good idea to handle whatever devel projects turn
unmaintained (the related community members disappear or are no longer
interested in working on it), but it is a bad idea to start with that setup.
Note that we have 18months to maintain the codebase, this is a long timeframe.
Greetings,
Dirk
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |