branch naming for stable security uploads

[Niko Tyni]

On Mon, Apr 16, 2018 at 02:00:09AM +0100, Dominic Hargreaves wrote:
> On Sun, Apr 15, 2018 at 10:34:35PM +0300, Niko Tyni wrote:

> > BTW I pushed the stable and oldstable updates to stretch and jessie
> > branch respectively, not stretch-security or jessie-security. Does that
> > matter? What's the use case for distinguishing between (for instance)
> > stretch vs. stretch-security ? Are there circumstances where they might
> > diverge?
> 
> If a security update comes out when a stable update is already in
> preparation it might be relevant. Otherwise, the use case is possibly
> just because I like the symmetry of preparing updates in a branch with
> the same name as the target distribution. It's one of those things
> which happens rarely enough that (and practices vary across different
> packages sets) that I would try and double check the relevant branches,
> so I don't think it hugely matters.

Makes sense, thanks. I think you convinced me enough that I'll use the
-security naming in the future (if I remember :)
-- 
Niko