> These fixes will either be accepted for 1.1.x or for 2.0.x but IMO they > shouldn't be backported to the 0.20/1.0 branch. 1.0 should be bug-compatible > with what we have.
Let's be really specific here, because writing "1.0 should be bug-compatible with what we have" is ambiguous. Do you mean that 1.x.y (all versions with major number 1) should be bug-compatible with what we have? or do you mean that 1.0.x (all versions with major number 1 and minor number 0) should be bug-compatible with what we have? Each has very different meanings. Here is what I understand from what we discussed: * After 1.0 is released, any versions along the 1.x branch will not break backwards compatibility. * ... unless there is a good reason to break backwards compatibility, then we will do so with a new minor release (i.e. 1.1, 1.2, etc.) These compiler bugs that require a breaking change which @GULPF refers to **should be fixed now** , before 1.0 is released. Otherwise 1.0 doesn't mean much, as we will have plenty of breaking changes in Nim 1.1, 1.2 etc. which IMO is just dishonest. Let's reserve the right to do this, but **only** for really major things, like security issues.
