Proposal for customized builds (was Releasing 1.6)

Ok, I'll bite and start a new thread (as suggested by Karl)...

Some open source projects have documented guidelines on
releasing "customized builds" of their open source software.

In order to preserve the integrity of the Subversion name,
I suggest some rules be put in place to help people
continue the great tradition.

There doesn't appear to be anything in the hacking guide,
but I think this type of information would fit there.

* Creating customized builds of Subversion
We recommend that you first work with the Subversion
developers to see if the functionality you are adding
is acceptable for inclusion in the Subversion trunk
for future release. If it is, great! Submit a patch!

If you would like to release your changes as a customized
build before the next official release of Subversion, we
suggest you (TBD).... Things like create a branch, etc.

If your changes are fundamentally incompatible with the
future direction of Subversion as decided by a majority
of the Subversion developers, we suggest that your
customize build be appropriately renamed and future
development occur in a separate repository.

etc.

While open source is all about freedom, I do believe
it is reasonable to be able to restrict usage of the
name and versioning numbers in nonstandard releases...

Kevin R.

---------------------------------------------------------------------
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 19:01:57 CEST