Re: [DISCUSS] 1.2.0 release

+1 On Thu, Aug 26, 2021 at 11:36 AM Vivek Ratnavel wrote: > +1, thanks for volunteering Ethan! > > > On Thu, Aug 26, 2021 at 11:35 AM Prashant Pogde > > wrote: > > > +1, thanks Thanks for volunteering! > > > > > On Aug 25, 2021, at 11:28 AM, Aravindan Vijayan > > wrote: > > > > > > Hello all,

[VOTE] Apache Ozone 1.2.0 RC0

/ The public key used to sign the artifacts can be found at: https://dist.apache.org/repos/dist/dev/ozone/KEYS The fingerprint of the key used to sign the artifacts is: 00D357B731EBDD66D7CA91B39146CE06B541B7E7 Thanks, Ethan Rose

Re: [VOTE] Apache Ozone 1.2.0 RC0

l. > > Docs are missing from the binary archive. Hugo is required for > building the docs. > > -Attila > > On Mon, Nov 1, 2021 at 6:44 PM Ethan Rose > wrote: > > > > Hello all, > > > > As discussed earlier, I am calling for a vote on Apache Ozone 1.2

[VOTE] Apache Ozone 1.2.0 RC1

The fingerprint of the key used to sign the artifacts is: 00D357B731EBDD66D7CA91B39146CE06B541B7E7 Thanks, Ethan Rose

Re: [VOTE] Apache Ozone 1.2.0 RC1

he > previous release for comparison: > > Source code repository https://github.com/apache/ozone.git -r > f2406c4b4eb2b1295d06ec379cfe684ed9a16637 > Compiled by ppogde on 2021-04-09T04:10Z > > -Attila > > On Thu, Nov 4, 2021 at 8:26 PM Ethan Rose > wrote: > > > &g

[VOTE] Apache Ozone 1.2.0 RC2

: 00D357B731EBDD66D7CA91B39146CE06B541B7E7 Thanks, Ethan Rose

Re: [VOTE] Apache Ozone 1.2.0 RC2

. On Tue, Nov 16, 2021 at 4:00 PM Neil Joshi wrote: > +1 > > Thanks Ethan. > > Regards, > Neil > > On Wed, Nov 10, 2021 at 11:38 AM Ethan Rose > wrote: > > > Hello all, > > > > The issue with `ozone version` output has been fixed and I would li

[Announce] Apache Ozone 1.2.0 Release

Hello all, I am happy to announce that Apache Ozone 1.2.0 has been released. Release details and links to downloads are on the 1.2.0 announcement page: https://ozone.apache.org/release/1.2.0/ Download links are also available from the downloads page: https://ozone.apache.org/downloads/ Versione

[Announce] Apache Ozone 1.2.1 Release

Hello all, I am happy to announce the release of Apache Ozone 1.2.1. This release updates Ozone's log4j version to 2.16. We are still working to update the website. The source and binary tarballs can be downloaded from: https://dlcdn.apache.org/ozone/1.2.1/ or https://downloads.apache.org/ozone/1

Re: [DISCUSS] 1.3.0 release

