| Magul added a comment. |
In T106121#2892478, @Multichill wrote:I don't agree. The whole thing with releases is just a giant time sink. We just killed off compat to not have to worry about multiple versions any more. I'd rather have people spend time on improving Pywikibot and fixing bugs, than waste time on some release nobody uses anyway. No, I'm not going to pin on some old version. Pywikibot you run on master. If you run into an issue, you update it to the latest version. If you run into the same issue again, you file a bug and get it fixed. If people are not able to do a simple git clone/git pull, they shouldn't be running Pywikibot at all (or just http://paws.wmflabs.org/).
We tried releases, we failed, let's abandon it.
Maybe it's my personal bias here, but I started contributing here, because I was trying to use PWB by myself, and obvious choise for me to install it was via pip and requests.txt in my project. I believe it's the most common way, how Python community is installing packages right now. That's the main reason that I'm advocating for releasing it in PyPI. Regarding Your argument about "time sink" I'm not trying to persuade anybody here to support old versions already released by PyPI. I would just release newer version in frequent cycle and suggest anybody to upgrade installed version to newer one. As You can see also e.g. in T152907 I'm not the only person, that would use PyPI package. From Your perspective (cloning/fetching/pulling from git) there is no problem, that there is release in PyPI and I could find one hour a month to release current tip of master branch.
In T106121#2893254, @Ladsgroup wrote:(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.
I would suggest here second option. It's clear and simple and first and third one require a little bit more work to be done.
BTW @Ladsgroup, I we have Your attention, could You add me (and maybe others) to owners group of Pywikibot on PyPI test index (https://testpypi.python.org/pypi/pywikibot/2.0rc1.post2). My login there is magul.
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
