Where is the talloc repository?
abartlet at samba.org
Fri Mar 18 21:23:46 UTC 2016
On Fri, 2016-03-18 at 21:51 +0100, Andreas Schneider wrote:
> On Saturday 19 March 2016 08:29:33 Andrew Bartlett wrote:
> > On Tue, 2016-03-15 at 15:50 +0100, Michael Adam wrote:
> > > On 2016-03-15 at 10:45 +0100, Volker Lendecke wrote:
> > > > On Tue, Mar 15, 2016 at 10:15:46AM +0100, Michael Adam wrote:
> > > > > Don't get me wrong: I am more than willing to accept real
> > > > > arguments, but these don't really seem to click for me,
> > > > > since they don't my perception of reality and extrapolate
> > > > > from another case which is somewhat different.
> > > >
> > > > If a patch that is supposed to be merged to Samba siting in an
> > > > external
> > > > repo for 4 months without any activity is not an argument
> > > > showing
> > > > that
> > > > split repos are a bad idea, I don't know what you would accept
> > > > as
> > > > an
> > > > argument.
> > This much I really agree with.
> > > tl;dr?
> > > ==> summary: We've been there, and splitting out seems to create
> > > more problems that is solves.
> > >
> > > On the other hand side, what is the problem with external
> > > consumers like distro packagers?
> > >
> > > - According to Andreas, it happens that samba ran against
> > >
> > > unreleased talloc / libfoo code. But with the abi checks
> > > in place, how could this actually happen?
> > > ==> need a concrete example.
> > I actually think it is good that git master of Samba can run with
> > unreleased talloc/tdb/ldb changes. It isn't OK to release with
> > those,
> > but otherwise 'technically' we would have to do a core lib release
> > after every git commit, which just seems wrong.
> The problem are not unreleased talloc/tdb/ldb changes. The problem is
> version bump in the core libs and without a tarball release which
> means Samba
> requires a version which has not been released yet.
I agree that a Samba release should not be made containing unreleased
(version bumped or not) changes. We script our release process, a few
git commands should be able to check for that.
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
More information about the samba-technical