Ladsgroup added a comment.

(I was subscribed so I make a note) Release engineering for pywikibot needs some work. We have three options here:

  • Going after semver (See http://semver.org/). So only major version change when there is a breaking change and minor change for minor ones. It's PEP440 compatible.
  • Going after year.month system. So pywikibot at end of January will be released as "pywikibot 2017.1". It's closer to WMF release engineering system and PEP440 compatible.
  • We can use WMF release engineering system. So at end of each of week a new release comes out (except weeks without deploy such as this week) and with the exact same number of mediawiki (see this for example) The biggest upside of this method is to being synced with mediawiki, so for example if a third party is running mediawiki core 1.29-wmf.1 he/she knows exactly what version of pywikibot to choose. And if mediawiki introduces a breaking change (which it does all the time) we can be synced too easily.

TASK DETAIL
https://phabricator.wikimedia.org/T106121

EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Xqt, Ladsgroup
Cc: Ladsgroup, Magul, TerraCodes, Legoktm, Luke081515, hashar, Jay8g, Dalba, Lokal_Profil, StudiesWorld, Multichill, valhallasw, jayvdb, XZise, Ricordisamoa, Aklapper, Xqt, pywikibot-bugs-list, Tbscho, MayS, Mdupont, JJMC89, fbstj, Masti, Alchimista, Rxy
_______________________________________________
pywikibot-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs

Reply via email to