> 1) Update src/contrib/ec2/hbase-ec2-env.sh to use the version
> of the release.
I removed the -dev of the next RC which I'm releasing at the moment.
>
> 2) Build a tarball hbase-{version}.tar.gz and put it up in an S3
> bucket of mine
>
> iridiant.s3.amazonaws.com/hbase/hbase-{version}.tar.gz
>
> 3) Use the build scripts to build new HBase AMIs:
> ./src/contrib/ec2/bin/create-hbase-image c1.medium
> ./src/contrib/ec2/bin/create-hbase-image c1.xlarge
>
> Implicit in this step is storage of the images in a S3 bucket
> under my account and registration of the image.
>
> Then, mark the AMIs as public.
>
> I think only step #1 can be done at release time and I'll have to
> do the rest subsequently.
>
> Also, as was brought up before, we should have a HBase project
> account with AWS somehow. Also, somebody else besides us owns the
> bucket names "hbase" and "hbase-images". I wonder what the AWS
> policy is and if we could enforce some kind of claim (doubtful)
> on those buckets.
+1, or maybe use hadoop-hbase or asf-hbase-images, etc
>
> - Andy
>
>
>
> ----- Original Message ----
>> From: Jean-Daniel Cryans <jdcry...@apache.org>
>> To: hbase-dev@hadoop.apache.org
>> Sent: Fri, January 8, 2010 11:10:30 AM
>> Subject: Re: Freezing commits to branch
>>
>> That could just be part of the release process IMO, we don't want to
>> delay releases if you are stuck over the pacific ocean :P
>>
>> J-D
>>
>> On Fri, Jan 8, 2010 at 11:06 AM, Andrew Purtell wrote:
>> > That's too bad. :-(
>> >
>> > But, hey, the next time, as soon as someone freezes a branch I will
>> > need to update one file -- src/contrib/ec2/bin/hbase-ec2-env.sh. I
>> > was so busy yesterday I forgot to mention it. Hope that is ok and not
>> > too inconvenient.
>> >
>> > - Andy
>
>
>
>
>
