SBE 2.0 Tracker about fix-simple-binary-encoding HOT 6 CLOSED

SBE version 1.0 has reached Technical Standard status and therefore, it is now immutable. Changes may only be made to subsequent versions of SBE, including proposed 2.0 (and later if necessary). Each version must go through the FIX technical standardization process.

from fix-simple-binary-encoding.

Fair enough, changed SBE 1.0 to SBE 1.1

We need to delineate the minor clarifications requested in the specification for SBE 1.0 which would morph into SBE 1.1 versus the changes which are not backward compatible with SBE 1.0 in SBE 2.0

from fix-simple-binary-encoding.

Aditya, you are apparently proposing to create two new standard versions simultaneously. Both would have to go through the standardization process of release candidate -> draft standard -> standard. I question whether we would want to commit resources to do that and what benefits it would have. It seems to me that it would likely cause fragmentation of implementations like you see with Android.

Also, issue #35 resulted in a change to the XML schema, so it would not be back compatible with version 1.0.

To be discussed on the High Performance Working Group meeting on June 14. I would like to hear other opinions on this.

from fix-simple-binary-encoding.

I cannot join next week's call but am concerned about the value or better the negative potential. If we want the community to move to 2.0 (or to start with 2.0) then it is dangerous to offer enhancements by means of 1.x versions. Version 1.0 is the base version which is ready to use. The "installed base" of SBE is very small and we do not want a split of non-interoperable implementations. Clarifications of 1.0 are useful and only depend on the available resources but that would be a 1.01 and not a 1.1 for me. Communication strategy is important here.

from fix-simple-binary-encoding.

Oh okay I see, I am not strongly wedded to the concept of SBE 1.1 and have removed any reference to it. We can all hop on the SBE 2.0 train going forward. My only goal was to jump start this and move it forward. We can certainly discuss this further.

Don, I will not be able to join on wednesday and even Hanno will not be available. Not sure if we should cancel or reschedule it to another day just for this one time

from fix-simple-binary-encoding.

For future releases, we can use GitHub Projects and Milestones features for tracking themes and groups of issues since they can be managed dynamically.

from fix-simple-binary-encoding.