Date: Sun, 3 Aug 1997 11:37:46 -0700 (PDT) From: Tom <tom@uniserve.com> To: Andreas Klemm <andreas@klemm.gtn.com> Cc: Chuck Robey <chuckr@glue.umd.edu>, ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Make this a relese coordinator decision (was Re: ports-current/packages-current discontinued) Message-ID: <Pine.BSF.3.96.970803113010.3843B-100000@shell.uniserve.com> In-Reply-To: <19970803122321.15396@klemm.gtn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 3 Aug 1997, Andreas Klemm wrote: ... > So he wanted only to support -stable in the future. But I think > this is a step behind. > Ports have to be buildable on -current and -stable, because : > a) -current is the next upcoming -stable release Really? Probably not. I expect that there will be a 2.2.5 or something out soon. > b) people like me, who have only one machine, usually > run the bleeding edge, I don't believe this is true. I believe true number of bleeding edge users is small. Unless your are a developer, there is little benefit. Other than SMP, what is in current that would tempt people to use it? People with only one machine are not normally technically advanced to run current, because they don't have the resources to develop that experience. ... > Figure out, if ports are only made for stable ... If -current > does more and more incompatible changes to -stable ... Who Key point here. Basically no one can stop developers from making current incompatible with stable. Basically, if current developers agree not to break compatibility, the problem goes away. Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970803113010.3843B-100000>