Dalba added a comment.
In T106121#3962754, @Dvorapa wrote:
But I personally more like 3.1.20180212 (major.incompatibility.stamp).
Under semver any incompatibility in API is considered a major change. In a major.incompatibility.stamp scheme, what kind of change will be associated with major versi
Xqt triaged this task as "Normal" priority.
TASK DETAILhttps://phabricator.wikimedia.org/T187009EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: XqtCc: gerritbot, Aklapper, pywikibot-bugs-list, Dvorapa, Cpaulf30, Ivana_Isadora, Jayprakash12345, Magul, Tbscho, r
Xqt added a comment.
I agree with Dalba. I've no idea for what the major release stands except 1.0 means trunk, 2.0 means the interim rewrite stable branch and 3 the current master which never will change in future except we have a complete code redesign.
I think semver release counting is wellkno
Dvorapa added a comment.
OK. I'm not against semver, I used it a lot in some of my older projects so I can see some serious questions we should solve before presenting this change: How this change will affect the developers? Will we require to increment PATCH number for every bugfix made and MINOR
Dalba added a comment.
In T106121#3967489, @Dvorapa wrote:
Will we require to increment PATCH number for every bugfix made and MINOR for every improvement?
Based on our current release cycle, I presume that we can keep developing on the dev (pre-release) version. The person who is going to updat
Lokal_Profil added a comment.
In T106121#3968520, @Dalba wrote:
The person who is going to update the changelog and do the release, should look at the changes since the last release and bump the version accordingly.
Do we have anyone/anyones willing to take that on? If I understand the pywik
.avgas added a comment.
Hi @Zoranzoki21, bot returned that error at different time, along many days. How could -pt:0 solve it?TASK DETAILhttps://phabricator.wikimedia.org/T187087EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: .avgasCc: Zoranzoki21, Aklapper,
Zoranzoki21 added a comment.
In T187087#3969058, @.avgas wrote:
Hi @Zoranzoki21, bot returned that error at different time, along many days. How could -pt:0 solve it?
This will maybe help to bot no return errors and to work without problems. On my wiki it is resolved problem like this.TASK DETA
Dvorapa added a project: Pywikibot-core.
TASK DETAILhttps://phabricator.wikimedia.org/T187087EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: DvorapaCc: Zoranzoki21, Aklapper, pywikibot-bugs-list, .avgas, Magul, Tbscho, rafidaslam, MayS, Mdupont, JJMC89, Avicen
Xqt added a comment.
In T106121#3968993, @Lokal_Profil wrote:
Do we have anyone/anyones willing to take that on?
I did it several times in past and it is very easy to do it with master branch in opposite to the previous so called stable release 2.0.
If I understand the pywikibot history cor
10 matches
Mail list logo
