hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lars hofhansl <la...@apache.org>
Subject Re: [ANNOUNCE] HBase 0.94.9 is available for download
Date Sat, 06 Jul 2013 16:14:26 GMT
An interesting question is how something like this can be avoided in the future. The problem
here was that tarball and the tag are created in separate steps and that the tarball is build
from the branch (not from the release SVN tag).

What we could do is setup a tempory jenkins build for the specific release tag and use that
to build the release.
The advantage is that that build - including the test run, etc - is there for everybody to
see. The tag-jenkins build can be deleted when the next point release is ready (or we could
just keep it).

-- Lars

----- Original Message -----
From: lars hofhansl <larsh@apache.org>
To: "user@hbase.apache.org" <user@hbase.apache.org>; "dev@hbase.apache.org" <dev@hbase.apache.org>
Sent: Saturday, July 6, 2013 9:09 AM
Subject: Re: [ANNOUNCE] HBase 0.94.9 is available for download

I am still leaning towards #1. There is no bug, just one jira missing from the maven release
for two weeks or so (until 0.94.10 is released).

HBASE-8656 has no functional implications but fixes a condition where sometimes handler threads
are leaked with secure HBase only.
Furthermore this issue has existing since 0.94.0.

So unless I hear very strong support/arguments for option #2 or #3 below, I'll simply leave
this as is.

-- Lars

From: Ted Yu <yuzhihong@gmail.com>
To: "dev@hbase.apache.org" <dev@hbase.apache.org> 
Cc: "dev@hbase.apache.org" <dev@hbase.apache.org>; hbase-user <user@hbase.apache.org>

Sent: Saturday, July 6, 2013 1:32 AM
Subject: Re: [ANNOUNCE] HBase 0.94.9 is available for download

Looks like option #2 is better. 


On Jul 6, 2013, at 1:22 AM, lars hofhansl <larsh@apache.org> wrote:

> So I cannot fix the maven release after the fact. So we have the following options:
> 1. Leave it as is. Tags/tar have HBASE-8656, but the maven release misses that that one
fix; and release 0.94.10 soon.
> 2. Release, which would be identical to 0.94.9 (except for the release name
change in pom.xml).
> 3. Re-release 0.94.9 with HBASE-8656 removed. That way tags and tar ball would be the
same as the maven release.
> Not sure which one I'd prefer. Probably #1 followed by #2.
> -- Lars
> ________________________________
> From: Aditya <adityakishore@gmail.com>
> To: "dev@hbase.apache.org" <dev@hbase.apache.org>; lars hofhansl <larsh@apache.org>

> Cc: hbase-user <user@hbase.apache.org> 
> Sent: Friday, July 5, 2013 9:12 PM
> Subject: Re: [ANNOUNCE] HBase 0.94.9 is available for download
> Thanks Lars.
> It looks like HBASE-8656, though part of the tarball, is not included in 0.94.9 tag.
> Regards,
> Aditya...
> On Thu, Jul 4, 2013 at 10:58 AM, lars hofhansl <larsh@apache.org> wrote:
> The HBase Team is pleased to announce the immediate release of HBase 0.94.9.
>> Download it from your favorite Apache mirror [1].
>> As usual, all previous 0.92.x and 0.94.x releases can upgraded to 0.94.9 via a rolling
upgrade without downtime, intermediary versions can be skipped.
>> 0.94.9 is the current stable release of HBase. It fixes the following 26 issues:
>>     [HBASE-8453] - TestImportExport failing again due to configuration issues
>>     [HBASE-8494] - TestRemoteAdmin#testClusterStatus should not assume 'requests'
does not change
>>     [HBASE-8522] - Archived hfiles and old hlogs may be deleted immediately by
HFileCleaner, LogCleaner in HMaster
>>     [HBASE-8555] - FilterList correctness may be affected by random ordering
of sub-filter(list)
>>     [HBASE-8590] - [0.94] BlockingMetaScannerVisitor should check for parent
meta entry while waiting for split daughter
>>     [HBASE-8639] - Poor performance of htable#getscanner in multithreaded environment
due to DNS.getDefaultHost() being called in ScannerCallable#prepare()
>>     [HBASE-8640] - ServerName in master may not initialize with the configured
ipc address of hbase.master.ipc.address
>>     [HBASE-8655] - Backport to 94 - HBASE-8346(Prefetching .META. rows in case
only when useCache is set to true)
>>     [HBASE-8656] - Rpc call may not be notified in SecureClient
>>     [HBASE-8671] - Per-region WAL breaks CP backwards compatibility in 0.94 for
non-enabled case
>>     [HBASE-8684] - Table Coprocessor can't access external HTable by default
>>     [HBASE-8700] - IntegrationTestBigLinkedList can fail due to random number
>>     [HBASE-8724] - [0.94] ExportSnapshot should not use hbase.tmp.dir as a staging
dir on hdfs
>>     [HBASE-8742] - HTableDescriptor Properties not preserved when cloning
>>     [HBASE-8743] - upgrade hadoop-23 version to 0.23.7
>>     [HBASE-8749] - Potential race condition between FSUtils.renameAndSetModifyTime()
and HFile/LogCleaner
>>     [HBASE-8762] - Performance/operational penalty when calling HTable.get with
a list of one Get
>>     [HBASE-8783] - RSSnapshotManager.ZKProcedureMemberRpcs may be initialized
with the wrong server name
>>     [HBASE-5083] - Backup HMaster should have http infoport open with link to
the active master
>>     [HBASE-8609] - Make the CopyTable support startRow, stopRow options
>>     [HBASE-8636] - Backport KeyValue Codec to 0.94 (HBASE-7413)
>>     [HBASE-8683] - Add major compaction support in CompactionTool
>>     [HBASE-8692] - [AccessController] Restrict HTableDescriptor enumeration
>>     [HBASE-8702] - Make WALEditCodec pluggable
>>     [HBASE-8504] - HTable.getRegionsInRange() should provide a non-cached API
>>     [HBASE-8603] - Backport HBASE-6921 to 0.94
>> See also the full release notes [2].
>> Thanks to the 18 individuals who contributed to this release!
>> Yours,
>> The HBase Team
>> 1. http://www.apache.org/dyn/closer.cgi/hbase/
>> 2. https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12324431

View raw message