[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772094#comment-13772094 ] Aleksandr Shulman commented on HBASE-9153: -- Looks like it's not going in smoothly in a few places. What can I do to help? Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0, 0.94.13 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771272#comment-13771272 ] Nick Dimiduk commented on HBASE-9153: - Committed Aleks's tool to trunk and 96. Will hold off on resolving until Lars has his say. [~aleksshulman] would you mind adding a release note? [~jmhsieh] I've updated the ticket title to reflect the work done here. You may want to open a new one for your original intention. Thanks Aleks! Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771274#comment-13771274 ] stack commented on HBASE-9153: -- +1 for trunk and 0.96 I can add doc to book from script head once committed. Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771278#comment-13771278 ] Jonathan Hsieh commented on HBASE-9153: --- thanks for committing nick, a little slow these days. Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771283#comment-13771283 ] Aleksandr Shulman commented on HBASE-9153: -- Hey Nick, thanks for the commit. In terms of release note, here is what I propose: Added a tool to generate a report of API compatibility between different versions of hbase. It is found in dev-support and uses JDiff under the covers. Usage info at the top of the script. I'm not sure if this is exactly what you're looking for, but we can adjust as necessary. Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771285#comment-13771285 ] Nick Dimiduk commented on HBASE-9153: - [~stack] sounds like a plan. [~jmhsieh] we all have our days (and weeks, and ...) *smile* Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771289#comment-13771289 ] Nick Dimiduk commented on HBASE-9153: - [~aleksshulman] That sounds perfect. Maybe stack and add the link to the site once he get the docbook changes committed. Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771351#comment-13771351 ] Lars Hofhansl commented on HBASE-9153: -- 0.94... Sure. It's all new and only in dev-support. Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771361#comment-13771361 ] Hudson commented on HBASE-9153: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #739 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/739/]) HBASE-9153: Introduce/update a script to generate jdiff reports (ndimiduk: rev 1524585) * /hbase/trunk/dev-support/hbase_jdiff_acrossSingularityTemplate.xml * /hbase/trunk/dev-support/hbase_jdiff_afterSingularityTemplate.xml * /hbase/trunk/dev-support/hbase_jdiff_template.xml * /hbase/trunk/dev-support/jdiffHBaseFromGitRepos.sh * /hbase/trunk/dev-support/jdiffHBasePublicAPI.sh * /hbase/trunk/dev-support/jdiffHBasePublicAPI_common.sh Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771372#comment-13771372 ] Nick Dimiduk commented on HBASE-9153: - Committed to 0.94. I think this missed your RC, right [~lhofhansl]? Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0, 0.94.13 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771416#comment-13771416 ] Hudson commented on HBASE-9153: --- SUCCESS: Integrated in HBase-0.94-security #296 (See [https://builds.apache.org/job/HBase-0.94-security/296/]) HBASE-9153: Introduce/update a script to generate jdiff reports (ndimiduk: rev 1524599) * /hbase/branches/0.94/dev-support/hbase_jdiff_acrossSingularityTemplate.xml * /hbase/branches/0.94/dev-support/hbase_jdiff_afterSingularityTemplate.xml * /hbase/branches/0.94/dev-support/hbase_jdiff_template.xml * /hbase/branches/0.94/dev-support/jdiffHBasePublicAPI.sh * /hbase/branches/0.94/dev-support/jdiffHBasePublicAPI_common.sh Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0, 0.94.13 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771448#comment-13771448 ] Hudson commented on HBASE-9153: --- FAILURE: Integrated in hbase-0.96-hadoop2 #37 (See [https://builds.apache.org/job/hbase-0.96-hadoop2/37/]) HBASE-9153: Introduce/update a script to generate jdiff reports (ndimiduk: rev 1524586) * /hbase/branches/0.96/dev-support/hbase_jdiff_acrossSingularityTemplate.xml * /hbase/branches/0.96/dev-support/hbase_jdiff_afterSingularityTemplate.xml * /hbase/branches/0.96/dev-support/hbase_jdiff_template.xml * /hbase/branches/0.96/dev-support/jdiffHBasePublicAPI.sh * /hbase/branches/0.96/dev-support/jdiffHBasePublicAPI_common.sh Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0, 0.94.13 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771466#comment-13771466 ] Hudson commented on HBASE-9153: --- FAILURE: Integrated in HBase-TRUNK #4530 (See [https://builds.apache.org/job/HBase-TRUNK/4530/]) HBASE-9153: Introduce/update a script to generate jdiff reports (ndimiduk: rev 1524585) * /hbase/trunk/dev-support/hbase_jdiff_acrossSingularityTemplate.xml * /hbase/trunk/dev-support/hbase_jdiff_afterSingularityTemplate.xml * /hbase/trunk/dev-support/hbase_jdiff_template.xml * /hbase/trunk/dev-support/jdiffHBaseFromGitRepos.sh * /hbase/trunk/dev-support/jdiffHBasePublicAPI.sh * /hbase/trunk/dev-support/jdiffHBasePublicAPI_common.sh Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0, 0.94.13 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771471#comment-13771471 ] Hudson commented on HBASE-9153: --- FAILURE: Integrated in HBase-0.94 #1153 (See [https://builds.apache.org/job/HBase-0.94/1153/]) HBASE-9153: Introduce/update a script to generate jdiff reports (ndimiduk: rev 1524599) * /hbase/branches/0.94/dev-support/hbase_jdiff_acrossSingularityTemplate.xml * /hbase/branches/0.94/dev-support/hbase_jdiff_afterSingularityTemplate.xml * /hbase/branches/0.94/dev-support/hbase_jdiff_template.xml * /hbase/branches/0.94/dev-support/jdiffHBasePublicAPI.sh * /hbase/branches/0.94/dev-support/jdiffHBasePublicAPI_common.sh Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0, 0.94.13 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771510#comment-13771510 ] Hudson commented on HBASE-9153: --- FAILURE: Integrated in hbase-0.96 #69 (See [https://builds.apache.org/job/hbase-0.96/69/]) HBASE-9153: Introduce/update a script to generate jdiff reports (ndimiduk: rev 1524586) * /hbase/branches/0.96/dev-support/hbase_jdiff_acrossSingularityTemplate.xml * /hbase/branches/0.96/dev-support/hbase_jdiff_afterSingularityTemplate.xml * /hbase/branches/0.96/dev-support/hbase_jdiff_template.xml * /hbase/branches/0.96/dev-support/jdiffHBasePublicAPI.sh * /hbase/branches/0.96/dev-support/jdiffHBasePublicAPI_common.sh Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0, 0.94.13 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9153) Introduce/update a script to generate jdiff reports
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771560#comment-13771560 ] Lars Hofhansl commented on HBASE-9153: -- Yeah it did. Just means it's in 3-4 weeks. :) Introduce/update a script to generate jdiff reports --- Key: HBASE-9153 URL: https://issues.apache.org/jira/browse/HBASE-9153 Project: HBase Issue Type: Task Reporter: Jonathan Hsieh Assignee: Aleksandr Shulman Fix For: 0.98.0, 0.96.0, 0.94.13 Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch, HBASE-9153-v4-0.94.patch, HBASE-9153-v4-0.95.patch, HBASE-9153-v4-trunk.patch, HBASE-9153-v5-0.94.patch, HBASE-9153-v5-0.95.patch, HBASE-9153-v5-trunk.patch, HBASE-9153-v6-0.94.patch, HBASE-9153-v6-0.95.patch, HBASE-9153-v6-trunk.patch We've had a few issues now where we've removed API's without deprecating or deprecating in the late release. (HBASE-9142, HBASE-9093) We should just have a tool that enforces our api deprecation policy as a release time check or as a precommit check. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
