Hi Sammi,

Thanks for creating the RC. If you do spin up a new RC, could you please 
consider including the following 2 Jiras in the release:
HDDS-4068 
HDDS-4063

Thanks,
Hanisha


> On Aug 24, 2020, at 1:01 PM, Attila Doroszlai <adorosz...@apache.org> wrote:
> 
> Hi Sammi,
> 
> Thanks for creating the RC.  I have found that there are some leftover
> references to version "0.6.0" in upgrade scripts and tests
> (HDDS-4139).  Created a pull request to fix it, please consider
> including it in the release.
> 
> thanks,
> Attila
> 
> On Mon, Aug 24, 2020 at 3:55 PM Elek, Marton <e...@apache.org 
> <mailto:e...@apache.org>> wrote:
>> 
>> 
>> +1 (binding)
>> 
>> 
>> 
>> 
>> 1. verified signatures
>> 
>> 2. verified checksums
>> 
>> 3. verified the output of `ozone version` (includes the good git revision)
>> 
>> 4. verified that the source package matches the git tag
>> 
>> 5. verified source can be used to build Ozone without previous state
>> (docker run -v ... -it maven ... --> built from the source with zero
>> local maven cache during 30 minutes)
>> 
>> 6. Verified Ozone can be used from binary package (cd compose/ozone &&
>> test.sh --> all tests were passed)
>> 
>> 7. Verified documentation is included in SCM UI
>> 
>> 8. Deployed to Kubernetes and executed Teragen on Yarn [1]
>> 
>> 9. Deployed to Kubernetes and executed Spark (3.0) Word count (local
>> executor) [2]
>> 
>> 
>> I know about a few performance problems (like HDDS-4119) but I don't
>> think we should further block the release (they are not regressions just
>>  improvements). If we will have significant performance improvements
>> soon, we can release 1.0.1 within 1 month.
>> 
>> 
>> Thanks the great work Sammi!!
>> 
>> Marton
>> 
>> [1]: https://github.com/elek/ozone-perf-env/tree/master/teragen-ozone
>> [2]: https://github.com/elek/ozone-perf-env/tree/master/spark-ozone
>> 
>> 
>> 
>> 
>> On 8/20/20 3:12 PM, Sammi Chen wrote:
>>> my +1(binding)
>>> 
>>>    -  Verified ozone version of binary package
>>> 
>>>    -  Verified ozone source package content with ozone-1.0.0-RC0 tag
>>> 
>>>    -  Build ozone from source package
>>> 
>>>    -  Upgrade an existing 1+3 cluster using RC0 binary package
>>> 
>>>    -  Check Ozone UI, SCM UI, Datanode UI and Recon UI
>>> 
>>>    -  Run TestDFSIO write/read with Hadoop 2.7.5
>>> 
>>>    -  Verified basic o3fs operations, upload and download file
>>> 
>>>    -  Create bucket using aws CLI,  upload and download 10G file through s3g
>>> 
>>> Thanks,
>>> Sammi
>>> 
>>> On Thu, Aug 20, 2020 at 8:55 PM Sammi Chen <sammic...@apache.org> wrote:
>>> 
>>>> 
>>>> This Ozone 1.0.0 release includes 620 JIRAs,
>>>> 
>>>> https://issues.apache.org/jira/issues/?jql=project+%3D+HDDS+AND+%28cf%5B12310320%5D+%3D+0.6.0+or+fixVersion+%3D+0.6.0%29
>>>> 
>>>> Thanks everyone for putting in the effort and making this happen.
>>>> 
>>>> You can find the RC0 artifacts are at:
>>>> https://home.apache.org/~sammichen/ozone-1.0.0-rc0/
>>>> 
>>>> Maven artifacts are staged at:
>>>> https://repository.apache.org/content/repositories/orgapachehadoop-1277
>>>> 
>>>> The public key used for signing the artifacts can be found at:
>>>> https://dist.apache.org/repos/dist/release/hadoop/common/KEYS
>>>> 
>>>> The RC0 tag in github is at:
>>>> https://github.com/apache/hadoop-ozone/releases/tag/ozone-1.0.0-RC0
>>>> 
>>>> *The vote will run for 7 days, ending on Aug 27th 2020 at 11:59 pm CST.*
>>>> 
>>>> Thanks,
>>>> Sammi Chen
>>>> 
>>>> 
>>>> 
>>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ozone-dev-unsubscr...@hadoop.apache.org 
>> <mailto:ozone-dev-unsubscr...@hadoop.apache.org>
>> For additional commands, e-mail: ozone-dev-h...@hadoop.apache.org 
>> <mailto:ozone-dev-h...@hadoop.apache.org>
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org 
> <mailto:hdfs-dev-unsubscr...@hadoop.apache.org>
> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org 
> <mailto:hdfs-dev-h...@hadoop.apache.org>

Reply via email to