Hi MingChao, thanks for driving this effort. We have a few release blockers on the upgrade side that need to be resolved before we can release: - SCM HA finalization (I have begun working on this): HDDS-5141 - Onboarding FSO into the upgrade framework (this can start now that EC has been onboarded

Re: [DISCUSS] 1.3.0 release

Also a reminder that there is still a merge vote for HDDS-4440 ongoing as well. It may be best to resolve that before discussing a release. On Fri, Apr 22, 2022 at 7:32 AM Ethan Rose wrote: > Hi MingChao, thanks for driving this effort. > > We have a few release blockers on the upg

Re: [VOTE] Merge Ozone S3 Multi-Tenancy feature branch (HDDS-4944) into master

+1 On Thu, May 26, 2022 at 2:06 PM Prashant Pogde wrote: > +1 > > > On May 23, 2022, at 8:40 PM, Siyao Meng wrote: > > > > Dear Ozone devs, > > > >I am starting this vote thread for merging the Ozone S3 Multi-Tenancy > > feature branch (HDDS-4944) to the master branch. > > > > S3 multi-ten

Re: [Internet][DISCUSS] 1.3.0 release

+1. I think we should fix the RocksDB memory leaks so we can increase to version 7 in this release, but those can be cherry-picked on to the branch. On Tue, Jul 26, 2022 at 7:48 PM baoloongmao(毛宝龙) wrote: > +1, thank you. > > > > > > > > > >--回复的邮件信息-- > > mingchao zhao 上

Re: [RFC] Proposal: Reserve Space for Allocated Blocks

I believe the flow is: 1. Datanode notices the container is near full. 2. Datanode sends close container action to SCM on its next heartbeat. 3. SCM closes the container and sends a close container command on the heartbeat response. 4. Datanodes get the response and close the container. If it is a

Re: [VOTE] Apache Ozone 1.3.0 RC0

We recently had a PR merged that fixes SCM HA finalization using the incorrect RocksDB table to write information. Since this is a new feature in 1.3.0 it seems like we should cherry pick this to the release branch and make an RC1. MingChao and others, wh

Re: [VOTE] Apache Ozone 1.3.0 RC0

thub.com/apache/ozone/pull/3961 fixed a severe problem. > > > > We'd better have it in 1.3.0 release. > > > > Bests, > > Sammi > > > > On Wed, 16 Nov 2022 at 02:42, Ethan Rose > > wrote: > > > > > We recently had a PR <https:

Re: Past Ozone Events

; > > The following was the list of agenda: > Bucket types and FSO improvements > > Speaker: Ethan Rose > > Recent release of the Cloudera Data Platform 7.1.8 shipped two key feature > improvements for Apache Ozone - ability to create specialized buckets: > object store (OBS) and

Re: [DISCUSS] Proposal to merge HDDS-6517 Ozone Snapshots

Hey Prashant, thanks for all the work on this feature. I think the confluence page needs a few updates for completeness. > > *2. documentation* > > Documentaion can be found under the Attachments section in the umbrella > jira: HDDS-6517 - Snapshot

Re: [DISCUSS] Proposal to merge HDDS-6517 Ozone Snapshots

Thanks for the updates Prashant. The wiki LGTM so I am +1 to proceed with a vote. On Wed, Jan 11, 2023 at 12:49 PM Prashant Pogde wrote: > Thanks for the feedback Ethan, Uma and Sid. I have updated the template on > the wiki with Jira tickets to address these concerns. > > > On Jan 11, 2023, at

Re: [DISCUSS] Proposal to merge HttpFS support in Ozone feature branch (HDDS-5447-httpfs) into master

+1 for merge, thanks Zita and Pifta! - Ethan On Mon, Feb 6, 2023 at 2:58 PM Zita Dombi wrote: > Hi Ozone Devs! > > I am starting this discussion thread for proposing to merge the HttpFS > support in Ozone feature branch (HDDS-5447 > ) to the mast

Re: Cutting Ozone 1.3.1

+1 for a patch release with all the fixes previously mentioned. In addition, these bugs related to FSO deletion were fixed since 1.3.0 and should be added: HDDS-7541 HDDS-7592 On Tue, Mar 14, 2023 at 7:53 AM Siddharth Wagle wrote: > +1 for 1.3.1 with critical fixes. > > Best, > Sid > > On Tue, M

Re: Proposal to enable GitHub discussions

+1. Ritesh, I've seen you messing around with this on your Ozone fork. If you have it in a presentable state, could you share the link here so others can reference an example of how we could set up the sections to organize questions, meeting minutes, etc? Ethan On Sun, Apr 23, 2023 at 11:12 PM Ri

Re: [VOTE] Proposal to merge Ozone feature branch HDDS-7733-Symmetric-Tokens to master

+1 for the merge Ethan On Wed, May 31, 2023 at 7:31 PM Sumit Agrawal wrote: > Hi Duong, > > Thanks for working on this. > > Binding +1 > > Regards > Sumit > > On Thu, Jun 1, 2023 at 6:10 AM Duong Nguyen wrote: > > > Hi Ozone Devs, > > > > Following the discussion thread regarding the same topi

[Proposal] Datanode container log for tracking container replica state changes

Hi Ozone Devs, I am currently working on HDDS-7364 to get Ozone's container scanner to a point where it can be enabled by default. The container scanner will check container block data and metadata in the background to identify corruption, mark co

Re: [DISCUSS] Next Ozone major release 1.4.0

+1 for a 1.4.0 release. We had hoped for a 1.3.1 release but it looks like that never gained the momentum it needed. It would be good to hear from devs working on larger features whether or not they would like to target this release. Things like snapshots, cert rotation, hsync, recon improvements e

Detecting disk/volume failures in Ozone

Hi Ozone devs, I am currently working on HDDS-8782 to improve the checks that are run by Ozone's volume scanner. This is a thread that periodically runs in the background of datanodes to check the health of volumes/disks configured with hdds.datano

Re: Detecting disk/volume failures in Ozone

e the disk? > > Regards, > Uma > > On Thu, Jun 15, 2023 at 3:46 PM Ethan Rose > wrote: > > > Hi Ozone devs, > > > > I am currently working on HDDS-8782 > > <https://issues.apache.org/jira/browse/HDDS-8782> to improve the checks > > that are run

Re: Detecting disk/volume failures in Ozone

bling them would be write > performance, but a small speed up in write should not be preferred over > data integrity. > > On Wed, Jun 21, 2023 at 12:45 AM Ethan Rose > wrote: > > > Hi Uma, > > > > The datanode side checksums on write are still turned off. IO Exceptio

Re: New committer: George Bijan Jahad

Congratulations George! Thanks for all your work on Ozone so far. Ethan On Tue, Jun 27, 2023 at 4:46 PM Michel Sumbul wrote: > Wouhouuu, congratulations George > > > Le mer. 28 juin 2023, 00:40, Wei-Chiu Chuang a écrit > : > > > The Project Management Committee (PMC) for Apache Ozone has i

Re: [DISCUSS] Please limit PR size

I've definitely been on both sides: posting a large PR myself, and as a reviewer asking for PRs to be separated into smaller pieces. If we want something persisted beyond an email thread I think we could update CONTRIBUTING.md with a new section about how to post larger changes. Tips for breaking d

Re: [DISCUSS] Please limit PR size

master/.github/pull_request_template.md > Seems like a good way to soft-enforce the rule. > > On Wed, Jul 26, 2023 at 3:53 PM Ethan Rose > wrote: > > > I've definitely been on both sides: posting a large PR myself, and as a > > reviewer asking for PRs to be separated

Re: [DISCUSS] Next Ozone major release 1.4.0

> > >>>> > > the > >>>> > > >>>> > > leader SCM will be able to initiate the rotation of CA > certificates > >>>> we > >>>> > > >>>> > have > >>>> > > >

Re: [DISCUSS] Next Ozone major release 1.4.0

23 at 9:59:15 PM, Sammi Chen < > >> > sammic...@apache.org > >> > > > > >> > > > > > wrote: > >> > > > > > >>>> > >> > > > > > >>>>> Thank you, Yiyang, for volunteering the 1

Re: [DISCUSS] Next Ozone major release 1.4.0

- Fetch root CA certificate list during SCM startup > > > > HDDS-8958 - Handle trust chain changes in clients when rootCAs are > > > rotated. > > > > HDDS-8960 - Hold the rootCA's private key only in memory for the time > > of > > > > initializa

Improving the Apache Ozone Website and Documentation

Hello Ozone Community, As many of you are aware, Ozone's website and documentation has remained somewhat disorganized and lacking in content for a while. I would like to kick start an initiative to change that. I have attached a document outlining a plan to redo Ozone's website and documentation s

Re: Improving the Apache Ozone Website and Documentation

attached it in the email above, but I can't find it > there, maybe I'm missing something :) > > thanks, > Zita > > Dinesh Chitlangia ezt írta (időpont: 2023. aug. 29., > K, 4:44): > > > +1 , this is a much needed improvement. > > > > > &

Re: Improving the Apache Ozone Website and Documentation

/13062569/Improving%20the%20Apache%20Ozone%20Website.pdf> as well. The proposal includes details for improving both the site layout and its content. Ethan On Tue, Aug 29, 2023 at 11:17 AM Ethan Rose wrote: > Thanks for the responses, it seems the PDF document did not attach > correctly. I h

Re: Improving the Apache Ozone Website and Documentation

ur current docs website is search > capability. I see the Yunikorn website you linked is using Algolia, it > would be great to integrate that or something equivalent. > > > > On Aug 28, 2023 at 5:25:16 PM, Ethan Rose > wrote: > > > Hello Ozone Community, > >

Re: Improving the Apache Ozone Website and Documentation

love to see is more user docs. > Our doc is by and large written for core Ozone developers. We need to have > more content around how to run workarounds, how to migrate existing > applications from HDFS to Ozone, API guide ... etc. > > On Mon, Aug 28, 2023 at 5:25 PM Ethan Rose >

Re: [Announce] Apache Ozone 1.4.0 Release

Thanks Yiyang for managing the release and to all who contributed. Ethan On Mon, Jan 22, 2024 at 12:25 AM Attila Doroszlai wrote: > Thanks Yiyang for driving the release to completion. > > -Attila > > - > To unsubscribe, e-mail

Re: Improving the Apache Ozone Website and Documentation

we can accept contributions to pages in the new website, and we are looking for volunteers who would like to help us with this project. Thanks, Ethan On Thu, Nov 2, 2023 at 6:32 PM Ethan Rose wrote: > Hi Ozone devs, > > It has been a while since I started this thread and got carried o

Ozone Storage Container Reconciliation

Hi Ozone Devs, I wanted to let everyone know that we have a proposal for a new container reconciliation feature to help us increase container durability and move beyond the complexity of unhealthy and quasi-closed states that the system currently cannot recover from. We discussed this at the US co

Re: RFC: Deprecate Slack and move to GitHub Discussions

Thanks for bringing up this proposal Ritesh. I am +1 for using GitHub Discussions for user/operational questions and indicating that on our Slack channel. I am also +1 for design discussions happening as PRs to markdown documents as we are doing for container reconciliation. Inline comments make i

Re: RFC: Deprecate Slack and move to GitHub Discussions

, to have an emphasis on at > least > > notifying everyone in the dev@ list also, so who is interested can chime > > in > > to the design process. > > If we select to go this way, leave slack, move user/operational questions > > to Github Discussions and design to

Re: Ozone Community Sync Notes - 29th Jan, 9AM Monday (PST)

pr. > >Attila pinging specific folks for review help. > > > >1. > > *Any new design proposals ?* > > * Discussion Notes:* > > Ethan presented a Container reconciliation proposal. > > There was some good Q&A. &

[VOTE] Change the default branch for ozone-site from asf-site to master

Hi Ozone devs, I’d like to start a vote thread to change the default branch in the apache/ozone-site repo from asf-site to master. Changing the default branch requires an Infra ticket and mailing thread according to the asfyaml README

Re: Supported releases

While I would also be surprised if people are successfully running an unpatched version of 1.3.0, it seems like a circular dependency to decide which versions to support based on what people are using. People will generally prefer to use supported versions so our messaging here informs their decisi

Re: [VOTE] Change the default branch for ozone-site from asf-site to master

;> febr. 10., Szo, 22:43): > >> > >>> Hi Ethan, > >>> Thanks for taking up this initiative. > >>> While this is not a problem for existing committers, I do believe > people > >>> who are new to the repo might have some confusion with t

Re: [VOTE] Change the default branch for ozone-site from asf-site to master

l-written description Ethan. I missed this thread > > > earlier. > > > > > > > > On Feb 20, 2024 at 10:21:38 PM, Dinesh Chitlangia < > dine...@apache.org> > > > > wrote: > > > > > > > >> +1 > > > >> > &g

Re: [VOTE] Change the default branch for ozone-site from asf-site to master

Follow https://issues.apache.org/jira/browse/INFRA-25530 if you would like more updates on this change. On Thu, Feb 22, 2024 at 1:21 PM Ethan Rose wrote: > Thanks everyone for voting. After running for 2 weeks the vote has passed > with: > 13 +1s (including 7 binding PMC +1s) > No

Re: Legal compliance for used cryptography - exploration/design phase

I saw this message in my inbox, but the issue may be that it did not come from an @apache email address, but I have a similar name with @apache in my gmail contacts. In this case gmail may flag it as phishing. I also have multiple sender addresses configured and sometimes forget to switch to my @ap

Re: [VOTE] Change the default branch for ozone-site from asf-site to master

INFRA-25530 is resolved and the default branch for apache/ozone-site is now master. The PR template is merged there as well and is now effective for pull requests across the repo. Thanks all for your participation, Ethan On Thu, Feb 22, 2024 at 1:49 PM Ethan Rose wrote: > Follow ht

Re: Improving the Apache Ozone Website and Documentation

cessible pages on the website to fill in as well. Overall I feel the project is steadily progressing and thank you all for your support. Ethan On Wed, Jan 24, 2024 at 5:17 PM Ethan Rose wrote: > Hi all, I just wanted to provide some updates on the new website. I will > try to send out the

Re: [DISCUSS] Ozone 1.4.1 Release

+1 for a 1.4.1 release. Thanks Xi Chen for volunteering as release manager! Ethan On Sun, Apr 7, 2024 at 8:38 PM Ivan Andika wrote: > +1. Since ETag feature already landed on ozone-1.4 branch. I also propose > to include ETag related fixes / improvements in version 1.4.1. > HDDS-9680. Use md5

Re: [DISCUSS] Ozone 1.4.1 Release

Doing the next release from master makes sense to me given the increased focus on bug fixes and stability. I don't think I have a preference on calling it 1.4.1 or 1.5.0. It might be strange to have an ozone-1.4 branch and then an ozone-1.4.1 branch that is not based off it, but that's not a big de

Re: [VOTE] Merge HDDS-10656-atomic-key-overwrite into master

Hi all, after reviewing the proposal I noticed this in the documentation section: > > The new API is for developers to build upon. Not intended for end-users > or administrators. > But there is a CLI under 'ozone sh' which looks like the type of thing u

Re: [VOTE] Merge HDDS-7593 (HSync and lease recovery) into master

Thanks for all the work on this. Looks good overall, just a few questions on compatibility: It looks like this line in the merge checklist was not updated. Can you go into more details about the OM compatibility for lease recovery or other operations? > A new OM version number was introduced to p

Re: [VOTE] Merge HDDS-7593 (HSync and lease recovery) into master

tal chunk list. We will update with a > more meaningful name as HBASE_INCREMENTAL_CHUNK_SUPPORT. > Also will update the merge checklist in more detail about this. > > Thanks, > Ashish > > On Fri, Jul 26, 2024 at 12:50 AM Ethan Rose wrote: > > > Thanks for all the wo

Re: [VOTE] Merge HDDS-7593 (HSync and lease recovery) into master

hunk list" > which > > is already taken care of. > > > > >> DataNode layout version "HBASE_SUPPORT" > > Yes this is only related to incremental chunk list. We will update with a > > more meaningful name as HBASE_INCREMENTAL_CHUNK_SUPPORT. > > A

Re: [VOTE] Merge HDDS-7593 (HSync and lease recovery) into master

gt; I hope this explanation makes sense. > > On Tue, Jul 30, 2024 at 10:20 AM Ethan Rose wrote: > > > Hi Wei-Chiu, I'm still unclear on the compatibility requirements of this > > feature. > > > > Feature flags are not a substitute for layout versions. Layout ver

Re: [VOTE] Apache Ozone 1.4.1 RC0

Hi Xi Chen, thanks for working on this release! I just have a few questions about the changes. - The RC has a minor Ratis version bump (3.0.1 to 3.1.0) in a patch Ozone release. This is unusual. What is the reason for this? Any concerns? - I see proto lock changes in this patch release, which is al

Re: [VOTE] Apache Ozone 1.4.1 RC0

Hi Xi Chen, sorry for not getting back to this earlier. The proto changes going out in the patch release are ok this time since there has not been another major release yet. In general this will not always be the case which is why backporting proto changes should be avoided. For example if 1.5.0 w

Re: [VOTE] Apache Ozone 1.4.1 RC0

Yes actually we should include HDDS-11040 since it fixes a compatibility regression in 1.4.0. Thanks Attila! What should I do specifically, could we update this part in the document? > We need to cherry pick this commit

Re: [VOTE] Apache Ozone 1.4.1 RC1

+1 (binding), thanks Xi Chen for updating. - Verified checksums - Verified signatures - Built from source - Checked `ozone version` output - Checked docs are included in the artifact - Tested `ozone freon ockrw` in docker - Branch structure in GitHub LGTM Ethan On Fri, Aug 16, 2024 at 1:13 AM mr

Re: [DISCUSS] Apache Ozone 1.5.0 release

+1 to start planning for 1.5.0. Our minor releases tend to take some time so it's good to start early. For any committers looking to gain more experience volunteering as release manager is a great way to do that. We have a release guide

Re: [DISCUSS] Apache Ozone 2.0 release was: Re: [DISCUSS] Apache Ozone 1.5.0 release

Thanks a lot for driving this Wei-Chiu, I'm +1 for deprecating legacy buckets and o3fs as well. The release plan will need to specify how these deprecations are implemented and what the impacts will be. For example, legacy buckets will likely remain readable and writable but creation of new ones wi

Re: [VOTE] Apache Ozone 1.4.1 RC1

Hi, any updates on the current 1.4.1 progress? Ratis 3.1.1 should be in Ozone now that HDDS-11504 is resolved. I see there’s discussion of doing a Ratis 3.1.2 to fix RATIS-2149 and RATIS-2172

Re: Ozone Community Meeting(APAC, 2024 Oct 25th)

Thanks for sharing Sammi. For deletion issues, see HDDS-11506 and its subtasks. - Proposed a key deleting service optimization, instead of iterating from > first key of the table, save last key of last iterator as the start key of > next iterator,

Re: [VOTE] Apache Ozone 1.4.1 RC2

Yes we should add a step in the guide to update the security file with the current release when a new one goes out. Thanks Nanda for catching this. I had been tracking updates required to the guide as part of this release process locally but hadn't shared anything yet. I just filed HDDS-11654

Re: [DISCUSS] bump minimum required Java

+1 for keeping java client compatible with java 8 and increasing server side minimum java version in Ozone 2.0. As for the specific version requirements for language, build, and runtime on the server side I'm not sure I have a strong opinion/enough information to weigh in on specifics right now. E

Re: [VOTE] Apache Ozone 1.4.1 RC3

+1 (binding) - Verified checksums - Verified signatures - Built from source - Checked `ozone version` output - Checked docs are included in the release and can be displayed - Tested `ozone freon ockrw` in docker Ethan On Wed, Nov 20, 2024 at 4:06 PM Siyao Meng wrote: > Good catch Ayush. It lo

Re: [VOTE] Apache Ozone 1.4.1 RC2

+1 for moving supported version list to the website and out of the release artifact. As Attila said, this is a living document so it does not really fit into immutable releases. We can find a place for it in the old and new website, but my first guess would be to put it on the downloads page which

Re: Reschedule Apache Ozone Community Sync to 8 AM PST

Sounds good, thanks Swami. It is good to sync with developers from IST in the community sync. Can you check if there are calendar invites or other pieces of documentation referring to the community sync that need to be updated with this information? Ethan On Fri, Nov 8, 2024 at 1:05 PM Abhishek P

CVE-2024-45106: Apache Ozone: Improper authentication when generating S3 secrets

the affected endpoint. This issue is being tracked as HDDS-9203 Credit: Ethan Rose (reporter) Ivan Zlenko (remediation developer) References: https://ozone.apache.org https://www.cve.org/CVERecord?id=CVE-2024-45106 https://issues.apache.org/jira/browse/HDDS-9203

Re: Reschedule Apache Ozone Community Sync to 8 AM PST

uma...@gmail.com> wrote: > > > +1 > > > > Thanks, Swami for bringing this up. > > > > Regards, > > Uma > > > > On Fri, Nov 8, 2024 at 3:36 PM Ethan Rose wrote: > > > > > Sounds good, thanks Swami. It is good to sync with dev

Re: Ozone 2.0 release update

Thanks for driving this Wei-Chiu. The GitHub discussion has references to a lot of items that were initially proposed to be included in 2.0. Can you add a comment there with which ones we are still planning to land in this release and which ones ar

Re: [VOTE] Apache Ozone 2.0.0 RC0

Thanks for working on this Wei-Chiu. Can you share the planned release notes for this release to help in the voting process? I'm not entirely sure which features did or did not make the cut, or what our compatibility guarantees are with the 1.x line. Ethan On Fri, Mar 21, 2025 at 7:02 PM Wei-Chiu

Re: [ASF] A note to projects with GitHub Discussions in use

I don't think GitHub wiki will help us. I would really like all Ozone content to be published on the new website, which would make our confluence page obsolete and we can then deprecate/remove it. Having a separate wiki anywhere creates split brain and is harder to manage. There's no clear answer f

Re: [VOTE] Apache Ozone 2.0.0 RC1

Have we run this change through the upgrade/downgrade acceptance tests yet? It would be good to know: 1. If it works with downgrade (only affects network related protos) 2. If we are supporting downgrade from the 2.x to 1.x line. There is a lot of room for improvement on the current release notes/c