Where is the talloc repository?

Andreas Schneider asn at samba.org
Mon Mar 14 12:38:01 UTC 2016

On Monday 14 March 2016 12:47:47 Michael Adam wrote:
> I think we need to communicate this more clearly:
> - The wrappers' upstream is the samba team.
> - Push rights are with the team.
> - This in principle includes doing releases, even though
>   de facto up to now usually Andreas has done them
>   (I think I did 1 or 2).
> The purpose in taking wrappers out of the main samba tree is
> NOT to reduce the control of the samba team over the code.
> And it is NOT to make the life of samba developers more
> miserable. But to more clearly separate the doing and place of
> the release processes and the version numbering. This makes
> everyhing more more explicit and more obvious for external
> consumers.

Thanks for the clarification. I've also added a doc to the team repository 
which some documentation for this and the process.

> The same holds for he proposed move of talloc/tevent
> to its own git.
> As Andreas wrote, the problem becomes more apparent
> when e.g. packaging samba+tevent+talloc+wrappers (etc)
> for a distribution. So the goal is to make the life
> of the distributors and other external consumers more easy,
> while NOT making the life of samba developers more miserable!
> With respect to the proposal to move talloc / tevent to
> their own git repo, I think we would need to talk more
> explicitly about (and document) the release and commit
> process for talloc / tevent etc. We'd want to put up an
> autobuild process for these. And need to decide what the
> commit policy will be and who will be release maintainer
> for these. And whether there will be branches. Etc.

Yes, this is also what I thought about. It is currently hard to follow 
development if you do not read the complete samba commit history.

Also we had a really hard time doing backports in the past.

It would be easier for people who are interested in talloc development but not 
Samba development to follow the project. It would be easier for distributions 
to do backports.

Also I would see it easier to push talloc patches. Running the talloc 
testsuites doesn't take 2 hours ;) Well assuming that the testsuite gives 
enough coverage. If not it should be extended.


	-- andreas

Andreas Schneider                   GPG-ID: CC014E3D
Samba Team                             asn at samba.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20160314/c16e9e5a/signature.sig>

More information about the samba-technical mailing list