unity-dev team mailing list archive

[Didier Roche <didrocks@xxxxxxxxxx>]

Le 09/01/2013 03:35, Daniel van Vugt a écrit :
> That's only true for the project "Unity". Yes if your commit was 
> correctly flagged as "--fixes lp:N" then Launchpad will automatically 
> set Fix Committed in "Unity" for you. But it will not update "unity 
> (Ubuntu)" automatically. You need to do that by hand.

Under normal circumstances (so when the automated daily release is up), 
those are collected and triaged by authors to populate debian/changelog. 
So, if the tests pass, the package is uploaded in ubuntu and so, the 
unity (ubuntu) bug tasks and all * (ubuntu) tasks will be marked as fix 
released automatically. To sum up, you don't need to do that :)

Cheers,
Didier

> On 09/01/13 10:30, Stephen M. Webb wrote:
> > On 01/08/2013 09:13 PM, Daniel van Vugt wrote:
> > > And now for something less contentious :)
> > >
> > > Please note that lp:unity (and other projects) now have in-line 
> > > packaging (that debian/ directory). So when a bug is
> > > marked as Fix Committed in "Unity" you probably should also set it 
> > > to Fix Committed in "unity (Ubuntu)" too. And of
> > > course, please remember to flag the milestone for lp:unity fixes as 
> > > 7.0.0. Otherwise fixes can get forgotten and never
> > > mentioned/updated when the release happens.
> >
> > These should be marked as Fixed Committed when the change lands in 
> > unity (Ubuntu) as long as the bug number is mentioned
> > in a commit message somewhere.  I would prefer the commit message in 
> > MP, since that shows up in the trunk.
> >
> > Changes are not autolanding in Ubuntu at the moment, so the bugs are 
> > not getting marked as closed.  Hopefully the
> > autolanding will start in the next few days as the autopilot tests 
> > get pummeled into shape.
> >
> > You should not have to mark any of the bug tasks to Fix Committed or 
> > Fix Released manually under normal circumstances.