Re: [ubuntu-studio-devel] Backports
On Fri, 27 May 2016 13:46:20 -0700 (PDT), Len Ovens wrote: >On Fri, 27 May 2016, lukefro...@hushmail.com wrote: > >> In the case of Kdenlive, versions 15.08 and later use a different >> file format. They can read an old project but cannot save back to >> the old format, saving to the new and renaming the old one as a >> backup. If the user deletes the backup, then reverts Kdenlive >> versions 15.04 and earlier cannot open the file written by the later >> version. Fortunately Kdenlive will warn of that and tell the user >> about the backup file, > >Ardour 5.* will be the same (already is in GIT). Ardour 3 and 4 are >interchangable (with some oddities- 4.1 intruduces trim) 5 takes old >sessions ok but the reverse is not true, the old style is kept as a >snapshot. Unfortunately editing the Ubuntu Wiki/help pages requires to subscribe to a special group now, so I won't write such a page. However, the information computer newbies need is very simple. Major releases always should be backwards compatible and should be without regressions, IOW 1.1, 1.2, 1.3 should be backwards-compatible. >From one major release to another no backwards-compatibility should be expected. IOW version numbers are not random numbers, they usually make sense. A good exception is the kernel, it might not be backwards-compatible, that's why rtirq needs fixes from time to time, but at least regressions are unwanted for the kernel, sure, they sometimes happen, especially for patched kernels. A very bad exception are soname issues e.g. not long ago introduced by GTK 3.20. The soname of a lib is the major version. Software is compiled against the soname, which usually is a link against a dot release. Regards, Ralf -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] Backports
On Fri, 27 May 2016, lukefro...@hushmail.com wrote: In the case of Kdenlive, versions 15.08 and later use a different file format. They can read an old project but cannot save back to the old format, saving to the new and renaming the old one as a backup. If the user deletes the backup, then reverts Kdenlive versions 15.04 and earlier cannot open the file written by the later version. Fortunately Kdenlive will warn of that and tell the user about the backup file, Ardour 5.* will be the same (already is in GIT). Ardour 3 and 4 are interchangable (with some oddities- 4.1 intruduces trim) 5 takes old sessions ok but the reverse is not true, the old style is kept as a snapshot. -- Len Ovens www.ovenwerks.net -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
[ubuntu-studio-devel] Call for Ardour Backport Testing
Hi All, As Set pointed out, we now have the latest version of Ardour ready to be tested for Backporting to Xenial and Trusty. We need to test that all of the binary packages install OK, and work. We also need to check all reverse dependencies, but as these are mostly "metapackages",it shouldn't be an issue. Q: I want to help, so how do I test? A: Step 1 - You need a Trusty and/or Xenial LTS installation of Ubuntu Studio that you don't mind potentially breaking Step 2 - follow the instructions (https://launchpad.net/~ubuntustudio-dev/+archive/ubuntu/backport-testing) to add our Backport Testing ppa and do an apt-get update, then apt-get upgrade. Step 3 - Give the new version of Ardour a test run. If you are pretty new to Ardour, you could try running our Manual Test Procedure: http://packages.qa.ubuntu.com/qatracker/milestones/361/builds/117793/testcases/1672/results Step 4 - Add a comment to the backport bug and tell us whether it was Trusty/Xenial or both that you tested, which binary packages exactly, and how things went. https://bugs.launchpad.net/trusty-backports/+bug/1584930 Once we have enough evidence that it is working, we can ask someone from the backports team to recommend it's upload to the archive. If you have any problems, then sing out! Regards, Ross PS: We would like to backport our other priority packages. The process is not that hard with the great tools in Ubuntu, so checkout the following wiki and follow the links to help out with that as well: https://wiki.ubuntu.com/UbuntuStudio/BackportsList -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
[ubuntu-studio-devel] Would Ubuntu Studio Team be Interested in Partnering with New England Conservatory?
Hi, I am a music teacher and one of my gigs is teaching for New England Conservatory (NEC) in Boston, MA. I dream of bringing free/libre software to the school for a number of reasons, and am coming up with a strategy for what would be most effective. My thought is a partnership of some sort between Ubuntu Studio and NEC might be worth looking into. My colleagues are willing to listen to me an the idealogical reasons why bringing software libre to the school would be nice, but the conversation always ends with "Okay, that was a great talk, but now what? How do we actualize all these great ideas you preach?" Does anyone have ideas on how to do this? If we can get a game plan together, I am confident that I could get an in-person meeting with the president or one of the deans at the school. Things NEC would be interested in: * Pedagogical Implications (I can help with this greatly. I helped develop Music Blocks software with Sugar Labs, for example. musicblocks.net) * Price savings (of course) * Having their name on something (maybe copyright on some sound-fonts that faculty help to create) * A greater association that their school is "with the times" tech-wise (unlike Berklee, NEC is stuck in middle-ages tech-wise and struggles with its image in this area to a great degree) Any Additional thoughts? Is this a project that Ubuntu Studio would be interested in taking on? Thanks, Devin -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] Backports
On 05/27/2016 01:23 PM, Kaj Ailomaa wrote: > Yes, I'm planning on adding a one-time popup information for > ubuntustudio-controls to be run at login, but that will only be helping > those who already have it installed (which all Ubuntu Studio users will > have, unless they uninstalled it). If this can be easily done, that would be great. But if it is hard, then I am not sure that it is really required. I assume we would need an SRU to get it into Trusty & Xenial. > Since Ubuntu users aren't used to backports for their multimedia > applications, it's important that they know the risks, and that they can > deselect backports. It used to be that it was a bit dangerous, but these days Ubuntu has very sensible defaults for Backports. Basically the backports repository is already in sources.list, but to install from there you must do it manually for each package. Unless you set up "pinning", and if you do that, then you probably know what you are doing. https://help.ubuntu.com/community/UbuntuBackports > We should spread this information quite soon on our web site and social > channels, as well as the user mail list. An announcement that the backport is available is necessary to let people know they are there. And it wouldn't hurt to warn them that they should research if they really want the new features first, and that if the new version uses a new file format, they may not be able to swap files with people using an older version. -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] Backports
And I just sat down to write an email requesting testers for it! Expect instructions with links etc soon. On 05/27/2016 12:16 PM, Set Sakrecoer wrote: > Hi list, and specifically Ross, > > This was brought to my attention: > https://bugs.launchpad.net/trusty-backports/+bug/1584930 > and its all "\o/ yay! Ross rocks yet again!" > > I read it like an open invitation to the devel-team to test the > backports but maybe it has a specific team? I'd gladly participate > however and the instructions are rather clear but having no experience > in the process i thought i'd ask here before i do anything. > > I read zequence was talking on IRC about finding a good way to warn our > users of the consequences of backports, since it appears backports are > able to break things for people having a project in the making. Hence > please also consider this email as an invitation to discuss how we > communicate this change to our user base. > > Yours, -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] Backports
On 05/27/2016 12:16 PM, Set Sakrecoer wrote: > Hi list, and specifically Ross, > > This was brought to my attention: > https://bugs.launchpad.net/trusty-backports/+bug/1584930 > and its all "\o/ yay! Ross rocks yet again!" > > I read it like an open invitation to the devel-team to test the > backports but maybe it has a specific team? I'd gladly participate > however and the instructions are rather clear but having no experience > in the process i thought i'd ask here before i do anything. > > I read zequence was talking on IRC about finding a good way to warn our > users of the consequences of backports, since it appears backports are > able to break things for people having a project in the making. Hence > please also consider this email as an invitation to discuss how we > communicate this change to our user base. > > Yours, -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] Backports
In the case of Kdenlive, versions 15.08 and later use a different file format. They can read an old project but cannot save back to the old format, saving to the new and renaming the old one as a backup. If the user deletes the backup, then reverts Kdenlive versions 15.04 and earlier cannot open the file written by the later version. Fortunately Kdenlive will warn of that and tell the user about the backup file, On 5/27/2016 at 6:18 AM, "Set Sakrecoer" wrote: > >Hi list, and specifically Ross, > >This was brought to my attention: >https://bugs.launchpad.net/trusty-backports/+bug/1584930 >and its all "\o/ yay! Ross rocks yet again!" > >I read it like an open invitation to the devel-team to test the >backports but maybe it has a specific team? I'd gladly participate >however and the instructions are rather clear but having no >experience >in the process i thought i'd ask here before i do anything. > >I read zequence was talking on IRC about finding a good way to >warn our >users of the consequences of backports, since it appears backports >are >able to break things for people having a project in the making. >Hence >please also consider this email as an invitation to discuss how we >communicate this change to our user base. > >Yours, >-- >Set aka ~sakrecoer > >-- >ubuntu-studio-devel mailing list >ubuntu-studio-devel@lists.ubuntu.com >Modify settings or unsubscribe at: >https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] Backports
On Fri, May 27, 2016, at 12:16 PM, Set Sakrecoer wrote: > I read zequence was talking on IRC about finding a good way to warn our > users of the consequences of backports, since it appears backports are > able to break things for people having a project in the making. Hence > please also consider this email as an invitation to discuss how we > communicate this change to our user base. > > Yours, > -- > Set aka ~sakrecoer > Yes, I'm planning on adding a one-time popup information for ubuntustudio-controls to be run at login, but that will only be helping those who already have it installed (which all Ubuntu Studio users will have, unless they uninstalled it). Since Ubuntu users aren't used to backports for their multimedia applications, it's important that they know the risks, and that they can deselect backports. We should spread this information quite soon on our web site and social channels, as well as the user mail list. -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
[ubuntu-studio-devel] Backports
Hi list, and specifically Ross, This was brought to my attention: https://bugs.launchpad.net/trusty-backports/+bug/1584930 and its all "\o/ yay! Ross rocks yet again!" I read it like an open invitation to the devel-team to test the backports but maybe it has a specific team? I'd gladly participate however and the instructions are rather clear but having no experience in the process i thought i'd ask here before i do anything. I read zequence was talking on IRC about finding a good way to warn our users of the consequences of backports, since it appears backports are able to break things for people having a project in the making. Hence please also consider this email as an invitation to discuss how we communicate this change to our user base. Yours, -- Set aka ~sakrecoer -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
