Mailinglist Archive: opensuse-factory (392 mails)
| < Previous | Next > |
Re: [opensuse-factory] RFC: Topics for 2007-04-19 dist meeting
- From: Richard Bos <ml@xxxxxxxxxx>
- Date: Wed, 18 Apr 2007 21:20:09 +0200
- Message-id: <200704182120.09610.ml@xxxxxxxxxx>
Op Wednesday 18 April 2007 20:10:05 schreef Andreas Jaeger:
> * log entries in .changes file
>
> Just a simple "Update to version x.y" is not valid in the packages
> changelog but happens far too often.
>
> Goal: present the changes done to packages to users in a good way and
> use that for e.g. Release Notes.
I can't be in the meeting tomorrow:
- How to differentiate between updates to the spec file and the
package/project? Or is this not important for the end user? As an example,
just recently I did an mass update to the gnome related project (due to the
prefix change). At the end this is not important to the end user, but for
other packagers it is!
However, at the same time I splitted the package into language dependend parts
and that's important for the end user.
Should there perhaps be 2 changelogs? A project changelog and a spec file
changelog?
I must admit I'm on side that a package version is sufficient to mention in
the spec file, as that all there is that changed. But now that the changelog
is presented on the web it is indeed interesting to provide the project
changelog for the end user. But in this case it might be sufficient to
provide a link to the (official/native) project changelog that is most likely
on the web in the rpm changelog...
--
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
> * log entries in .changes file
>
> Just a simple "Update to version x.y" is not valid in the packages
> changelog but happens far too often.
>
> Goal: present the changes done to packages to users in a good way and
> use that for e.g. Release Notes.
I can't be in the meeting tomorrow:
- How to differentiate between updates to the spec file and the
package/project? Or is this not important for the end user? As an example,
just recently I did an mass update to the gnome related project (due to the
prefix change). At the end this is not important to the end user, but for
other packagers it is!
However, at the same time I splitted the package into language dependend parts
and that's important for the end user.
Should there perhaps be 2 changelogs? A project changelog and a spec file
changelog?
I must admit I'm on side that a package version is sufficient to mention in
the spec file, as that all there is that changed. But now that the changelog
is presented on the web it is indeed interesting to provide the project
changelog for the end user. But in this case it might be sufficient to
provide a link to the (official/native) project changelog that is most likely
on the web in the rpm changelog...
--
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |