Folks, this entire thread is missing the point:
CollabNet is going to give special binaries to certain customers
*whether done from a branch in the public repos or not*. If there's no
branch in the public repos, then they'll maintain one privately, via SVK
or git-svn or whatever.
So discussing on dev@ whether or not CollabNet should do this, or how
they should do it, is purely advisory. CollabNet is free to do it, and
we cannot stop them -- IMHO we shouldn't want to stop them anyway --
just as anyone else is free to build and distribute custom binaries.
The question before us is whether there is benefit to the project in
having them do that from a branch in the repository (or, more properly,
in having certain committers maintain a branch in the repository from
which CollabNet will make some binaries).
_That_ is the topic under discussion.
Discussing whether or not a company should build custom binaries and
hand them out to certain customers is another topic, for another thread.
If we want to discuss that, let's please do it in a separate thread, and
keep in mind that whatever we say there is purely advisory. This is
open source software. Freedom, freedom, freedom :-). 'Nuff said.
(Yes, I think there's value in reminding those who distribute unusual
binaries that they need to be careful not to besmirch the good name of
the Subversion project. But CollabNet has done this before, and has an
excellent track record -- see Mike Pilato's reminder about the
merge-tracking early access program. We couldn't ask for better
evidence, really.)
+1 on option (1) from Stefan Sperling's excellent summary of the options
at http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=141654,
FWIW.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-08 18:27:21 CEST