HBASE-22497 Mark HBase 1.2 line as EOM

Signed-off-by: Duo Zhang <zhangduo@apache.org>
This commit is contained in:
Sean Busbey 2019-05-31 19:51:20 -05:00
parent 073de44445
commit 51c49a1784
7 changed files with 10 additions and 40 deletions

View File

@ -32,7 +32,7 @@
# --annotation org.apache.yetus.audience.InterfaceAudience.LimitedPrivate \ # --annotation org.apache.yetus.audience.InterfaceAudience.LimitedPrivate \
# --include-file "hbase-*" \ # --include-file "hbase-*" \
# --known_problems_path ~/known_problems.json \ # --known_problems_path ~/known_problems.json \
# rel/1.0.0 branch-1.2 # rel/1.3.0 branch-1.4
import json import json
import logging import logging
@ -325,14 +325,14 @@ def get_known_problems(json_path, src_rev, dst_rev):
keys in the format source_branch/destination_branch and the values keys in the format source_branch/destination_branch and the values
dictionaries with binary and source problems and warnings dictionaries with binary and source problems and warnings
Example: Example:
{'branch-1.0.0': { {'branch-1.3': {
'rel/1.0.0': {'binary': {'problems': 123, 'warnings': 16}, 'rel/1.3.0': {'binary': {'problems': 123, 'warnings': 16},
'source': {'problems': 167, 'warnings': 1}}, 'source': {'problems': 167, 'warnings': 1}},
'branch-1.2.0': {'binary': {'problems': 0, 'warnings': 0}, 'branch-1.4': {'binary': {'problems': 0, 'warnings': 0},
'source': {'problems': 0, 'warnings': 0}} 'source': {'problems': 0, 'warnings': 0}}
}, },
'branch-1.2.0': { 'branch-1.4': {
'rel/1.2.1': {'binary': {'problems': 13, 'warnings': 1}, 'rel/1.4.1': {'binary': {'problems': 13, 'warnings': 1},
'source': {'problems': 23, 'warnings': 0}} 'source': {'problems': 23, 'warnings': 0}}
} }
} """ } """

View File

@ -135,7 +135,7 @@ public class VersionInfo {
/** /**
* Returns the version components as String objects * Returns the version components as String objects
* Examples: "1.2.3" returns ["1", "2", "3"], "4.5.6-SNAPSHOT" returns ["4", "5", "6", "-1"] * Examples: "1.4.3" returns ["1", "4", "3"], "4.5.6-SNAPSHOT" returns ["4", "5", "6", "-1"]
* "4.5.6-beta" returns ["4", "5", "6", "-2"], "4.5.6-alpha" returns ["4", "5", "6", "-3"] * "4.5.6-beta" returns ["4", "5", "6", "-2"], "4.5.6-alpha" returns ["4", "5", "6", "-3"]
* "4.5.6-UNKNOW" returns ["4", "5", "6", "-4"] * "4.5.6-UNKNOW" returns ["4", "5", "6", "-4"]
* @return the components of the version string * @return the components of the version string

View File

@ -148,7 +148,7 @@ public final class VersionInfoUtil {
/** /**
* Returns the version components * Returns the version components
* Examples: "1.2.3" returns [1, 2, 3], "4.5.6-SNAPSHOT" returns [4, 5, 6, "SNAPSHOT"] * Examples: "1.4.3" returns [1, 4, 3], "4.5.6-SNAPSHOT" returns [4, 5, 6, "SNAPSHOT"]
* @returns the components of the version string * @returns the components of the version string
*/ */
private static String[] getVersionComponents(final HBaseProtos.VersionInfo versionInfo) { private static String[] getVersionComponents(final HBaseProtos.VersionInfo versionInfo) {

View File

@ -82,9 +82,6 @@ NOTE: End-of-life releases are not included in this list.
| Release | Release
| Release Manager | Release Manager
| 1.2
| Sean Busbey
| 1.3 | 1.3
| Mikhail Antonov | Mikhail Antonov

View File

@ -162,7 +162,7 @@ HBase Private API::
[[hbase.binary.compatibility]] [[hbase.binary.compatibility]]
.Binary Compatibility .Binary Compatibility
When we say two HBase versions are compatible, we mean that the versions are wire and binary compatible. Compatible HBase versions means that clients can talk to compatible but differently versioned servers. It means too that you can just swap out the jars of one version and replace them with the jars of another, compatible version and all will just work. Unless otherwise specified, HBase point versions are (mostly) binary compatible. You can safely do rolling upgrades between binary compatible versions; i.e. across maintenance releases: e.g. from 1.2.4 to 1.2.6. See link:[Does compatibility between versions also mean binary compatibility?] discussion on the HBase dev mailing list. When we say two HBase versions are compatible, we mean that the versions are wire and binary compatible. Compatible HBase versions means that clients can talk to compatible but differently versioned servers. It means too that you can just swap out the jars of one version and replace them with the jars of another, compatible version and all will just work. Unless otherwise specified, HBase point versions are (mostly) binary compatible. You can safely do rolling upgrades between binary compatible versions; i.e. across maintenance releases: e.g. from 1.4.4 to 1.4.6. See link:[Does compatibility between versions also mean binary compatibility?] discussion on the HBase dev mailing list.
[[hbase.rolling.upgrade]] [[hbase.rolling.upgrade]]
=== Rolling Upgrades === Rolling Upgrades
@ -180,7 +180,7 @@ The rolling-restart script will first gracefully stop and restart the master, an
[[hbase.rolling.restart]] [[hbase.rolling.restart]]
.Rolling Upgrade Between Versions that are Binary/Wire Compatible .Rolling Upgrade Between Versions that are Binary/Wire Compatible
Unless otherwise specified, HBase minor versions are binary compatible. You can do a <<hbase.rolling.upgrade>> between HBase point versions. For example, you can go to 1.2.4 from 1.2.6 by doing a rolling upgrade across the cluster replacing the 1.2.4 binary with a 1.2.6 binary. Unless otherwise specified, HBase minor versions are binary compatible. You can do a <<hbase.rolling.upgrade>> between HBase point versions. For example, you can go to 1.4.4 from 1.4.6 by doing a rolling upgrade across the cluster replacing the 1.4.4 binary with a 1.4.6 binary.
In the minor version-particular sections below, we call out where the versions are wire/protocol compatible and in this case, it is also possible to do a <<hbase.rolling.upgrade>>. In the minor version-particular sections below, we call out where the versions are wire/protocol compatible and in this case, it is also possible to do a <<hbase.rolling.upgrade>>.

View File

@ -126,11 +126,6 @@
<item name="API" href="2.0/apidocs/index.html" target="_blank" /> <item name="API" href="2.0/apidocs/index.html" target="_blank" />
<item name="Ref Guide (single-page)" href="2.0/book.html" target="_blank" /> <item name="Ref Guide (single-page)" href="2.0/book.html" target="_blank" />
</item> </item>
<item name="1.2 Documentation">
<item name="API" href="1.2/apidocs/index.html" target="_blank" />
<item name="X-Ref" href="1.2/xref/index.html" target="_blank" />
<item name="Ref Guide (single-page)" href="1.2/book.html" target="_blank" />
</item>
</menu> </menu>
<menu name="ASF"> <menu name="ASF">
<item name="Apache Software Foundation" href="http://www.apache.org/foundation/" target="_blank" /> <item name="Apache Software Foundation" href="http://www.apache.org/foundation/" target="_blank" />

View File

@ -133,28 +133,6 @@ under the License.
</td> </td>
<td /> <td />
</tr> </tr>
<tr>
<td style="test-align: left">
1.2.12
</td>
<td style="test-align: left">
2019/04/17
</td>
<td style="test-align: left">
<a href="https://apache.org/dist/hbase/hbase-1.2.12/compat-check-report.html">1.2.11 vs 1.2.12</a>
</td>
<td style="test-align: left">
<a href="https://github.com/apache/hbase/blob/rel/1.2.12/CHANGES.txt">Changes</a>
</td>
<td style="test-align: left">
<a href="https://s.apache.org/hbase-1.2.12-jira-release-notes">Release Notes</a>
</td>
<td style="test-align: left">
<a href="https://www.apache.org/dyn/closer.lua/hbase/hbase-1.2.12/hbase-1.2.12-src.tar.gz">src</a> (<a href="https://apache.org/dist/hbase/hbase-1.2.12/hbase-1.2.12-src.tar.gz.sha512">sha512</a> <a href="https://apache.org/dist/hbase/hbase-1.2.12/hbase-1.2.12-src.tar.gz.asc">asc</a>) <br />
<a href="https://www.apache.org/dyn/closer.lua/hbase/hbase-1.2.12/hbase-1.2.12-bin.tar.gz">bin</a> (<a href="https://apache.org/dist/hbase/hbase-1.2.12/hbase-1.2.12-bin.tar.gz.sha512">sha512</a> <a href="https://apache.org/dist/hbase/hbase-1.2.12/hbase-1.2.12-bin.tar.gz.asc">asc</a>)
</td>
<td />
</tr>
</table> </table>
</section> </section>
<section name="Connectors"> <section name="Connectors">