(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)(cleanup) ->
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 :)
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
[email protected]
http://lists.meego.com/listinfo/meego-dev
