ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #01268
Re: Writing good changelog entries
On Thu, Mar 21, 2013 at 02:19:59AM -0700, Robert Bruce Park wrote:
> On Thu, Mar 21, 2013 at 08:40:14AM +0000, Daniel Holbach wrote:
> > On 18.03.2013 14:54, Michał Sawicz wrote:
> > > Should essentially every MR be accompanied by a changelog entry? I'd
> > > like that, only we'll get conflicts on every merge request if something
> > > merged in trunk in the mean time :/
> >
> > I don't know how other teams like the Unity team are doing it. Does
> > anyone know?
>
> My understanding is that jenkins will create the changelog for you if
> you are set up for autolanding correctly. All you need to do is make
> sure there is a lp bug registered to track the work you're doing, and
> then when you submit the MP, set the commit message as "Fixes bug /
> implements some feature (LP: #nnnnnn)" and then when jenkins merges it
> for you, it will add the changelog entry for you.
This is valid for the daily release autolanding, in phablet there are
a couple of differences to land in the PPA.
Changelog entry atm is manual. If your series is UNRELEASED it won't dput
into the PPA and only merge (we used to have a staging PPA which was always
pushed to regardless). We also had a multiple series requirement that
happened automagically.
Once we move to pushing to distro archives and out of the PPA we will be
on our way to be more aligned with the former. That is, once _s_ is open.
Cheers,
Sergio
References