Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[qvto-dev] Post Photon version numbering/naming/planning

Hi

(email to qvto-dev; similar discussion applies to OCL and QVTd.)

Photon is the last yearly simultaneous release with quarterly maintenance releases. SimRel moves to three monthly releases with no maintenance. Names are now "Eclipse SimRel YYYY-MM". See https://bugs.eclipse.org/bugs/show_bug.cgi?id=532220

Retrospectively I think we can start to refer to e.g. QVTo 3.7.0 as "Eclipse QVTo 2017 (3.7.0 for Oxygen)".

Going forward, we do not seem to have adequate committer activity for four minor version releases per year.

Pragmatically is the policy for each 3 monthly release?

  • Contribute a, possibly no-change, maintenance release if nothing significant has happened. A rebuild is almost mandatory to ensure that the latest Orbit etc is in use.
  • Contribute a minor release if something minor has happened.
  • Contribute a major release if something major has happened. In practice an EMF API evolution. One day for a Pivot OCL-based QVTo.

Planning. No planning. Everyone just does whatever they can whenever they can, hopefully letting others know in advance via qvto-dev and/or Bugzillas.

Therefore what we contribute in September will likely be "Eclipse QVTo 2018-09 (3.8.1)" but might be "Eclipse QVTo 2018-09 (3.9.0)"

Any better ideas on how to comply with the new policy with limited committer activity?

    Regards

        Ed Willink


Virus-free. www.avast.com

Back to the top