+1
Thanks
Baoloong
> On Aug 12, 2020, at 22:30, Sammi Chen wrote:
>
> We have resolved all JIRAs targeting 0.6.0 by today. Thanks everyone for
> your continuous contribution!
>
> All 0.6.0 commits are cherry-picked from master to ozone-0.6.0, except this
> revert request(https://github.com/ap
+1 for 1.0.0
On Wed, Aug 12, 2020 at 10:50 AM Aravindan Vijayan
wrote:
> +1 for 1.0.0.
>
> https://github.com/apache/hadoop-ozone/pull/1313 has been merged to
> ozone-0.6.0.
>
>
> On Wed, Aug 12, 2020 at 9:15 AM Arpit Agarwal
>
> wrote:
>
> > +1 to update the version to 1.0.0.
> >
> > Anyone ob
+1 for 1.0.0.
https://github.com/apache/hadoop-ozone/pull/1313 has been merged to
ozone-0.6.0.
On Wed, Aug 12, 2020 at 9:15 AM Arpit Agarwal
wrote:
> +1 to update the version to 1.0.0.
>
> Anyone objecting to the version number change can respond to the release
> vote. We don't need a separate
+1 to update the version to 1.0.0.
Anyone objecting to the version number change can respond to the release vote.
We don't need a separate vote thread.
On 8/12/20, 7:31 AM, "Sammi Chen" wrote:
We have resolved all JIRAs targeting 0.6.0 by today. Thanks everyone for
your continuous c
+1
Thanks
Shashi
On Wed, Aug 12, 2020, 8:37 PM Bharat Viswanadham
wrote:
> +1 for 1.0
>
> Thanks,
> Bharat
>
>
> On Wed, Aug 12, 2020 at 8:06 AM Jitendra Pandey
> wrote:
>
> > +1 to change the version to 1.0.0
> >
> > On Wed, Aug 12, 2020 at 7:31 AM Sammi Chen wrote:
> >
> > > We have resolve
+1 for 1.0
Thanks,
Bharat
On Wed, Aug 12, 2020 at 8:06 AM Jitendra Pandey wrote:
> +1 to change the version to 1.0.0
>
> On Wed, Aug 12, 2020 at 7:31 AM Sammi Chen wrote:
>
> > We have resolved all JIRAs targeting 0.6.0 by today. Thanks everyone for
> > your continuous contribution!
> >
> >
+1 to change the version to 1.0.0
On Wed, Aug 12, 2020 at 7:31 AM Sammi Chen wrote:
> We have resolved all JIRAs targeting 0.6.0 by today. Thanks everyone for
> your continuous contribution!
>
> All 0.6.0 commits are cherry-picked from master to ozone-0.6.0, except this
> revert request(https:/
We have resolved all JIRAs targeting 0.6.0 by today. Thanks everyone for
your continuous contribution!
All 0.6.0 commits are cherry-picked from master to ozone-0.6.0, except this
revert request(https://github.com/apache/hadoop-ozone/pull/1313) which is
pending for confirmation.
I will start to b
+1 for 1.0.0 as GA
On Thu, Jul 23, 2020 at 8:32 AM Sammi Chen wrote:
> Marton, good idea. 1.0.0 is a good candidate for GA version.
>
> I will wait a few days in case there is other feedback.
>
> Sammi
>
> On Mon, Jul 20, 2020 at 6:03 PM Elek, Marton wrote:
>
> >
> > On 7/10/20 11:50 AM, Mukul
Marton, good idea. 1.0.0 is a good candidate for GA version.
I will wait a few days in case there is other feedback.
Sammi
On Mon, Jul 20, 2020 at 6:03 PM Elek, Marton wrote:
>
> On 7/10/20 11:50 AM, Mukul Kumar Singh wrote:
> > +1 for GA as well.
> >
> > We have done lots of compatibility te
On 7/10/20 11:50 AM, Mukul Kumar Singh wrote:
+1 for GA as well.
We have done lots of compatibility testing with Ozone with Hive and Spark. >
I have the same question as on the Ratis side.
If we think it's GA, why don't we call it 1.0.0 ?
Marton
--
+1 for GA as well.
We have done lots of compatibility testing with Ozone with Hive and Spark.
Thanks,
Mukul
On 09/07/20 10:42 am, Aravindan Vijayan wrote:
+1 for GA.
We are tracking some basic 0.6.0 work items to make sure there is upgrade
compatibility in the future. HDDS-3698 will be the
+1 for GA.
We are tracking some basic 0.6.0 work items to make sure there is upgrade
compatibility in the future. HDDS-3698 will be the umbrella JIRA for the
full non-rolling upgrade support for the next release. I will send out a
mail with guidelines for API compatibility maintenance and handling
+1 to call it GA.
Agree with Arpit that we will need to provide compatibility and upgrade
paths, going forward.
On Wed, Jul 8, 2020 at 9:48 AM Arpit Agarwal
wrote:
> Quality aside, declaring GA means:
> 1. We will not make incompatible changes to wire protocols, APIs, tools or
> on-disk formats.
Quality aside, declaring GA means:
1. We will not make incompatible changes to wire protocols, APIs, tools or
on-disk formats.
2. We will support upgrades from GA to any future release.
I am +1 to call this a GA release, assuming Sammi approves as the RM.
On Wed, Jul 8, 2020 at 6:12 AM Sammi Chen
Branch ozone-0.6.0 is created today.
So far we have 18 opens for 0.6.0. You can find the details from
https://issues.apache.org/jira/issues/?jql=project+%3D+HDDS+AND+cf%5B12310320%5D+%3D+0.6.0+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%2C+%22Patch+Available%22%29
Our internal clust
Hi,
Are we planning to make the next version of the Ozone release as GA?
*Few points to consider in making ozone GA release.*
1. A lot of testing has been done with Hive and Spark TPC-DS.
2. Scale test is also done. A billion object test is also run on Ozone.
Thanks,
Bharat
On Sun, Jun 21, 20
Hi, everyone,
Here is the planned feature list of 0.6.0 release.
- Security Phase II
- HA support for Ozone Manager
- OFS (HDDS-2665), new scheme: ofs://om/volume/bucket/key
- Ozone Filesystem performance improvement (HDDS-2939)
- Ozone support security enabled Hadoop 2.x
- S3
18 matches
Mail list logo
