You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by st...@apache.org on 2012/09/14 00:35:26 UTC
svn commit: r1384580 - /hbase/trunk/src/docbkx/community.xml
Author: stack
Date: Thu Sep 13 22:35:25 2012
New Revision: 1384580
URL: http://svn.apache.org/viewvc?rev=1384580&view=rev
Log:
Use link suggested by Otis
Modified:
hbase/trunk/src/docbkx/community.xml
Modified: hbase/trunk/src/docbkx/community.xml
URL: http://svn.apache.org/viewvc/hbase/trunk/src/docbkx/community.xml?rev=1384580&r1=1384579&r2=1384580&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/community.xml (original)
+++ hbase/trunk/src/docbkx/community.xml Thu Sep 13 22:35:25 2012
@@ -34,7 +34,7 @@
<para>Feature Branches are easy to make. You do not have to be a committer to make one. Just request the name of your branch be added to JIRA up on the
developer's mailing list and a committer will add it for you. Thereafter you can file issues against your feature branch in HBase JIRA. Your code you
keep elsewhere -- it should be public so it can be observed -- and you can update dev mailing list on progress. When the feature is ready for commit,
- 3 +1s from committers will get your feature merged<footnote><para>See <link xlink:href="http://search-hadoop.com/m/uPNz32C5FkS1&subj=Re+Thoughts+about+large+feature+dev+branches">HBase, mail # dev - Thoughts about large feature dev branches</link></para></footnote>
+ 3 +1s from committers will get your feature merged<footnote><para>See <link xlink:href="http://search-hadoop.com/m/asM982C5FkS1">HBase, mail # dev - Thoughts about large feature dev branches</link></para></footnote>
</para>
</section>
</section>