Jason Chu wrote: >On Thu, Nov 17, 2005 at 09:56:47AM -0800, Doug Jolley wrote: > > >> Well, I've been playing with Arch Linux for about 2 months now and I >> certainly like what I'm seeing. For my own workstation, it's great. >> However, I'm now thinking about moving on and actually using Arch in >> some production installations. In that regard, I have some questions >> about how the rolling release system works. >> Hypothetically, let's say that the latest released version is 'Yawn' >> and the next version to be released is 'BleedingEdge'. So, put >> differently, BleedingEdge is currently under development and >> development work has been completed on Yawn. As the development work >> is proceeding on BleedingEdge, does Yawn receive security updates and >> bug fixes? If so, how long does this policy of providing security >> updates and bug fixes to Yawn continue? >> Thanks for any input. >> ... doug >> >> > >I know lots of other people will jump on this, but I wanted to as well... > >What you've described is more of a frozen release system. Multiple >branches moving forward at the same time. > >Our release structure isn't like that at all. We just take a snapshot of >the state of current and that's a release. The rolling part means that the >difference between releases is all the updates we've done. > >A release is out of date seconds after it's been made. We don't touch it >after that. > >Jason > > Well, I agree with Jason mostly but as I have been using Arch for almost 2 years now, I've seen some packages receiving security updates without the complete re-release of a development version. As you might have noticed in Firefox's PKGBUILD many patches are applied for security reasons. These might of course have been fixed already in the CVS or wherever but there hasn't been a release yet. To sum up, security fixes are only aplied if there's not a later released that has them already fixed and severeity is hight enough.
I'm certain about what I just said but hey, I could have missed out on something. :) Cheers! Alex / kth5 _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
