Going 1.0

[jlecour]

Hi,

RailsConfig has been quite stale for many month : only a handful of commits during the last year, almost no issue closed, …

Maybe it's a good time to evaluate the most important open issues and try to solve them then release a 1.0 version.

A piece of software, used by many in production for a long time, can't really stay in 0.x forever.
Plus, it might never be perfectly bug free and feature complete, but the life of project doesn't stop at 1.0.

FInally, according to SemVer semantics, marking a 1.0 release is a strong indication that the public API is stable (until 2.0) and is trusted to be used in production.

What do you think about that

[pkuczynski]

I am working on this...

[gdlx]

Many major gems are in 0.x: i18n=>0.6, oauth=>0.4, pry=>0.10, mysql2=>0.3, rails-api=>0.2, ...
Bumping 1.0 should not be a target but should reflect a mature and stable project.
Keeping 0.x indicates to the user "The API could change anytime, don't upgrade without testing".
Bumping 1.0 means the dev team will have to maintain 1.x while working on 2.0, which requires a lot of time and commitment...many small teams cannot afford this.

I prefer to stuck on =0.x.y than trusting a ~>1.0.0 branch that cannot guarantee the absence of regression...