> -----Original Message----- > From: David Greaves [mailto:da...@dgreaves.com] > Sent: Sunday, June 27, 2010 6:38 PM > To: meego-packag...@meego.com; MeeGo-dev@meego.com > Cc: Zhu, Peter J; mmeeks > Subject: Changelog formatting (was Re: [meego-packaging] 4899: Changes to > MeeGo:1.0:Netbook:Update:Testing/evolution ACCEPTED) > > (note cross-posting - I don't think all devs are on meego-packaging) > > Just picking on this as a typical example: > > On 27/06/10 09:45, Peter Zhu wrote: > > submit: > home:mmeeks:branches:MeeGo:1.0:Netbook:Update:Testing/evolution(r8)(cle > anup) -> > MeeGo:1.0:Netbook:Update:Testing/evolution > > > > > > Message: > > fix bugs 2393, 1704, 1104 > > One of the things being worked on is tracking and automating activity through > release reporting. > > http://meego.gitorious.org/meego-infrastructure-tools/revs > http://meego.gitorious.org/meego-infrastructure-tools/boss > > The changelog is the canonical source for this information which of course > means > we're going to have to parse them. > > So, can we make an effort to agree (and use!) a consistent style for changelog > entries related to MeeGo (and associated) originated entries. > > http://wiki.meego.com/Packaging/Guidelines#Changelogs > (comments welcome) > > We're working on validation tools that will be integrated into the automation > and will alert you to any transgressions :) > Cool. I compared this with guideline and seem only missing or inconsistent parts are a missing dash "-" between mail and version.
Actually we have another tool of vc, that's part of packagint-tools, to automatically to insert a new changelog entry into changesfile. > Until that arrives we'd appreciate both developer and release-engineering > support in keeping to the guidelines manually. > > Thanks. > > David > > -- > "Don't worry, you'll be fine; I saw it work in a cartoon once..." _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
