[L2Ork-dev] Purr Data v.2.14.0 - JGU Release

[Jonathan Wilkes]

> Ah ok, so this is basically finished and needs review?

Well, don't quote me on that. I guess we should hear from Guillem and
his mentor for GSoC, Matt, first.

But in fact we have merged a few features that Guillem added for the
private abstractions part of his project-- namely visual notification
for dirty abstractions, and warning when more than one is dirty. That
turns out to be helpful for file-level abstractions, too.

-Jonathan

On Tue, Sep 22, 2020 at 1:42 PM Albert Graef <aggraef at gmail.com> wrote:
>
> Hi Jonathan,
>
> On Tue, Sep 22, 2020 at 6:29 PM Jonathan Wilkes <jon.w.wilkes at gmail.com> wrote:
>>
>> On Tue, Sep 22, 2020 at 7:16 AM Albert Graef <aggraef at gmail.com> wrote:
>> > You remember correctly, Guillem's branch is still WIP: https://git.purrdata.net/jwilkes/purr-data/-/merge_requests/560
>>
>> Ah, good. Sanity restored. :)
>
>
> Being the master of releases is a demanding job, that's for sure. But you're doing great, staying calm amidst all the turmoil, with everyone around you trying to lure you to their merge requests: "Come look at my MR!", "This one is ready, merge before release, please!", .... :))
>
>> I'm very curious to read the responses to the patch-private
>> abstractions Guillem designed and
>> implemented. I think he chose a sensible path for UX that will make
>> sense to current users as
>> well as being easy for new users to pick up on.
>
>
> Ah ok, so this is basically finished and needs review? I can hopefully do that later tonight or first thing tomorrow morning, after 2.14.2 is out.
>
> Joseph wrote:
>>
>> Among other things, I'm really impatient to look at Gillem's implementation of Private Abstractions which will simplify our complex patchs design.
>
>
> I think that you'll be glad to hear that I'm about to add a purr-data-preview package to the OBS, so that we have a channel to get those experimental branches into the hands of Linux users much more quickly. I think that this would help tremendously with the reviews, because then people willing to give a helping hand don't have to find and build stuff themselves, which is a big barrier for most people.
>
> In particular, Joseph, as you can't wait to try out Guillem's private abstractions, I guess that if I can upload a preview package with them, you'd be more than happy to give them a whirl and report back, right? :)
>
> Best,
> Albert
>
>> Also, I think it would be helpful to have some length of a "review
>> period" so that if there is some
>> part of that feature that needs to be changed or rethought, we can do
>> it without worrying about
>> backwards compatibility. In general that would be a nice pattern for
>> new features-- something like
>> what I tried to do with the "info" class methods, but also *actually*
>> coming back to finalize it later
>> would be even better. :)
>>
>> -Jonathan
>>
>> >
>> > Albert
>> >
>> >> -Jonathan
>> >>
>> >> >
>> >> > Thanks to All.
>> >> > Best, Joseph
>> >> > - - - - - - - - - - - - - - - - - - - -
>> >> >
>> >> > Le 22/09/2020 à 02:33, Albert Graef a écrit :
>> >> >
>> >> > Thanks Joseph, also (if I may) on behalf of the entire team and the GSoC contributors!
>> >> >
>> >> > I think that Jonathan will announce this shortly himself, but 2.14.1 is already on it's way. Jonathan has already uploaded the Mac and Windows binaries to his GH project, and I'll update my GH mirror tomorrow. Moreover, I've already uploaded the 2.14.1 source to the OBS, so Linux packages should be available there in a few hours.
>> >> >
>> >> > Best,
>> >> > Albert
>> >> >
>> >> >
>> >> > On Mon, Sep 21, 2020 at 8:31 PM Linux ROUEN Normandie <linux.rouen at free.fr> wrote:
>> >> >>
>> >> >> @Albert,
>> >> >> Thank you for having released today your JGU (Johannes Gutenberg University) package of Purr Data v.2.14.0 (Pd engine 0.48.0 + nw.js 0.24.4).
>> >> >> I just made the update from v.2.13.0 towards v.2.14.0 in a couple of minutes with no issue at all on one of my GNU/Linux systems (Linux Mint 20.0).
>> >> >>
>> >> >> @All Contributors,
>> >> >> Thanks for this new great release.
>> >> >> After few minutes of use, I'm already seeing some previous and annoying issues which are now gone.
>> >> >>
>> >> >> Best,
>> >> >> Joseph Gastelais
>> >> >>
>> >> >> _______________________________________________
>> >> >> L2Ork-dev mailing list
>> >> >> L2Ork-dev at disis.music.vt.edu
>> >> >> https://disis.music.vt.edu/listinfo/l2ork-dev
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Dr. Albert Gr"af
>> >> > Computer Music Research Group, JGU Mainz, Germany
>> >> > Email: aggraef at gmail.com, web: https://agraef.github.io/
>> >> >
>> >> > _______________________________________________
>> >> > L2Ork-dev mailing list
>> >> > L2Ork-dev at disis.music.vt.edu
>> >> > https://disis.music.vt.edu/listinfo/l2ork-dev
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > L2Ork-dev mailing list
>> >> > L2Ork-dev at disis.music.vt.edu
>> >> > https://disis.music.vt.edu/listinfo/l2ork-dev
>> >> _______________________________________________
>> >> L2Ork-dev mailing list
>> >> L2Ork-dev at disis.music.vt.edu
>> >> https://disis.music.vt.edu/listinfo/l2ork-dev
>> >
>> >
>> >
>> > --
>> > Dr. Albert Gr"af
>> > Computer Music Research Group, JGU Mainz, Germany
>> > Email: aggraef at gmail.com, web: https://agraef.github.io/
>> > _______________________________________________
>> > L2Ork-dev mailing list
>> > L2Ork-dev at disis.music.vt.edu
>> > https://disis.music.vt.edu/listinfo/l2ork-dev
>> _______________________________________________
>> L2Ork-dev mailing list
>> L2Ork-dev at disis.music.vt.edu
>> https://disis.music.vt.edu/listinfo/l2ork-dev
>
>
>
> --
> Dr. Albert Gr"af
> Computer Music Research Group, JGU Mainz, Germany
> Email: aggraef at gmail.com, web: https://agraef.github.io/
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev