libxml v1 dependencies (was: Re: multilib fun - devel packages)

[Jeff Spaleta]

On 12/15/05, Jesse Keating <jkeating at j2solutions.net> wrote:
> Things have to change.  The question is do we do it now or later?
Sure do "it" now... the problem is "it" isnt pulling crap out of Core.
 "it" is changing the Extras policy and development model to make
maintaining Core+Extras release targets attractive and manageable for
volunteers to do.  Pulling functionality from Core now, before the
inftrastructure and policy that allows Core+Extras release targets to
be made is putting the cart before the horse.    If you start pulling
functionality out of Core now, to encourage people to maintain
Core+Extras release targets all you are going to do is frustrate your
potential volunteer release maintainers because they will be fighting
against the infrastructure.  You want Core+Extras release targets to
be a successful experiment then I suggest you lock yourself in a room
with the other Core release team members for a day and write down
exactly what is needed to make sure a release target is managable as
paid professionals, then ask what support would be needed if they were
volunteering spare time to maintain a release target.  At a minimum
"freeze" points in the tree(s) from which a release is built from has
to be there. Extras NEEDS "freeze" points or you are asking volunteers
to do the impossible.

Define what Core is suppose to be
Define what Extras is suppose to be
Define what the Core+Extras relationshiop is suppose to be
Build policies and infrastructure to support that relationship.
THEN start moving things around in the framework of that relatonship.

-jef