Is there a general date for the first 0.48 test release?
I want to update the install & build instructions before this gets out.
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
I'm just thinking about this. I think I want to "freeze" things July 14 (Bastille Day) or thereabouts, and make a "pd-0.48" branch then. (Heretofoore I've been making branches only if I wanted to go back and fix bugs, but I think its better practice to do that when ready to stop adding stuff).
At that point I can keep on merrily applying PRs to the main branch but only apply bug fix and documentation PRs to the 0.48 branch. So that would suggest getting any functional changes in over the next 2 weeks, then any doc updates before the (hoped for) finalization date Aug. 1.
cheers Miller
On Mon, Jul 03, 2017 at 12:12:54AM +0200, Dan Wilcox wrote:
Is there a general date for the first 0.48 test release?
I want to update the install & build instructions before this gets out.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
2017-07-02 19:26 GMT-03:00 Miller Puckette msp@ucsd.edu:
I'm just thinking about this. I think I want to "freeze" things July 14 (Bastille Day) or thereabouts, and make a "pd-0.48" branch then. (Heretofoore I've been making branches only if I wanted to go back and fix bugs, but I think its better practice to do that when ready to stop adding stuff).
Let me see if I get it correctly, you mean stop with feature additions by july 14th, and then have another 2 weeks of fixing bugs related to the features added? Or do you mean stop with the new stuff but keep working on bug fixes and other things?
There are at least a couple of bug fixes that I really hope could happen for 0.48 - one of which I was trying to fix with Matt Barber ([nbx] not displaying 'nan' anymore). I ask all this just so I can plan for it.
cheers
Well, [nbx] is itself a bug :)
Anyway, I mean, fixes to new and old bugs anytime - except that, late in the game I'd like to avoid bug fixes that could possibly lead to more bugs. I don't know how to judge that except intuitively.
cheers Miller
On Sun, Jul 02, 2017 at 08:13:25PM -0300, Alexandre Torres Porres wrote:
2017-07-02 19:26 GMT-03:00 Miller Puckette msp@ucsd.edu:
I'm just thinking about this. I think I want to "freeze" things July 14 (Bastille Day) or thereabouts, and make a "pd-0.48" branch then. (Heretofoore I've been making branches only if I wanted to go back and fix bugs, but I think its better practice to do that when ready to stop adding stuff).
Let me see if I get it correctly, you mean stop with feature additions by july 14th, and then have another 2 weeks of fixing bugs related to the features added? Or do you mean stop with the new stuff but keep working on bug fixes and other things?
There are at least a couple of bug fixes that I really hope could happen for 0.48 - one of which I was trying to fix with Matt Barber ([nbx] not displaying 'nan' anymore). I ask all this just so I can plan for it.
cheers
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
2017-07-02 20:16 GMT-03:00 Miller Puckette msp@ucsd.edu:
Well, [nbx] is itself a bug :)
haha, we were hoping it wasn't too crazy as we thought, and that the dev list could help us, but this discouraging :)
there was a change that led to this bug, and it is weird now that even reverting it back doesn't fix it. We'll check a bit more on it and come here for help if we don't go anywhere.
cheers
-
Alexandre Torres Porres -
Dan Wilcox -
Miller Puckette