Hi, Makes good sense to me. Cutting the next release as a major version reflects the high amount of change in dependencies that the downstream should expect.
-MR On October 13, 2017 at 8:58:38 AM, Angela Schreiber ( [email protected]) wrote: hi given the fact that the m12n topic is quite an effort and has major consequences for oak, i would like to propose that we discuss the option of making the next stable release from trunk a 2.0 instead of just a next 1.8. imho it would better reflect the changes if we compare it to a minor step from 1.4 to 1.6. wdyt? kind regards angela
