Developers of Sympa

[Marc Chantreux <address@concealed>]

hello,

semantic versioning for sympa7 was acted during the
hackathon but what about the 6.* ?

* some of us just can't trust the current so called
  stable release because of the lack of beta cycle.
  stability is very important for very large
  organizations using sympa. Soji does a great job
  providing assistance on github but obviously, he
  can't catch every flaws so we need a real beta cycle
  time.
* also those very large organizations cannot afford
  a very to update to every new stable release
  (damn true when instability and regressions are in
  the corner) so i still think we we need to slow
  down the release cycle.
* on the other side, maybe some little sites can
  handle the release pace of 6.2
* the lack of beta cycle is a problem

i was thinking about a way to improve the situation
with the current release cycle. that's my proposal:

* Soji moves from 6.2 to 6.3, releasing the pace that
  sounds good for him.
* Whenever something is know up and running fine
  by large sites who want to contribute to beta test
  (universalistes for sure but we can ask for friends
  to jump in...  framalist, unistra, ...), we pick that
  version to become a 6.4.something.
* whenever there is a breaking change, we can increment
  the minor.

i see avantages:

* semantic versionning for sympa6 (so newcomers are not
  confused about to )
* let Soji run the pace he wants but trying to avoid
  the problems he can't handle by his own.

regards,
marc