[calcite] branch site updated: Site: Add guidelines for JIRA's fix version field

[za...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

zabetak pushed a commit to branch site
in repository https://gitbox.apache.org/repos/asf/calcite.git


The following commit(s) were added to refs/heads/site by this push:
     new ffe62fc  Site: Add guidelines for JIRA's fix version field
ffe62fc is described below

commit ffe62fc86f54ffc9df4c1565d3d6062e8573fd05
Author: Stamatis Zampetakis <za...@gmail.com>
AuthorDate: Sun Mar 24 17:05:54 2019 +0100

    Site: Add guidelines for JIRA's fix version field
    
    Add guidelines for setting correctly the fix version field in JIRA, as discussed with Francis Chuang and Julian Hyde.
---
 site/develop/index.md | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/site/develop/index.md b/site/develop/index.md
index c708978..f754df9 100644
--- a/site/develop/index.md
+++ b/site/develop/index.md
@@ -67,6 +67,26 @@ helps to agree on the general approach. Log a
 [JIRA case](https://issues.apache.org/jira/browse/CALCITE) for your
 proposed feature or start a discussion on the dev list.
 
+Before opening up a new JIRA case, have a look in the existing issues.
+The feature or bug that you plan to work on may already be there.  
+
+If you are going to take on the issue right away assign it to yourself.
+To assign issues to yourself you have to be registered in JIRA as a contributor. 
+In order to do that, send an email to the developers list
+and provide your JIRA username.   
+
+If you are committed to fixing the issue before the upcoming release set 
+the fix version accordingly (e.g., 1.20.0), otherwise leave it as blank.
+
+If you pick up an existing issue, mark it 'in progress', and when it's 
+finished flag it with 'pull-request-available'. 
+
+If for any reason you decide that an issue cannot go into the ongoing
+release, reset the fix version to blank.
+
+During a release, the release manager will update the issues that were 
+not completed for the current release to the next release
+
 Fork the GitHub repository, and create a branch for your feature.
 
 Develop your feature and test cases, and make sure that