Date: Tue, 05 Jun 2007 15:54:25 -0700 From: Doug Barton <dougb@FreeBSD.org> To: "Timur I. Bakeyev" <timur@gnu.org> Cc: Andrea Venturoli <ml.diespammer@netfence.it>, spil.oss@gmail.com, freebsd-ports@freebsd.org Subject: Re: [net/samba3] Upgrade to Samba 3.0.25a Message-ID: <4665E9A1.2030402@FreeBSD.org> In-Reply-To: <20070605124644.GD22215@com.bat.ru> References: <5fbf03c20706050031p6f25d02cyae7a91593e40171a@mail.gmail.com> <20070605082244.GB22215@com.bat.ru> <46652DEF.1070709@netfence.it> <20070605124644.GD22215@com.bat.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Timur I. Bakeyev wrote:
> Unfortunately, Samba3 became so big and hairy, that fixing one problem
> there creates few new. So, for the last ~10 releases this was pretty
> common situation when erratra release was following very quickly.
I think it's very reasonable, and well in keeping with FreeBSD
tradition, to delay upgrading to a new release of ported software
until the maintainer is convinced that it's safe to do so. I have
taken the same approach with the BIND ports, and actually went so far
as to place a comment in the Makefiles to try and stem the tide of
requests for instant upgrades to new releases.
As a samba user, I appreciate you giving these issues careful
consideration, and your looking out for the best interests of our
userbase.
Regards,
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4665E9A1.2030402>