=== Lpotujovp is now known as [studio-user]-ng
=== [studio-user]-ng is now known as |studio
=== |studio is now known as |studio_user|21
=== |studio_user|21 is now known as [studio-user]-J^
[15:08] <OvenWerks> for those who can do backports... Ardour 5.0 has hit debian.
[15:09] <autumna> hi ovenwerks!
[15:10] <OvenWerks> hi.
[15:10] <sakrecoer> hi OvenWerks ! good news! :)
[15:11] <autumna> :D
[15:12] <sakrecoer> nice news features!
[15:12] <sakrecoer> https://community.ardour.org/node/13842
[15:13] <OvenWerks> Ardour 5 is very different than 4.7. The session file format changes. (5 can load 4.7 files, 4.7 can not deal with 5.0 files)
[15:14] <sakrecoer> that's good!
[15:16] <sakrecoer> easy sidechain, midi-busses, OSC... \o/
[15:16] <autumna> Lua scripting!
[15:16] <OvenWerks> OSC surface control is completely different... but much expanded.
[15:17] <sakrecoer> wow... i wonder if we can have that in before feature freeze... :p
[15:20] <autumna> what is needed to make it happen?
[15:27] <sakrecoer> not very clear to me yet... but i think it needs to be in the seeds...
[15:28] <sakrecoer> https://wiki.ubuntu.com/FeatureFreeze
[15:34] <sakrecoer> if i read this correctly, it will be synced, since we are still prior to FF https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages#Requesting_a_new_package_for_Ubuntu
[15:34] <sakrecoer> wait... FF and DIF
[15:35] <sakrecoer> oh, its the same day... https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule
[15:35] <sakrecoer> tomorrow that is...
[15:36] <sakrecoer> i guess i should poke Ross about it..
[15:41] <zequence> I will be doing uploads of all packages that have changes in them today
[15:41] <zequence> Has anything else changed apart from the seeds?
[15:41] <zequence> I could also wait until tomorrow evening, if someone wants to poke around with a package still-
[15:43] <zequence> If ardour5 is in Debian unstable, it is possible to do a sync request
[15:43] <zequence> ..after FF, that is. Otherwise it should be imported automatically before Debian Import Freeze
[15:45] <sakrecoer> zequence: we are looking into changing the default-settings
[15:45] <zequence> sakrecoer: What are you going to change?
[15:45] <sakrecoer> the theme
[15:45] <sakrecoer> from greybird to numix
[15:45] <zequence> That can be done even after FF. But, I would suggest fixing the colors before doing that
[15:46] <zequence> Theming would fall under the UI Freeze category
[15:46] <zequence> sakrecoer: So, nothing else than seeds yet?
[15:47] <sakrecoer> cool! thank you! good to know, because we are working on packaging the blue version, so it will not be ready tomorrow indeed...
[15:47] <sakrecoer> not that i can think of right now...
[15:48] <sakrecoer> zequence ^
[15:48] <zequence> Ok. I'll put up a new meta today then.
[15:49] <sakrecoer> zequence: maybe ou can shoot a mail to the list, so ross can have a chance to react?
[15:49] <zequence> Poke me whenever you need a change fixed. Last cycle we waited much too long with changes, but it was an LTS. This time there's no reasonable reason to hurry.
[15:50] <zequence> If Ross would like to change something, I'm sure he would have done it already
[15:50] <sakrecoer> cool! thank you very much zequence ! :)
[15:52]  * autumna catches up to log after dinner
[15:53] <autumna> yay (and hi zequence)
[15:53] <zequence> autumna: hi
[15:54] <zequence> Anyone tried snaps yet?
[15:54] <zequence> Would seem like ardour might be suitable as a snap.
[15:55] <autumna> zequence: why would ardour be suitable as a snap compared to another package? (asking to understand better)
[15:57] <zequence> It would be simpler to update it to the most recent version - all though I would not like to have ardour4 be replaced with ardour5. I'd rather have them installed in paralell, and that would also be possible with snaps
[15:57] <autumna> ah.. 
[15:58] <autumna> so this is in theory true for software packages? (e.g. krita, blender, etc)?
[15:59] <zequence> Yes, all of them might be easier to maintain as snaps
[15:59] <zequence> There's still a problem with drivers though, as far as graphics go, I think.
[15:59] <autumna> I see
[16:00] <autumna> so audio packages are a go, but wait on anything graphics and video, that uses.. is it just the graphic cards, or is there issues with other drivers too?
[16:00] <zequence> Think there was an issue with Blender. Something with openGL libs
[16:01] <autumna> *nods*
[16:02] <autumna> which would rule out Krita, blender, and processing too if I ever got to that
[16:02] <autumna> and possibly several other programs
[16:02] <zequence> You can find snaps with: snap find <package>
[16:03] <autumna> (krita has a snap package, but I feel like i read somewhere it too had issues? I might be wrong through)
[16:04] <autumna> I am fairly certain processing and p5.js was never packaged through. p5.js editor just came out for one thing
[16:04] <autumna> (just came out for linux)
[16:09] <zequence> Heh, someone just updated ubuntustudio-meta
[16:10] <autumna> :)))
[16:10] <zequence> It was infinity, the release manager, a Canonical employee
[16:10] <OvenWerks> I agree that installing Ardour 4 and 5 in parallel would be a good choice.
[16:12] <zequence> Apparently infinity was poking with seeds for many flavors, and decided to update them all.
[16:14] <autumna> :D
[16:29] <autumna> sakrecoer, do you think it is enough to give 1 week for final review of the website content before we declare it finished? 
[16:29] <autumna> this is after all the pages are complete
[17:07] <zequence> Major spamming on the staging site. 922 comments so far
[17:07] <zequence> Closing commenting.
[17:09] <zequence> Mail box got kind of full these past two days. Hadn't checked it for a while.
[17:31] <sakrecoer> autumna: a week from now? maybe yes, it depends on how available everyone is. but then we have to migrate it too... not too sure how that will work, but i guess we weill figure it out.
[17:31] <autumna> a week only for the review
[17:31] <autumna> as for migration, I am hoping to have a final set of plugins (we are missing a security plugin at the moment, unless the real site has something that isn't on the stage)
[17:31] <autumna> we can put the ticket in
[17:32] <autumna> for that
[17:32] <autumna> then review the content, after that either migrate
[17:32] <autumna> I mean those two can happen at same time
[17:32] <autumna> I'd really deploy the site before the release rush hits through
[17:32] <sakrecoer> either migrate, or...?
[17:32] <autumna> oh either migrate or give an extra week or two of user feedback
[17:33] <autumna> as "beta site"
[17:33] <sakrecoer> that would be a good idea. it's probably wise also to do as you say: deploy before release
[17:35] <autumna> please!
[17:35] <autumna> :D
[17:35] <autumna> so yes, I mean if we can finish our internal review and deploying of the plugins etc by end of august
[17:36] <autumna> that gives us maybe 2 weeks to calmly get feedback and deploy it to main?
[17:39] <sakrecoer> sounds fair..
[17:47] <autumna> *nods*
[17:48] <autumna> I mean as I said I am not certain we have logistics in place to do a beta open to public
[17:48] <autumna> but it is something to consider
[17:48] <autumna> anyhow I think when I finish the download page the site will be done
[17:48] <autumna> footer, check
[17:48] <autumna> social media links, check
[17:48] <autumna> merchandise page, check
[17:48] <autumna> artpage will come later.
[17:49] <autumna> oh we need to draft the forum post requesting images, so that I can uncomment the relevant bit in "contribute" section
[17:50] <autumna> sorry I am mostly thinking out loud
[17:51] <autumna> I'll email the mailing list later tonight
[18:00] <sakrecoer> thinking out loud is good (nice even), email the list is best so everyone can be in on it :)
[18:23] <autumna> will do when download page is done