[
https://issues.apache.org/jira/browse/HBASE-23012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16958944#comment-16958944
]
Sean Busbey edited comment on HBASE-23012 at 10/24/19 2:51 PM:
---------------------------------------------------------------
because releases are a business process of the foundation, they need to be
dated according to that process. The authoritative date for a release is when
the artifacts are placed in the subversion repo backing dist.a.o.
so for 1.3.6 if we look at the log
{code}
hbase-releases busbey$ TZ=GMT svn log --verbose hbase-1.3.6/
------------------------------------------------------------------------
r36393 | busbey | 2019-10-20 03:28:55 +0000 (Sun, 20 Oct 2019) | 1 line
Changed paths:
D /dev/hbase/hbase-1.3.6RC1
A /release/hbase/hbase-1.3.6 (from /dev/hbase/hbase-1.3.6RC1:36392)
Release Apache HBase 1.3.6
------------------------------------------------------------------------
r36344 | busbey | 2019-10-15 13:15:34 +0000 (Tue, 15 Oct 2019) | 1 line
Changed paths:
D /dev/hbase/hbase-1.3.6RC0
A /dev/hbase/hbase-1.3.6RC1
A /dev/hbase/hbase-1.3.6RC1/compat-check-report.html
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-bin.tar.gz
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-bin.tar.gz.asc
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-bin.tar.gz.md5
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-bin.tar.gz.sha
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-src.tar.gz
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-src.tar.gz.asc
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-src.tar.gz.md5
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-src.tar.gz.sha
Staging HBase 1.3.6 RC1 for Sakthi.
------------------------------------------------------------------------
{code}
And see that the source artifact arrived in the release area at 2019-10-20. It
only really matters for our board report and I think that pulls from
reporter.a.o.
was (Author: busbey):
because releases are a business process of the foundation, they're need to be
dated according to that process. The authoritative date for a release is when
the artifacts are placed in the subversion repo backing dist.a.o.
so for 1.3.6 if we look at the log
{code}
hbase-releases busbey$ TZ=GMT svn log --verbose hbase-1.3.6/
------------------------------------------------------------------------
r36393 | busbey | 2019-10-20 03:28:55 +0000 (Sun, 20 Oct 2019) | 1 line
Changed paths:
D /dev/hbase/hbase-1.3.6RC1
A /release/hbase/hbase-1.3.6 (from /dev/hbase/hbase-1.3.6RC1:36392)
Release Apache HBase 1.3.6
------------------------------------------------------------------------
r36344 | busbey | 2019-10-15 13:15:34 +0000 (Tue, 15 Oct 2019) | 1 line
Changed paths:
D /dev/hbase/hbase-1.3.6RC0
A /dev/hbase/hbase-1.3.6RC1
A /dev/hbase/hbase-1.3.6RC1/compat-check-report.html
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-bin.tar.gz
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-bin.tar.gz.asc
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-bin.tar.gz.md5
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-bin.tar.gz.sha
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-src.tar.gz
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-src.tar.gz.asc
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-src.tar.gz.md5
A /dev/hbase/hbase-1.3.6RC1/hbase-1.3.6-src.tar.gz.sha
Staging HBase 1.3.6 RC1 for Sakthi.
------------------------------------------------------------------------
{code}
And see that the source artifact arrived in the release area at 2019-10-20. It
only really matters for our board report and I think that pulls from
reporter.a.o.
> Release 1.3.6
> -------------
>
> Key: HBASE-23012
> URL: https://issues.apache.org/jira/browse/HBASE-23012
> Project: HBase
> Issue Type: Task
> Components: community
> Reporter: Sakthi
> Assignee: Sakthi
> Priority: Major
> Fix For: 1.3.6
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
