On Sat, May 15, 2004 at 01:16:09AM -0400, Kevin Mark wrote: > On Fri, May 14, 2004 at 09:50:00PM -0600, s. keeling wrote: > > I imagine there are cases in which this approach won't work, but we > > see the same thing from people everyday who are limiting themselves > > to only using debian tools. Just look at that stable vs. testing > > vs. unstable thread a month ago. > > > > And that's possibly the worst news the original poster wants to > > hear; he's got to make his stuff work on stable, testing, and > > unstable?!? Gah! > > Hi S, > one doesnt make a product 'work' for stable, testing or unstable. > every package start out it life as an unstable package. And if it > proves its stability it will get moved to testing. And then if all > goes well, it moves into stable. its stability and interaction with > other packages are the criteria that the debian packager of an authors > work uses to judge when it is moved to the next phase of readyness for > 'stable'.
That applies to Debian packages, but not to third-party products being ported to Debian. The usual approach for those is to build for stable and deal with other problems if and when they arise. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
