Mailinglist Archive: opensuse-factory (392 mails)
| < Previous | Next > |
Re: [opensuse-factory] RFC: Topics for 2007-04-19 dist meeting
- From: Andreas Jaeger <aj@xxxxxxx>
- Date: Thu, 19 Apr 2007 10:33:23 +0200
- Message-id: <ho1wig4vcc.fsf@xxxxxxxxxxxxx>
"Cristian Rodriguez R." <judas_iscariote@xxxxxxxxxxxxx> writes:
> Andreas Jaeger escribió:
>
>> * 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.
>>
>
> 1. The average user does not read package changelogs at all, probably
> they only read "patches" changelog if at all.
>
> 2. software provides NEWS and Changelog either included in the package
> or on the internet by their own. so it is absolutely pointeless to
> duplicate effort already done.
>
> 3. we provides **packages** of certain software, so the package
> changelog should include changes to the package **itself**. as stated
> previously there are counteless ways to retrieve software changes.(some
> poeple is even subscribed to announce lists of several software they use)
>
> 4. I have been told this is proposed to make autobuild people 's life
> easier,I wonder if autobuild people does not have a internet connection
> or a terminal to look at the NEWS file, the package can contain a link
> to the changelog.
>
> 5. Thsi unnecesarilly clutter changelog files with information that
> users **wont read**.
>
> 6. this cause unnecesarry work for packagers with no gain to users.
>
> In short, I would like to know the real rationale beahind this as I
> currently can see a single reason to do what is proposed.
I'm under the impression that end users want to know in an easy way why
the version update happened - and not only that it happened.
We currently copy some of that information also around, e.g. add it to
some announcements in a distilled way. I would like to see this
improved,
Andreas
--
Andreas Jaeger, aj@xxxxxxx, http://www.suse.de/~aj/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
> Andreas Jaeger escribió:
>
>> * 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.
>>
>
> 1. The average user does not read package changelogs at all, probably
> they only read "patches" changelog if at all.
>
> 2. software provides NEWS and Changelog either included in the package
> or on the internet by their own. so it is absolutely pointeless to
> duplicate effort already done.
>
> 3. we provides **packages** of certain software, so the package
> changelog should include changes to the package **itself**. as stated
> previously there are counteless ways to retrieve software changes.(some
> poeple is even subscribed to announce lists of several software they use)
>
> 4. I have been told this is proposed to make autobuild people 's life
> easier,I wonder if autobuild people does not have a internet connection
> or a terminal to look at the NEWS file, the package can contain a link
> to the changelog.
>
> 5. Thsi unnecesarilly clutter changelog files with information that
> users **wont read**.
>
> 6. this cause unnecesarry work for packagers with no gain to users.
>
> In short, I would like to know the real rationale beahind this as I
> currently can see a single reason to do what is proposed.
I'm under the impression that end users want to know in an easy way why
the version update happened - and not only that it happened.
We currently copy some of that information also around, e.g. add it to
some announcements in a distilled way. I would like to see this
improved,
Andreas
--
Andreas Jaeger, aj@xxxxxxx, http://www.suse.de/~aj/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
| < Previous | Next > |