[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: release policy text changes

* Steve Langasek (vorlon@debian.org) [050620 11:43]:
> On Sun, Jun 19, 2005 at 05:15:39PM +0200, Andreas Barth wrote:
> >   (p) Linux Standard Base
> > 
> >         Packages must not conflict with requirements of the LSB,
> >         v1.3. (eg, if you provide a library specified in the LSB, you
> >         must be compatible with the LSB specification of that library)
> > 
> >         Basically, you should be LSB compatible. You can expect a bug
> >         report to be filed if you're not, and if you don't know how to
> >         fix the problem, you should email debian-lsb@lists.debian.org
> >         for assistance.
> > 
> >         {+[Expect that the LSB Version will be bumped to 3 during etch
> >         development.]+}
> Perhaps we should be making this decision so that this isn't left as a
> footnote.  Maintainers need to know which version they're targetting, since
> they're not compatible.

Agreed. This footnote was IMHO just there to remind us to do the
decision, and shouldn't last longer than 3 weeks or so. :)

> >   (q) Python
> > 
> >         Packages providing python modules must comply with the python
> >         policy (naming scheme and dependencies). See 
> >         http://people.debian.org/~joss/python/python-policy-draft.txt
> > 
> >         {+[Expect that the python policy and implementation will change
> >         during the etch development cycle]+}
> Again, I'm not sure why we want to write that in the rc checklist.

Because IMHO the RC checklist is one of the first things we need to
finalize for the release, so that people know what they're supposed to
work to. For that reason, I wanted to mark the two outstanding issues
(in the hope that all places where a change will happen are marked now).

But well, never mind. (About the other changes: I commited them as
proposed by you now.)


Reply to: