[Pkg-samba-maint] (forw) [Announce] Samba 3.6.7 Available for Download

Christian PERRIER bubulle at debian.org
Tue Aug 7 06:12:57 UTC 2012


Quoting Ivo De Decker (ivo.dedecker at ugent.be):

> Are there specific fixes you think we should try to 'backport'?

Hard to say. We don't have specific bugs that I know about which are
fixed by this release. But, of course, nearly all fixed bugs
potentially  affect our users. And, of the Samba Team is fairly
conservative in their stable branch, I think that, in theory, most bug
fixes mentioned in the annoucement would deserve to be fixed by us

> 
> > I really would like bt I think that, in some way, our release policy isn't
> > really great...because I'm 101% sure that 3.6.7 is by far an improvement
> > over 3.6.6
> 
> Well, I think it's impossible for the release team to start giving broad
> exceptions to some packages and not to others...

I have the weaknes to think that some credit could be given to
"trustable" maintenance teams(and here I include upstreams). And I
have the weakness to think that we (Debian samba maintainers plus the
Samba Team) are exactly this.

But, I agree this is hard to scale.

So we're left with the choice of either wait for users bug reports or
anticipate them by going through fixed bugs one by one and make our
decision on each of them

> 
> > Anyway, I'm considering to upload this 3.6.7 release to experimental.
> > 
> > In our VCS, we have two options:
> > 
> > - branch the trunk as experimental and do 3.6.7 work there
> > - branch the trunk as wheezy (which we'll do at some point anyway) and
> > work on experimental in the trunk
> > 
> > Advices?
> 
> I think using an 'experimental' branch for packages in experimental is the
> best way. But I don't really feel that strongly about it.


My only concern is that this is the method I used during the squeeze
freeze and I had to manage some very painful merges.

Particularly, the *current* experimental branch is a leftover of the
last version we uploaded to experimental (3.6.1-1), which means a
quite painful merge, probably. An alternative is of course dropping
entirely the current experimental branch and start one from
scratch. Indeed the new experimental branch has nothing to do with the
current one.

I really start to be missing git now that I'm more and more
comfortable with it..:-)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-samba-maint/attachments/20120807/0dd1c6d8/attachment.pgp>


More information about the Pkg-samba-maint mailing list