Daniel Shahaf wrote:
> kmradke_at_rockwellcollins.com wrote on Fri, 8 Aug 2008 at 16:59 -0500:
>> Karl Fogel <kfogel_at_red-bean.com> wrote on 08/08/2008 04:45:27 PM:
>>> "Kevin Radke" <kmradke_at_gmail.com> writes:
>>>> [[[
>>>> Add some guidelines about creating a custom release and include link
>>>> to trademark policy.
>>>>
>>>> *www/hacking.html
>>>> ]]]
>>> Kevin, the patch is all messed up (see quoted text below, which is
>>> exactly as I received it except for the "> " quotes along the left).
>>>
>>> Try re-attaching after tweaking your mailer in whatever way is
>>> necessary?
>> Hmm.... I just did an attach file with the gmail web interface. Figured
>> it would be much better than Notes at work... I'll resend with
>> thunderbird when I get home...
>>
>
> FWIW, the patch displays correctly here -- except for having MIME type
> of text/html. This just shows again how important the MIME type is,
> I suppose :)
Well, looks like the gmail web interface messed that up. Let's try
and see if Thunderbird gets it "right". (Notes at work actually
showed the old one fine too.)
I'm embarrassed I'm having problems with such a trivial patch...
Kevin R.
Index: www/hacking.html
===================================================================
--- www/hacking.html (revision 32408)
+++ www/hacking.html (working copy)
@@ -65,6 +65,7 @@
<li>Stabilizing and maintaining releases</li>
<li>Signing source distribution packages</li>
<li>Localization (l10n)</li>
+<li>Creating a custom release</li>
</ul>
</div>
@@ -2962,6 +2963,24 @@
>http://svn.collab.net/repos/svn/trunk/TRANSLATING</a> for more
information about translating.</p>
+<div class="h2" id="custom-releases" title="custom-releases">
+<h2>Creating a custom release</h2>
+<p>It is preferred to use the patch process and have your changes accepted
+and applied to trunk to be released on the normal Subversion release schedule.
+However, if you feel that you need to make changes that would not be
+widely accepted by the Subversion developer community or need
+to provide earlier custom releases, you should follow some guidelines.</p>
+
+<p>First, make sure you follow the <a
+href="http://subversion.org/legal/trademark-policy.html">
+Subversion trademark policy</a>. You will need to differentiate your release
+from the standard Subversion releases to reduce any potential confusion
+caused by your custom release.</p>
+
+<p>Second, consider creating a branch in the public subversion repository
+to track your changes and to potentially allow your custom changes to be
+merged into the normal Subversion functionality.</p>
+
</div>
</div>
---------------------------------------------------------------------
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-09 16:31:59 CEST