Updates System

[Jesse Keating]

On Wednesday 16 May 2007 10:06:08 Ralf Corsepius wrote:
> Where is this documented? URL?

I don't know if it's documented yet.  I know that the previous incarnation of 
this that is used internally for Core updates allows for this, and that the 
new incarnation of it would too.

> > > 0) maintainer tests package's  functionality.
> > >
> > > > 1) Maintainer checks changes into CVS branch.
> > > > 2) Maintainer builds.
> > > > 3) Maintainer tests that build.
> > > > 4) Maintainer fills out the form with the N-V-R, optional security
> > > > (yes/no), optional Bug numbers fixed, and some fills in some details
> > > > of what the update is about, then chooses updates or updates-testing.
> > > > 5) Submit, where security and/or rel-eng team pushes it through.
> > >
> > > Now where in this scheme is Will Woods? I don't see him testing
> > > anything. All I see is more bureaucracy and more manual steps than
> > > before.
> >
> > Perhaps this is where we're not communicating clearly enough.  Will isn't
> > going to be doing (all) the testing himself.  However Will is going to be
> > driving a QA team and anybody else who is interested to make use of the
> > public updates-testing repo.
>
> I still fail to understand what he does and how a community package is
> supposed to profit from this.
>
> What does he do, what a "package consistency checker" can't and what
> can't be achieved by having a repo containing packages?

http://fedoraproject.org/wiki/WillWoods

-- 
Jesse Keating
Release Engineer: Fedora
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-maintainers/attachments/20070516/dd590cb2/attachment.sig>