You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jonathan Gray (Created) (JIRA)" <ji...@apache.org> on 2011/10/15 02:58:11 UTC
[jira] [Created] (HBASE-4593) Design and document the official
procedure for posting patches, commits, commit messages, etc. to smooth
process and make integration with tools easier
Design and document the official procedure for posting patches, commits, commit messages, etc. to smooth process and make integration with tools easier
-------------------------------------------------------------------------------------------------------------------------------------------------------
Key: HBASE-4593
URL: https://issues.apache.org/jira/browse/HBASE-4593
Project: HBase
Issue Type: Task
Components: documentation
Reporter: Jonathan Gray
I have been building a tool (currently called reposync) to help me keep the internal FB hbase-92-based branch up-to-date with the public branches.
Various inconsistencies in our process has made it difficult to automate a lot of this stuff.
I'd like to work with everyone to come up with the official best practices and stick to it.
I welcome all suggestions. Among some of the things I'd like to nail down:
- Commit message format
- Best practice and commit message format for multiple commits
- Multiple commits per jira vs. jira per commit, what are the exceptions and when
- Affects vs. Fix versions
- Potential usage of [tags] in commit messages for things like book, scripts, shell... maybe even whatever is in the components field?
- Increased usage of JIRA tags or labels to mark exactly which repos a JIRA has been committed to (potentially even internal repos? ways for a tool to keep track in JIRA?)
We also need to be more strict about some things if we want to follow Apache guidelines. For example, all final versions of a patch must be attached to JIRA so that the author properly assigns it to Apache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4593) Design and document the official
procedure for posting patches, commits, commit messages, etc. to smooth
process and make integration with tools easier
Posted by "stack (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128075#comment-13128075 ]
stack commented on HBASE-4593:
------------------------------
Good stuff Jon. I started to make a response and then thought, back and forth on this should probably be out on the dev list? Want to start a thread?
> Design and document the official procedure for posting patches, commits, commit messages, etc. to smooth process and make integration with tools easier
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-4593
> URL: https://issues.apache.org/jira/browse/HBASE-4593
> Project: HBase
> Issue Type: Task
> Components: documentation
> Reporter: Jonathan Gray
>
> I have been building a tool (currently called reposync) to help me keep the internal FB hbase-92-based branch up-to-date with the public branches.
> Various inconsistencies in our process has made it difficult to automate a lot of this stuff.
> I'd like to work with everyone to come up with the official best practices and stick to it.
> I welcome all suggestions. Among some of the things I'd like to nail down:
> - Commit message format
> - Best practice and commit message format for multiple commits
> - Multiple commits per jira vs. jira per commit, what are the exceptions and when
> - Affects vs. Fix versions
> - Potential usage of [tags] in commit messages for things like book, scripts, shell... maybe even whatever is in the components field?
> - Increased usage of JIRA tags or labels to mark exactly which repos a JIRA has been committed to (potentially even internal repos? ways for a tool to keep track in JIRA?)
> We also need to be more strict about some things if we want to follow Apache guidelines. For example, all final versions of a patch must be attached to JIRA so that the author properly assigns it to Apache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-4593) Design and document the official
procedure for posting patches, commits, commit messages, etc. to smooth
process and make integration with tools easier
Posted by "Jonathan Gray (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128012#comment-13128012 ]
Jonathan Gray commented on HBASE-4593:
--------------------------------------
BTW, once we nail down the formatting and everything, I will toss reposync up on a github repo or something.
> Design and document the official procedure for posting patches, commits, commit messages, etc. to smooth process and make integration with tools easier
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-4593
> URL: https://issues.apache.org/jira/browse/HBASE-4593
> Project: HBase
> Issue Type: Task
> Components: documentation
> Reporter: Jonathan Gray
>
> I have been building a tool (currently called reposync) to help me keep the internal FB hbase-92-based branch up-to-date with the public branches.
> Various inconsistencies in our process has made it difficult to automate a lot of this stuff.
> I'd like to work with everyone to come up with the official best practices and stick to it.
> I welcome all suggestions. Among some of the things I'd like to nail down:
> - Commit message format
> - Best practice and commit message format for multiple commits
> - Multiple commits per jira vs. jira per commit, what are the exceptions and when
> - Affects vs. Fix versions
> - Potential usage of [tags] in commit messages for things like book, scripts, shell... maybe even whatever is in the components field?
> - Increased usage of JIRA tags or labels to mark exactly which repos a JIRA has been committed to (potentially even internal repos? ways for a tool to keep track in JIRA?)
> We also need to be more strict about some things if we want to follow Apache guidelines. For example, all final versions of a patch must be attached to JIRA so that the author properly assigns it to Apache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira