| OvenWerks | who reads wikis though ;) | 18:34 |
|---|---|---|
| Eickmeyer | Haha! | 18:35 |
| Eickmeyer | They already said they were looking into it. :D | 18:35 |
| Eickmeyer | Just made a new factoid for !cadence, Waiting on hggdh to add it. | 18:56 |
| Eickmeyer | If he does. | 18:56 |
| Eickmeyer | M_aD: Welcome! | 19:12 |
| M_aD | thanks :) | 19:13 |
| Eickmeyer | !cadence | OvenWerks | 19:22 |
| ubottu | OvenWerks: Cadence is an application for managing Jack in KXStudio and its repositories. Due to the nature of its intrusive configuration, it causes compatibility issues with Ubuntu's audio configuration, particularly !ubuntustudio-controls. For this reason, adding the KXStudio repos to any Ubuntu install is highly discouraged. | 19:22 |
| Eickmeyer | OvenWerks: How do you feel about changing the version numbers for our ubuntustudio-* packages to match with the current release? Like, controls 1.8 would become 19.10, etc.? | 20:11 |
| OvenWerks | Eickmeyer: what do you do if you have a bugfix inbetween? maybe more than one? | 20:16 |
| Eickmeyer | OvenWerks: That's easy. 19.10.x | 20:19 |
| Eickmeyer | So, you'd really start with 19.10.0 and work up from there. | 20:19 |
| Eickmeyer | I have been seeing other flavors do the same with their versioning, and it seems to make sense. | 20:20 |
| OvenWerks | So after 1904 releases, the next release is 19.10? | 20:25 |
| Eickmeyer | Yes. | 20:27 |
| Eickmeyer | !yymm | 20:28 |
| Eickmeyer | !yy.mm | 20:28 |
| ubottu | Ubuntu version numbers are: YY.MM (YY=release year,MM=release month). Each year sees two releases, so just specifying YY is imprecise. See also https://www.ubuntu.com/about/release-cycle | 20:28 |
| Eickmeyer | I know you knew that, but that's the ! command. | 20:28 |
| OvenWerks | So long as it doesn't cause trouble with the PTB I don't really care. It does take away some of the sense of how old the package is | 20:29 |
| Eickmeyer | Isn't that what changelogs are for? | 20:29 |
| OvenWerks | Anyway, I am not worried one way or the other... setting the version is the uploaders job ;) | 20:31 |
| Eickmeyer | Yeah, that's true. :) | 20:32 |
| OvenWerks | It would be easier to remember what feature was added when too. | 20:33 |
| Eickmeyer | That's generally my motivation. Makes support easier. | 20:33 |
| OvenWerks | A problem I can see is that the 19.* would appear twice in the package file name | 20:34 |
| OvenWerks | Would a user think "oh I acn't use 19.10 in my 18.04 install because it won't work" | 20:35 |
| Eickmeyer | !info ubuntustudio-default-settings | 20:35 |
| ubottu | ubuntustudio-default-settings (source: ubuntustudio-default-settings): default settings for the Ubuntu Studio desktop. In component universe, is optional. Version 0.65 (disco), package size 39 kB, installed size 219 kB | 20:35 |
| Eickmeyer | Are you referring to backports? | 20:36 |
| OvenWerks | yes | 20:36 |
| Eickmeyer | I shouldn't think so. Version numbers are pretty arbitrary. | 20:37 |
| OvenWerks | 1.7~ubuntu18.10.1 | 20:37 |
| Eickmeyer | ^ That only applies to Autobuilds. | 20:37 |
| OvenWerks | (for -controls) | 20:37 |
| OvenWerks | https://launchpad.net/~ubuntustudio-ppa/+archive/ubuntu/backports | 20:37 |
| Eickmeyer | Oh, I guess it would apply to backports too. | 20:37 |
| OvenWerks | Still if other people are doing it, that should be ok. | 20:38 |
| Eickmeyer | Well, then the version number would be (for Bionic backports) 19.10.0~ubuntu18.04.1 | 20:38 |
| Eickmeyer | Yeah. | 20:38 |
| OvenWerks | The user needs to think of upgrading to the 19.10 version that is ok too. | 20:39 |
| Eickmeyer | 19.10.0~ubuntu18.04.1 | 20:39 |
| Eickmeyer | ^Version ^ What it's built against | 20:39 |
| Eickmeyer | So, the important thing to match is the last number. | 20:40 |
| Eickmeyer | Also, look at KDE Apps. The version number is 18.12 landing in 19.04. | 20:40 |
| Eickmeyer | (Not plasma, but the apps) | 20:40 |
| OvenWerks | I would suggest yy.mm.sub | 20:41 |
| OvenWerks | so the mm may not match with a cycle release | 20:41 |
| Eickmeyer | .sub? | 20:41 |
| OvenWerks | sub release | 20:41 |
| Eickmeyer | Oh, yes. That's why I said 19.10.x | 20:42 |
| Eickmeyer | That way, if there are any bugfixes after upload, they can be the .x number. | 20:42 |
| OvenWerks | Anyway, Like I said, whatever the UL decides to do is fine by me. | 20:42 |
| Eickmeyer | Ok | 20:43 |
| Eickmeyer | I might run it past Ross and see what he thinks. | 20:44 |
| OvenWerks | Question: after 19.04 is released, 19.10 gets released... say in about 19.06. Then more work is done and they are also ready to release before 19.10 what is that called? | 20:45 |
| OvenWerks | or do they remain beta till cycle beta2 is past and then jump to 20.04 for new features? | 20:46 |
| Eickmeyer | It would be 19.06, but that doesn't fit the release schedule. | 20:46 |
| Eickmeyer | Beta 2 isn't a thing anymore... | 20:46 |
| OvenWerks | Till FF then | 20:47 |
| Eickmeyer | Okay. So, the only way a 19.06 would happen is if 19.04 got delayed until June. | 20:48 |
| Eickmeyer | Releases are never early for Ubuntu. | 20:48 |
| Eickmeyer | So, if 19.10 wasn't released until 20.04... I don't konw. | 20:48 |
| OvenWerks | I thik I am not being clear | 20:49 |
| Eickmeyer | I think the TB would be making that call. | 20:49 |
| Eickmeyer | Yeah, I'm confused. | 20:49 |
| OvenWerks | I am saying that rather than releasing a package inbetween cycles it may be best to keep them unreleased until FF | 20:50 |
| Eickmeyer | OvenWerks: I completely agree with that. | 20:50 |
| OvenWerks | So they are available in autobuilds before that. | 20:51 |
| Eickmeyer | The yy.mm is the target, not necessarily when it's actually released (for packages, not for Ubuntu itself). | 20:51 |
| Eickmeyer | OvenWerks: Yes. | 20:51 |
| OvenWerks | I think that should work fine. | 20:51 |
| Eickmeyer | The only reason we released anything into Backports early was because it was work-in-progress. | 20:52 |
| Eickmeyer | Cool. | 20:52 |
| Eickmeyer | I consider our backports to be stable at the moment, in terms of changes. | 20:52 |
| OvenWerks | Things have been a bit odd because installer and controls are almost like new apps and give a huge jump in feature | 20:52 |
| Eickmeyer | Right. | 20:53 |
| OvenWerks | Things will prob slow down now | 20:53 |
| Eickmeyer | We did two years' worth of updates and consolidated it into one. | 20:53 |
| Eickmeyer | I think if we did the metapackage parsing you were talking about for -installer, that would be good for 19.10 so we can squash bugs for 20.04. | 20:54 |
| Eickmeyer | And any improvements to -controls. | 20:54 |
| Eickmeyer | I'll work on theming bugs and plugin packaging. | 20:55 |
| Eickmeyer | Perhaps another wallpaper contest for 19.10 for wallpapers to land in 19.10 and 20.04. | 20:56 |
| * Eickmeyer might even bug eylul- for a fancy new 20.04 wallpaper :) | 20:56 | |
| M_aD | Honestly, i think it's time to get rid of that dark default wallpaper :) | 21:17 |
| OvenWerks | While backdrops are one of the first things I change when I install, Dark and relatively non-busy are what many artists prefer. | 21:19 |
| OvenWerks | The other thing to remember, is that we want a business to feel comfortable leaving the backdrop as is in their studio if it is music of a portrait shop | 21:20 |
| OvenWerks | In the end, it does depend on what various artists come up with | 21:37 |
| Eickmeyer | M_aD: Have you seen the new default wallpaper for 19.04? | 22:03 |
| M_aD | this one? http://ubuntustudio.org/wp-content/uploads/2019/03/1fe8/ubuntustudio_disco_dingo_1080.jpg | 22:07 |
| Eickmeyer | M_aD: Yep. Except it's in 4k from the repo. | 22:11 |
| Eickmeyer | OvenWerks, M_aD, sakrecoer: If any of you (or anyone reading this) are around, we have pre-RC images. | 22:33 |
| Eickmeyer | https://discourse.ubuntu.com/t/disco-disco-19-04-release-candidate-testing/10570 | 22:33 |
| Eickmeyer | Images at http://cdimage.ubuntu.com/ubuntustudio/dvd/20190413.1/ | 22:33 |
| Eickmeyer | I'll be shooting an email to the -devel list. | 22:34 |
| * OvenWerks is DL the image. but doesn't know when he will be able to try it. | 23:56 | |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!
