Mailinglist Archive: opensuse-factory (753 mails)

< Previous Next >
Re: [opensuse-factory] Re: [opensuse-packaging] Packaging Guideline enforcement
On 08/31/2012 01:31 PM, Philipp Thomas wrote:
* Dominique Leuenberger a.k.a DimStar (DimStar@xxxxxxxxxxxx) [20120829 14:42]:

A simple "Update to version x.y.z" is, as before, not accepted.

What is when there is *no* nor no usable info in the package about the
changes? Perfect example are some of the packages that comprise OFED
(publicly accessible in OFED:Factory). It's nearly impossible to get
useful info on the changes and I will not try to scan a ChangeLog with the
detailed changes and try to condense them into something usefull.


If you can't figure out what's new - why do the update? ;)

Seriously, if you update and the update is a pile of many bugs, just say "Update to x.y.z, bugfix release.". In same cases it's just a version bump since all packages of a collection get updated, so say "version bump, no changes.". But if there are changes, highlight the one or two major ones. I'm sure there's an announcement out there that says something...

Most prominent is likely the mentioning of the patches life cycle,

The most usefull requirement would IMO be that patches were annotated as is
required for our kernels, i.e. a From line, date and and brief summary plus
the name and address of the person that added the patch.

That is one option, the PATCH-* description is a condensed form of that, e.g.:
# PATCH-FEATURE-OPENSUSE -- use separate symbol version for Owl extensions - lnussel@xxxxxxx

I'm fine with either option - I agree it's important to document it,

Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups