>> dubbo protocol fail >> 2.5.8 2.5.8 no >> 2.5.9 2.0.0(spec) >> 2.0.1(impl)(why 2.0.1?) yes >> 2.5.10 2.0.0(spec) >> 2.0.1(impl) yes >> 2.6.1 2.0.0 no >> 2.6.2 2.0.0 no >> 2.6.2 2.0.1 no
This is a compatible problem we haven’t covered in test. For users stay with 2.5.9 and 2.5.10, this will block them from upgrading to 2.6.3, so I think we should cancel vote of RC2 now and upgrade the protocol version to 2.0.2. >> It's better to document the change log of protocol versions. Agree, we definitely need a Compatibility Notice part for every upcoming release. Let’s start from 2.6.3. Best regards, Jun > On 3 Aug 2018, at 10:44, Jason Joo <[email protected]> wrote: > > add the table as image: > > <PastedGraphic-2.png> > > best regards, > > Jason > >> On Aug 3, 2018, at 10:38, Jason Joo <[email protected] >> <mailto:[email protected]>> wrote: >> >> hey, everyone >> >> Today i found a big compatible problem in our staging env. >> >> Issue has been submitted as >> https://github.com/apache/incubator-dubbo/issues/2174 >> <https://github.com/apache/incubator-dubbo/issues/2174> >> <https://github.com/apache/incubator-dubbo/issues/2174 >> <https://github.com/apache/incubator-dubbo/issues/2174>> >> >> And we can check it quickly in below table: >> >> dubbo protocol fail >> 2.5.8 2.5.8 no >> 2.5.9 2.0.0(spec) >> 2.0.1(impl)(why 2.0.1?) yes >> 2.5.10 2.0.0(spec) >> 2.0.1(impl) yes >> 2.6.1 2.0.0 no >> 2.6.2 2.0.0 no >> 2.6.2 2.0.1 no >> >> >> Maybe the best way to solve this is to patch 2.6.3(just released) and change >> it to "2.0.2" >> >> Any opinion? >> >> It's better to document the change log of protocol versions. >> >> >> best regards, >> >> Jason >> >
