[ubuntu/raring-proposed] libunity-webapps 2.4.3daily12.11.29-0ubuntu1 (Accepted)

[Didier Roche]

Le 29/11/2012 16:37, Micah Gersten a écrit :
> On 11/29/2012 09:26 AM, Didier Roche wrote:
>> Le 29/11/2012 16:12, Micah Gersten a écrit :
>>> On 11/29/2012 04:45 AM, Ubuntu Archive Robot wrote:
>>>> libunity-webapps (2.4.3daily12.11.29-0ubuntu1) raring; urgency=low
>>>>
>>>>    * Automatic snapshot from revision 866
>>>>
>>>> Date: 2012-11-29 08:00:12.447090+00:00
>>>> Changed-By: PS Jenkins bot<ps-jenkins at lists.canonical.com>
>>>> Maintainer: Ubuntu Desktop<ubuntu-desktop at lists.ubuntu.com>
>>>> Signed-By: Ubuntu Archive Robot<cjwatson+ubuntu-archive-robot at chiark.greenend.org.uk>
>>>> https://launchpad.net/ubuntu/raring/+source/libunity-webapps/2.4.3daily12.11.29-0ubuntu1
>>>>
>>> Could we please have more verbose changelogs about what has changed than
>>> this?
>> Hey Micah,
>>
>> The changelog is generated from all the bugs attached to the branch 
>> from the developers. So, if the developers attached no bug to a 
>> branch and doesn't file the NEWS file, it will be empty, as you can 
>> see with most of the uploads we have in GNOME and others "New 
>> upstream release".
>>
>> When people are actually doing this, you get even more info than a 
>> simple upload you do manually, see for instance:
>>
>> https://lists.ubuntu.com/archives/raring-changes/2012-November/001547.html 
>> where you get the upstream committer name.
>>
> That's fine if it's a new upstream release as that means that someone 
> has manually signed off on it as a release containing new content 
> worth making a release for.  Here, as an automated process, I think 
> it's more problematic if there's no entry explaining why the upload 
> was done.  The commits might be rather useless and not really warrant 
> an upload.  It might be possible to refine the automation further to 
> skip such useless uploads.  I'm wondering, if there's no bug or NEWS 
> entry, if the bzr commit message should be used.

I tried as the first approach to use the commit message if no bug was 
attached, but the changelog did sound really noisy and I think that what 
we are really interested in are the bugs that are closed in an upload. 
You still have the debdiff if you want to have the full story of what's 
new inside (or the upstream vcs which is listed in debian/control). I 
think people interested enough in addition to the team monitoring those 
upstream projects can have a look there.

Cheers,
Didier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20121129/7b8f61b4/attachment.html>