| Re: Re: [Users] OpenVZ kernel RPM changelog [message #8459 is a reply to message #8243] |
Mon, 20 November 2006 13:31   |
|
|
Dag Wieers wrote:
> Also I noticed that the ovz kernel had no internal changelog. I do
> understand that if it is based on the RHEL kernel, there is no real need
> to list the Red Hat changes. But having (fictitious) statements in the
> changelog like:
>
> * Sun Nov 12 OpenVZ kernel developer 2
> - Fixed a conditional kernel oops when <the shit hits the fan>
> - Improved locking in the <ultra-glue whoosy bits>
> - Fixed a security problem due to UBC counter overflow
>
> * Sat Nov 11 OpenVZ Kernel developer 1
> - Fixed bug M, BU Y and bug Z
> - Removed CONFIG_ABC and CONFIG_DEF
> - Based on RHEL4 kernel X.Y.Z
>
> would give a better understanding what we have in our hands. Especially if
> the versioning is not related to the upstream kernel. If we need to apply
> an update (and reboot the server) we prefer to know what the change/impact
> is and how important the update is.
>
We could automatically fetch that stuff from GIT and put it into
%changelog, if that's really required. But for me it looks like a
duplication of information (which is already available from other
place). More to say, the changelog could be rather big, with 100s of
entries.
Perhaps we could use short-style changelog, like this (for 028test005
kernel):
- FUSE support.
- Critical scheduler bug fixes
- Miscellaneous bug and compilation fixes
- Code cleanups.
So, which solution would you prefer?
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
