Mailinglist Archive: opensuse-gnome (124 mails)
| < Previous | Next > |
Re: [opensuse-gnome] To Changelog or to not Changelog
- From: Luis Medinas <lmedinas@xxxxxxxxx>
- Date: Fri, 30 Jan 2009 01:07:47 +0000
- Message-id: <1233277667.4208.5.camel@fermi>
On Fri, 2009-01-30 at 12:02 +1100, Magnus Boman wrote:
team maintaining all packages(everyone can bump a pkg) it's useful to
know what changed from a release to another, specially what dirty hacks,
workarounds and dependencies were remove along with new features
introduced that might not be enabled. Also it keeps easier to keep
tracking bugs on upstream -> bnc.
Luis
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-gnome+help@xxxxxxxxxxxx
Hello,My opinion is that we should stick with the current policy, since is the
Currently, when doing package updates, we have some (strange) policy
that we have to put in what changes upstream made (ie, bugfixes, new
features etc).
All this information is already available in the NEWS/ChangeLog file for
most packages.
Since this doesn't seem to be an openSUSE policy [1] I wonder why we
enforce this for GNOME components?
Enforcing updates of the changelog makes it possible to check details of
upstream changes with;
# rpm -q --changelog nautilus
By not enforcing these changes, one can do;
# cat /usr/share/doc/packages/nautilus/NEWS
I see little (if any) value in doing this, but it adds a lot of time
when doing a package update, so I would like to change the policy to
simple contain specific updates that the packager made (add/remove patch
etc)
Opinions?
team maintaining all packages(everyone can bump a pkg) it's useful to
know what changed from a release to another, specially what dirty hacks,
workarounds and dependencies were remove along with new features
introduced that might not be enabled. Also it keeps easier to keep
tracking bugs on upstream -> bnc.
Luis
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-gnome+help@xxxxxxxxxxxx
| < Previous | Next > |