Proposal: Foreman 1.XX = 2.0 (a new one)

I think there is misunderstanding and the thread deviated to 2.0 feature discussion. This is not core of my proposal, I explicitly do not want to do feature talk. There will always be something that we would like to have in version X.Y. What I propose is:

A) Let's do 2.0 instead 1.17 regardless of features
B) Let's do 2.0 instead 1.18 regardless of features
C) Let's do 2.0 instead 1.19 regardless of features
D) I want to stick with 1.X, talk about feature-driven release management or simply decide later

And it's totally fair if you guys prefer to talk about features and decide later. This is just my attempt to set the direction back, but it looks like I already know where this is going anyways :-)

At least I tried and opened the discussion so we don't hit the wall of "twenty"...


··· --
Later,
  Lukas @lzap Zapletal
Ok, gmail did not refresh me the thread, I was reading old posts.

D) I want to stick with 1.X, talk about feature-driven release
management or simply decide later
It looks like majority want to continue the discussion, please carry on there.

There are some voices that vertical nav with Rails 5.x might be a good reason to do 2.0, but Eric preferred also to include V1 drop.

Also one interesting remark was that we don't need to rush and it does not make any huge difference if we switch 1.17 or 1.19, that's also worth mentioning.

That's for the summary.


··· --
Later,
  Lukas @lzap Zapletal