[opensuse-factory] openSUSE 11.2 and maintenance
Hi, its time to start thinking about how we want to manage updates to openSUSE 11.2 when it is released. I think it is a good idea to incrementally open up the process of releasing updates to the community so that everybody can submit updates. While talking to various people we came up with the following proposal: - the openSUSE community proposes an update policy - the openSUSE community comes up with a devel project layout for all packages in 11.2 (probably similar to the layout in factory) - maintenance updates are triggered by asking for a SWAMPID in bugzilla like usual - there will be an externally accessible "simple" interface to SWAMP where anyone can submit a patchinfo (this has to be developed). Due to time constraints we can not open up the internal workflow tracking to the outside as no proper ACL support can be implemented in time for 11.2. - package updates can be submitted against openSUSE:11.2:Update - A group of openSUSE people (both community and Novell internal, I 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. This group is also responsible for handling security updates with coordinated release with care. - To ensure timely release of security updates, each devel group for 11.2 must contain at least one Novell employee. We can think about relaxing this for future openSUSE releases. Comments,opinions, feedback? Thanks, Dirk -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, 12 Aug 2009, Dirk Müller wrote:
its time to start thinking about how we want to manage updates to openSUSE 11.2 when it is released. I think it is a good idea to incrementally open up the process of releasing updates to the community so that everybody can submit updates.
While talking to various people we came up with the following proposal:
- the openSUSE community proposes an update policy
- the openSUSE community comes up with a devel project layout for all packages in 11.2 (probably similar to the layout in factory)
- maintenance updates are triggered by asking for a SWAMPID in bugzilla like usual
- there will be an externally accessible "simple" interface to SWAMP where anyone can submit a patchinfo (this has to be developed). Due to time constraints we can not open up the internal workflow tracking to the outside as no proper ACL support can be implemented in time for 11.2.
- package updates can be submitted against openSUSE:11.2:Update
- A group of openSUSE people (both community and Novell internal, I 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. This group is also responsible for handling security updates with coordinated release with care.
- To ensure timely release of security updates, each devel group for 11.2 must contain at least one Novell employee. We can think about relaxing this for future openSUSE releases.
I like this idea. Maybe it needs to be coordinated with the testing group
as well. See
http://lists.opensuse.org/opensuse-testing/2009-07/msg00002.html
I think that a minimum of some testing may be required. We want to avoid
major breaks in function of openSUSE 11.2.
--
Boyd Gerber
Hi, Dirk Müller wrote:
its time to start thinking about how we want to manage updates to openSUSE 11.2 when it is released. I think it is a good idea to incrementally open up the process of releasing updates to the community so that everybody can submit updates.
Yes that sounds like a good plan.
- there will be an externally accessible "simple" interface to SWAMP where anyone can submit a patchinfo (this has to be developed). Due to time constraints we can not open up the internal workflow tracking to the outside as no proper ACL support can be implemented in time for 11.2.
- package updates can be submitted against openSUSE:11.2:Update
Adrian 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?
- A group of openSUSE people (both community and Novell internal, I 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.
That should be simple. Is there anyone who would be interested in this?
- To ensure timely release of security updates, each devel group for 11.2 must contain at least one Novell employee. We can think about relaxing this for future openSUSE releases.
We don't have this rule for devel projects for factory. As maintenance for released products is is just another assignment for the devel projects i think we have to live without this. 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. 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. Opinions? :) Henne -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, 2009-08-13 at 15:41 +0200, Henne Vogelsang wrote:
Hi,
Dirk Müller wrote:
[...]
- A group of openSUSE people (both community and Novell internal, I 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.
That should be simple. Is there anyone who would be interested in this?
Count me in! :-) Cheers, Magnus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Aug 13, 2009 at 11:48:12PM +1000, Magnus Boman wrote:
On Thu, 2009-08-13 at 15:41 +0200, Henne Vogelsang wrote:
Hi,
Dirk Müller wrote:
[...]
- A group of openSUSE people (both community and Novell internal, I 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.
That should be simple. Is there anyone who would be interested in this?
Count me in! :-)
Me too... -- Best regards / s pozdravem Petr Uzel, openSUSE Community Multiplier Team ----------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: puzel@suse.cz Lihovarská 1060/12 http://www.suse.cz 190 00 Prague 9, CR
On Fri, Aug 14, 2009 at 4:46 AM, Petr Uzel
On Thu, Aug 13, 2009 at 11:48:12PM +1000, Magnus Boman wrote:
On Thu, 2009-08-13 at 15:41 +0200, Henne Vogelsang wrote:
Hi,
Dirk Müller wrote:
[...]
- A group of openSUSE people (both community and Novell internal, I 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.
That should be simple. Is there anyone who would be interested in this?
Count me in! :-)
Me too...
Count me in too. -- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday 13 August 2009, Henne Vogelsang wrote:
- package updates can be submitted against openSUSE:11.2:Update Adrian 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, I 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. That should be simple. Is there anyone who would be interested in this?
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.2 must contain at least one Novell employee. We can think about relaxing this for future openSUSE releases. We don't have this rule for devel projects for factory. As maintenance 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@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (6)
-
aledr -
Boyd Lynn Gerber -
Dirk Müller -
Henne Vogelsang -
Magnus Boman -
Petr Uzel