commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From st...@apache.org
Subject svn commit: r1750674 - /commons/proper/collections/trunk/CONTRIBUTING.md
Date Wed, 29 Jun 2016 16:59:39 GMT
Author: stain
Date: Wed Jun 29 16:59:39 2016
New Revision: 1750674

URL: http://svn.apache.org/viewvc?rev=1750674&view=rev
Log:
(doc) Avoid using VFS example

Modified:
    commons/proper/collections/trunk/CONTRIBUTING.md

Modified: commons/proper/collections/trunk/CONTRIBUTING.md
URL: http://svn.apache.org/viewvc/commons/proper/collections/trunk/CONTRIBUTING.md?rev=1750674&r1=1750673&r2=1750674&view=diff
==============================================================================
--- commons/proper/collections/trunk/CONTRIBUTING.md (original)
+++ commons/proper/collections/trunk/CONTRIBUTING.md Wed Jun 29 16:59:39 2016
@@ -62,11 +62,11 @@ Making Changes
 
 + Create a _topic branch_ for your isolated work.
   * Usually you should base your branch on the `master` or `trunk` branch.
-  * A good topic branch name can be the JIRA bug id plus a keyword, e.g. `VFS-614-MonitorInputStream`.
+  * A good topic branch name can be the JIRA bug id plus a keyword, e.g. `COLLECTIONS-123-InputStream`.
   * If you have submitted multiple JIRA issues, try to maintain separate branches and pull
requests.
 + Make commits of logical units.
   * Make sure your commit messages are meaningful and in the proper format. Your commit message
should contain the key of the JIRA issue.
-  * e.g. `VFS-614: Close input stream early`
+  * e.g. `COLLECTIONS-123: Close input stream earlier`
 + Respect the original code style:
   + Only use spaces for indentation.
   + Create minimal diffs - disable _On Save_ actions like _Reformat Source Code_ or _Organize
Imports_. If you feel the source code should be reformatted create a separate PR for this
change first.



Mime
View raw message