search

WebAssembly / binaryen

Optimizer and compiler/toolchain library for WebAssembly
Apache License 2.0
7.4k stars 729 forks source link

Branches #313

Open kripken opened 8 years ago

kripken commented 8 years ago

The design and spec repos are moving to have a branch for each binary version on the way to 1.0, next is 0xb. Perhaps we should do the same here?

On the other hand, we have a lot more code moving around, so much higher risk of merge issues. My initial thought is that we'd target the next binary version (now, 0xb) on our master. After 0xb ships, we'd tag or branch that, so people could use it with browsers supporting that version.

jfbastien commented 8 years ago

Tags sound simpler IMO.

kripken commented 8 years ago

Yes, although if we want to backport to 0xb while working on 0xc, a branch would be nice. But maybe we can start with a tag and see.

Sounds like no concerns with master tracking the next binary format?

jfbastien commented 8 years ago

Depends how you recommend consumers work. If we want to get it for the waterfall then it'll break :-)