I just realized from the list that there's a pretty serious bug that's already fixed in git but not in Pd 0.52-0 ... I think it's worth putting out a bugfix version. My plan then would be to merge the latest running updates and some of Alexandre's documentation updates and then release a testing version this weekend. Are there other updates that need to make their way into Pd 0.52-1? (No improvements please, just bug fixes :)
Miller
Hey, cool!
Em qui., 13 de out. de 2022 às 23:26, Miller Puckette via Pd-dev < pd-dev@lists.iem.at> escreveu:
My plan then would be to merge the latest running updates and some of Alexandre's documentation updates
why not all? :)
and then release a testing version this weekend. Are there other updates that need to make their way into Pd 0.52-1? (No improvements please, just bug fixes :)
I got a couple of simple PRs labeled as bug fixes sitting there - https://github.com/pure-data/pure-data/pull/1683 - https://github.com/pure-data/pure-data/pull/1618
I also see things labeled as "improvement", one is the latest deken version, which I guess must be included - https://github.com/pure-data/pure-data/pull/1736
I also have some PRs of mine marked as improvements, and I consider this one to be actually a bug fix - https://github.com/pure-data/pure-data/pull/1581
Although these two are also marked as improvements, they seem like no brainers and things that could have been part of the "development" branch, so please consider them. - https://github.com/pure-data/pure-data/pull/1635 - https://github.com/pure-data/pure-data/pull/1034
Thanks!
Em sex., 14 de out. de 2022 às 01:21, Alexandre Torres Porres < porres@gmail.com> escreveu:
I got a couple of simple PRs labeled as bug fixes sitting there
Both above had conflicts that I have now resolved so they're ready to merge. Would you consider merging them now Miller?
Thanks
Note that my documentation branch also has some new last commits for the release as well. I don't have anything else in the horizon now to add here. https://github.com/pure-data/pure-data/pull/1770
Em seg., 17 de out. de 2022 às 17:51, Alexandre Torres Porres < porres@gmail.com> escreveu:
Em sex., 14 de out. de 2022 às 01:21, Alexandre Torres Porres < porres@gmail.com> escreveu:
I got a couple of simple PRs labeled as bug fixes sitting there
Both above had conflicts that I have now resolved so they're ready to merge. Would you consider merging them now Miller?
Thanks
note that #1635 has conflicts; I think it has been made obsolete by the recent rework of the interface to GUI (probably should be closed).
Antoine
Le ven. 14 oct. 2022 à 06:23, Alexandre Torres Porres porres@gmail.com a écrit :
Em qui., 13 de out. de 2022 às 23:26, Miller Puckette via Pd-dev < pd-dev@lists.iem.at> escreveu:
Are there other updates that need to make their way into Pd 0.52-1?
btw, I was checking, current version is 0.52-2, so the bugfix update would be 0.52-3, right?
cheers
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Am 14. Oktober 2022 15:32:42 MESZ schrieb Antoine Rousseau antoine@metalu.net:
has been made obsolete by the recent rework of the interface to GUI
Speaking of which: I think a bugfix release 0.52.3 should probably *not* contain the "rework of the interface to GUI", which is a rather big change...
mfg.sfg.jfd IOhannes
Am 14. Oktober 2022 17:12:02 MESZ schrieb "IOhannes m zmölnig" zmoelnig@iem.at:
Speaking of which: I think a bugfix release 0.52.3 should probably *not* contain the "rework of the interface to GUI", which is a rather big change...
Also I see that my deken update branch has been merged, which is great. But it includes mostly new features, rather than just bugfixes.
So are we aiming at 0.53.0 or at 0.52.3?
mfg.sfg.jfd IOhannes
I _think_ the deken update won't break anything (after all you don't have to use it to run Pd) - so I think it's worth the risk of updating it.
Also, the GUI changes would be hard to untangle from the other updates, so I think the safer thing is to just leave them in. As far as I can tell they're adequately shaken down now.
Even though it's not considered correct behavior, I still find it less problematic to fully commit to changes in the main branch than to try to maintain long twisted chains of duplicate bugfixes in both master and in some 0.52 branch - this didn't work out so well this time around (I cornered myself into taking the GUI updates into a minor release) but, ouch, we all just have to deal with my 1970s-vintage coding skills :)
M
On Fri, Oct 14, 2022 at 05:18:58PM +0200, IOhannes m zmölnig wrote:
Am 14. Oktober 2022 17:12:02 MESZ schrieb "IOhannes m zmölnig" zmoelnig@iem.at:
Speaking of which: I think a bugfix release 0.52.3 should probably *not* contain the "rework of the interface to GUI", which is a rather big change...
Also I see that my deken update branch has been merged, which is great. But it includes mostly new features, rather than just bugfixes.
So are we aiming at 0.53.0 or at 0.52.3?
mfg.sfg.jfd IOhannes
Pd-dev mailing list Pd-dev@lists.iem.at https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-dev__;!!...
Em sex., 14 de out. de 2022 às 12:12, IOhannes m zmölnig zmoelnig@iem.at escreveu:
Am 14. Oktober 2022 15:32:42 MESZ schrieb Antoine Rousseau < antoine@metalu.net>:
has been made obsolete by the recent rework of the interface to GUI
Speaking of which: I think a bugfix release 0.52.3 should probably *not* contain the "rework of the interface to GUI", which is a rather big change...
Why not? We're talking about things that had already been merged before, right? It seems to me most changes are "under the hood" and not proper new features. I also see that as numerous bug fixes. The only new feature is the 'orientation' message to sliders/radio buttons. But yeah, I think I might be missing your point/reasons to assume this should be considered a new version instead.
cheers
mfg.sfg.jfd IOhannes
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Am 14. Oktober 2022 18:13:00 MESZ schrieb Alexandre Torres Porres porres@gmail.com:
Em sex., 14 de out. de 2022 às 12:12, IOhannes m zmölnig zmoelnig@iem.at escreveu:
Am 14. Oktober 2022 15:32:42 MESZ schrieb Antoine Rousseau < antoine@metalu.net>:
has been made obsolete by the recent rework of the interface to GUI
Speaking of which: I think a bugfix release 0.52.3 should probably *not* contain the "rework of the interface to GUI", which is a rather big change...
Why not? We're talking about things that had already been merged before,
So what?
i'm not really sure i understand what you mean exactly with "have been merged before". the fact that the PRs have already been merged into master? how is that related to "bugfix release"?
right? It seems to me most changes are "under the hood" and not proper new features.
And all of them include regressions.
imho, a "bugfix release" is a promise to the user that says "nothing has changed with respect to the previous release, except we fixed these annoying bugs". so i worry not about "features" but about "anything not a bugfix".
and with 0.52-3, plenty of things have changed (and a few annoying bugs have been fixed as well). ~70 C-files have been modified, and 3 header files have been modified (suggesting additions to the API)
so i just fail to understand why we can't just call it "0.53-0", as this clearly is beyond a "bugfix" release.
i'm probably highly influenced by semantic versioning [1], which is targetting versioning for libraries (API/ABI compatibility) rather than applications, but i think the model is so great that it can be applied to any software (that is not released very frequently).
in any case: i'm not the one who is deciding on the versioning.
gfmdsa IOhannes
Hello,
On 15.10.22 22:00, IOhannes m zmölnig wrote:
imho, a "bugfix release" is a promise to the user that says "nothing has changed with respect to the previous release, except we fixed these annoying bugs". so i worry not about "features" but about "anything not a bugfix".
and with 0.52-3, plenty of things have changed (and a few annoying bugs have been fixed as well). ~70 C-files have been modified, and 3 header files have been modified (suggesting additions to the API)
so i just fail to understand why we can't just call it "0.53-0", as this clearly is beyond a "bugfix" release.
I fully agree with IOhannes. Someone may need a bugfix for their concert next week and they are positively surprised by getting this bugfix just in time, while being negatively surprised by the regression during their performance. Signalling big changes by version number is a good thing.
Not every user read the release info or changelog, as to most this is unintelligable gibberish (What exactly does "rework of GUI code" mean to an end user?)
Just my 0,02€, Thomas
OK, I'm convinced. Anyhow there are plenty of possible version numbers left :)
Another reason could be that I'm unable to do as much testing myself as usual.
A minor inconvenience is that the older-mac compiles will have to wait until I can get back to my usual lair.
cheers Miller
On Sun, Oct 16, 2022 at 03:09:52PM +0200, Thomas Mayer wrote:
Hello,
On 15.10.22 22:00, IOhannes m zmölnig wrote:
imho, a "bugfix release" is a promise to the user that says "nothing has changed with respect to the previous release, except we fixed these annoying bugs". so i worry not about "features" but about "anything not a bugfix".
and with 0.52-3, plenty of things have changed (and a few annoying bugs have been fixed as well). ~70 C-files have been modified, and 3 header files have been modified (suggesting additions to the API)
so i just fail to understand why we can't just call it "0.53-0", as this clearly is beyond a "bugfix" release.
I fully agree with IOhannes. Someone may need a bugfix for their concert next week and they are positively surprised by getting this bugfix just in time, while being negatively surprised by the regression during their performance. Signalling big changes by version number is a good thing.
Not every user read the release info or changelog, as to most this is unintelligable gibberish (What exactly does "rework of GUI code" mean to an end user?)
Just my 0,02€, Thomas -- "Prisons are needed only to provide the illusion that courts and police are effective. They're a kind of job insurance." (Leto II. in: Frank Herbert, God Emperor of Dune) https://urldefense.com/v3/__http://www.residuum.org/__;!!Mih3wA!AVIbE0_v1-MH...
Pd-dev mailing list Pd-dev@lists.iem.at https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-dev__;!!...
Em dom., 16 de out. de 2022 às 11:59, Miller Puckette via Pd-dev < pd-dev@lists.iem.at> escreveu:
OK, I'm convinced. Anyhow there are plenty of possible version numbers left :)
Does this mean we're getting the same update now but as 0.53-0?
Another reason could be that I'm unable to do as much testing myself as usual.
A minor inconvenience is that the older-mac compiles will have to wait until I can get back to my usual lair.
I still can't see the new test compilations up in your website. What about those? I think older mac versions (32 bits) are very rarely used these days.
cheers Miller
On Sun, Oct 16, 2022 at 03:09:52PM +0200, Thomas Mayer wrote:
Hello,
On 15.10.22 22:00, IOhannes m zmölnig wrote:
imho, a "bugfix release" is a promise to the user that says "nothing
has
changed with respect to the previous release, except we fixed these annoying bugs". so i worry not about "features" but about "anything not a bugfix".
and with 0.52-3, plenty of things have changed (and a few annoying bugs have been fixed as well). ~70 C-files have been modified, and 3 header files have been modified (suggesting additions to the API)
so i just fail to understand why we can't just call it "0.53-0", as
this
clearly is beyond a "bugfix" release.
I fully agree with IOhannes. Someone may need a bugfix for their concert next week and they are positively surprised by getting this bugfix just
in
time, while being negatively surprised by the regression during their performance. Signalling big changes by version number is a good thing.
Not every user read the release info or changelog, as to most this is unintelligable gibberish (What exactly does "rework of GUI code" mean to
an
end user?)
Just my 0,02€, Thomas -- "Prisons are needed only to provide the illusion that courts and police are effective. They're a kind of job insurance." (Leto II. in: Frank Herbert, God Emperor of Dune)
https://urldefense.com/v3/__http://www.residuum.org/__;!!Mih3wA!AVIbE0_v1-MH...
Pd-dev mailing list Pd-dev@lists.iem.at
https://urldefense.com/v3/__https://lists.puredata.info/listinfo/pd-dev__;!!...
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
On 10/16/22 16:58, Miller Puckette via Pd-dev wrote:
OK, I'm convinced. Anyhow there are plenty of possible version numbers left :)
:-)
i see you have merged another round of PRs.
do you have an estimate on when the release is going to happen? i'm mainly asking because of the translations, which currently have gained a bit of momentum (dutch, french, german, korean, brazilean portuguese and russion are now complete; spanish almost; canadian english, italian and hungarian have also considerable portions translated). i thought about pushing the ukrainian translation a bit.
in any case, it would be great to have an approx schedule, so i can prepare an updated i18n branch in time.
mgfyfx IOhannes
What are the regressions? I could only see bug fixes.
Em sáb., 15 de out. de 2022 às 17:01, IOhannes m zmölnig zmoelnig@iem.at escreveu:
Am 14. Oktober 2022 18:13:00 MESZ schrieb Alexandre Torres Porres porres@gmail.com:
Em sex., 14 de out. de 2022 às 12:12, IOhannes m zmölnig <zmoelnig@iem.at
escreveu:
Am 14. Oktober 2022 15:32:42 MESZ schrieb Antoine Rousseau < antoine@metalu.net>:
has been made obsolete by the recent rework of the interface to GUI
Speaking of which: I think a bugfix release 0.52.3 should probably *not* contain the "rework of the interface to GUI", which is a rather big change...
Why not? We're talking about things that had already been merged before,
So what?
i'm not really sure i understand what you mean exactly with "have been merged before". the fact that the PRs have already been merged into master? how is that related to "bugfix release"?
right? It seems to me most changes are "under the hood" and not proper new features.
And all of them include regressions.
imho, a "bugfix release" is a promise to the user that says "nothing has changed with respect to the previous release, except we fixed these annoying bugs". so i worry not about "features" but about "anything not a bugfix".
and with 0.52-3, plenty of things have changed (and a few annoying bugs have been fixed as well). ~70 C-files have been modified, and 3 header files have been modified (suggesting additions to the API)
so i just fail to understand why we can't just call it "0.53-0", as this clearly is beyond a "bugfix" release.
i'm probably highly influenced by semantic versioning [1], which is targetting versioning for libraries (API/ABI compatibility) rather than applications, but i think the model is so great that it can be applied to any software (that is not released very frequently).
in any case: i'm not the one who is deciding on the versioning.
gfmdsa IOhannes
[1] https://semver.org/ _______________________________________________ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
I guess I don't understand the meaning of 'regression' actually.
Anyway, I see some of my help files updates were considering 0.53, like the unification of sliders, so yeah, even though there's not much new, there it is :)
Em dom., 16 de out. de 2022 às 13:47, Alexandre Torres Porres < porres@gmail.com> escreveu:
What are the regressions? I could only see bug fixes.
Em sáb., 15 de out. de 2022 às 17:01, IOhannes m zmölnig zmoelnig@iem.at escreveu:
Am 14. Oktober 2022 18:13:00 MESZ schrieb Alexandre Torres Porres porres@gmail.com:
Em sex., 14 de out. de 2022 às 12:12, IOhannes m zmölnig <
zmoelnig@iem.at>
escreveu:
Am 14. Oktober 2022 15:32:42 MESZ schrieb Antoine Rousseau < antoine@metalu.net>:
has been made obsolete by the recent rework of the interface to GUI
Speaking of which: I think a bugfix release 0.52.3 should probably
*not*
contain the "rework of the interface to GUI", which is a rather big change...
Why not? We're talking about things that had already been merged before,
So what?
i'm not really sure i understand what you mean exactly with "have been merged before". the fact that the PRs have already been merged into master? how is that related to "bugfix release"?
right? It seems to me most changes are "under the hood" and not proper
new
features.
And all of them include regressions.
imho, a "bugfix release" is a promise to the user that says "nothing has changed with respect to the previous release, except we fixed these annoying bugs". so i worry not about "features" but about "anything not a bugfix".
and with 0.52-3, plenty of things have changed (and a few annoying bugs have been fixed as well). ~70 C-files have been modified, and 3 header files have been modified (suggesting additions to the API)
so i just fail to understand why we can't just call it "0.53-0", as this clearly is beyond a "bugfix" release.
i'm probably highly influenced by semantic versioning [1], which is targetting versioning for libraries (API/ABI compatibility) rather than applications, but i think the model is so great that it can be applied to any software (that is not released very frequently).
in any case: i'm not the one who is deciding on the versioning.
gfmdsa IOhannes
[1] https://semver.org/ _______________________________________________ Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Em sex., 14 de out. de 2022 às 10:33, Antoine Rousseau antoine@metalu.net escreveu:
note that #1635 has conflicts; I think it has been made obsolete by the recent rework of the interface to GUI (probably should be closed).
Hmm, I'll have a look, thanks
Antoine
Le ven. 14 oct. 2022 à 06:23, Alexandre Torres Porres porres@gmail.com a écrit :
Em qui., 13 de out. de 2022 às 23:26, Miller Puckette via Pd-dev < pd-dev@lists.iem.at> escreveu:
Are there other updates that need to make their way into Pd 0.52-1?
btw, I was checking, current version is 0.52-2, so the bugfix update would be 0.52-3, right?
cheers
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Em sex., 14 de out. de 2022 às 10:33, Antoine Rousseau antoine@metalu.net escreveu:
note that #1635 has conflicts; I think it has been made obsolete by the recent rework of the interface to GUI (probably should be closed).
I see objects are now moved via the "move" command, but not graphs as in my PR. I may close it but will keep the issue opened or reboot it
Antoine
Le ven. 14 oct. 2022 à 06:23, Alexandre Torres Porres porres@gmail.com a écrit :
Em qui., 13 de out. de 2022 às 23:26, Miller Puckette via Pd-dev < pd-dev@lists.iem.at> escreveu:
Are there other updates that need to make their way into Pd 0.52-1?
btw, I was checking, current version is 0.52-2, so the bugfix update would be 0.52-3, right?
cheers
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
-
Alexandre Torres Porres -
Antoine Rousseau -
IOhannes m zmölnig -
Miller Puckette -
Thomas Mayer