Paul Armstrong wrote: >> James Carlson wrote: >>> Having "X.Y.Z" release numbers is one way to handle the problem, but >>> there might be others. I don't much care how it gets done, so long as >>> the documentation of the content is clear and understandable. >>> >> We've been talking about exactly such versioning of >> packages... this >> will become clearer when we get an approved project >> and the docs and >> source become available. > > To do this properly, it would seem that we need to have several branches of > patches/packages. > > If we have an x.y.z patch numbering and z means only bug fixes, then is the > proposal to have package trains for each update so customers who need > security patches don't have to pull features? > > Along these lines, if I install 11_U2 when it comes out, with say > SUNWpkgcmdsu version 12.1.0 then I can expect updates to the z number but > updates on the y only if I upgrade to 11_U3 and x only if I upgrade to 12FCS > or newer. > > This would take more work on the part of Sun and others doing packaging, but > provide more stability to administrators. > > Paul >
Exactly such ideas are under discussion.... the idea is that the new technologies will allow Sun to much more easily deliver multiple streams of change, rather than forcing everyone to pick and choose from a single one. - Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts
