Re: [ubuntu-studio-devel] check-in and reminder release candidate on April 6th
Thanks Eylul & Len. Just back from my travels and I see the tests are marked ready, and the release notes prepared! I will probably still give the ISOs a spin - probably be a while before the release is official. Will also go over the Release Notes. Cheers, Ross On 04/13/2017 01:26 AM, eylul wrote: > Quick update: behind testing, but the release notes are up. > > https://wiki.ubuntu.com/ZestyZapus/ReleaseNotes/UbuntuStudio feel free > to add, remove, edit, etc to make sure we didn't miss any other changes. > > Also, got in touch with Set about the website, both Krytarik and I have > administrator access, so we should be able to post tomorrow or when needed. > > Thanks. > > Best > > Eylul > > > On 04/02/2017 11:52 AM, Ross Gammon wrote: >> On 03/31/2017 10:36 AM, eylul wrote: >>> I will be around for testing April 11,12,13th, and will be available in >>> chatroom the (european) evenings during that time. Will probably try to >>> do some more tests before that too if I can. >>> >>> I'll also start the notes so that we can all add items on it. (nag me if >>> it is not done by next tuesday). (unfortunately probably not much help >>> on development side tasks). >> Thanks for volunteering for that. It can easily be forgotten in the rush >> of testing the ISO images. >> >>> we should probably also email users ML to see if there is anybody who >>> can help us test there as well. :) >> Done - just now >> >>> On 03/30/2017 01:56 PM, Ross Gammon wrote: Thanks Eylul - you must have read my mind! On 29/03/17 20:43, eylul wrote: > Hi! > > Zesty release is right around the corner and we will have release > candidates out starting April 6th. Where are we with things? Who do we > have available to test the week of April 6th/13th? > > Best > > Eylul I am afraid I have availability problems for this particular release week. I might have some time on the 6th to test the first Release Candidate. And I should be back on the 13th to try and help with the release, but with no guarantee that I will have much time to spare. So it would be great to have some volunteers for testing one or two of the days during that week. Please reply to this message if you can, otherwise we might need to inform the Ubuntu Release Team that we would like to defer our release until after the Easter Holidays. There are also some tasks that I am aware of that we could be doing this week to help prepare for a good release. >> [...] >> Development: 1. Len did some excellent work on ubuntustudio-controls this cycle, but we needed to revert back to something like the state it was at Revision 128. I tried to do this, but may have made some mistakes (r130). It crashed when I tested it, and I haven't had time to get back on it. It may be too late to get a freeze exception for this, but if someone was keen to try. >> Prepared & waiting for the Release Team to confirm the Freeze Exception. >> We should maybe ping them on IRC next week. >> 2. There has been a mass rebuild of the archive, and there are a few build failures of our packages that someone could look into: http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-zesty.html#ubuntustudio http://qa.ubuntuwire.com/ftbfs/#ubuntustudio Testing: 1. No-one from the team (that I am aware of) did any real testing of the Final Beta, so the Ubuntu Release Team asked that we give the daily ISOs a good bash between now and the release: http://iso.qa.ubuntu.com/qatracker/milestones/369/builds 2. We could do with a smoke test of our important applications. There are test cases that can be used here: http://packages.qa.ubuntu.com/qatracker/milestones/370/builds Testing Please submit a bug if you find something bad, and let us know. Please also record your results if you found no problems, then others can decide to concentrate on untested ones if they are short of time. Bugs: Lots of people have already reported bugs against our packages: https://bugs.launchpad.net/~ubuntustudio-bugs/+packagebugs Feel free to triage some of these bugs to see if any of our packages contain serious bugs, and let us know. There is some advice here for triaging bugs in Launchpad: https://wiki.ubuntu.com/Bugs/Triage/ I hope we can all "muck in" and make it a good release! >> Do we have someone to man the website & blog about the release? >> >> Also, our support for the Ubuntu Studio Trusty 14.04 (LTS) release ends >> with the release of 17.04 (3 years). We should announce this here, the >> users list and on the website ahead of time. >> >> Cheers, >> >> Ross >> > > -- 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] check-in and reminder release candidate on April 6th
Quick update: behind testing, but the release notes are up. https://wiki.ubuntu.com/ZestyZapus/ReleaseNotes/UbuntuStudio feel free to add, remove, edit, etc to make sure we didn't miss any other changes. Also, got in touch with Set about the website, both Krytarik and I have administrator access, so we should be able to post tomorrow or when needed. Thanks. Best Eylul On 04/02/2017 11:52 AM, Ross Gammon wrote: > On 03/31/2017 10:36 AM, eylul wrote: >> I will be around for testing April 11,12,13th, and will be available in >> chatroom the (european) evenings during that time. Will probably try to >> do some more tests before that too if I can. >> >> I'll also start the notes so that we can all add items on it. (nag me if >> it is not done by next tuesday). (unfortunately probably not much help >> on development side tasks). > Thanks for volunteering for that. It can easily be forgotten in the rush > of testing the ISO images. > >> we should probably also email users ML to see if there is anybody who >> can help us test there as well. :) > Done - just now > >> On 03/30/2017 01:56 PM, Ross Gammon wrote: >>> Thanks Eylul - you must have read my mind! >>> >>> On 29/03/17 20:43, eylul wrote: Hi! Zesty release is right around the corner and we will have release candidates out starting April 6th. Where are we with things? Who do we have available to test the week of April 6th/13th? Best Eylul >>> I am afraid I have availability problems for this particular release >>> week. I might have some time on the 6th to test the first Release >>> Candidate. And I should be back on the 13th to try and help with the >>> release, but with no guarantee that I will have much time to spare. >>> >>> So it would be great to have some volunteers for testing one or two of >>> the days during that week. Please reply to this message if you can, >>> otherwise we might need to inform the Ubuntu Release Team that we >>> would like to defer our release until after the Easter Holidays. >>> >>> There are also some tasks that I am aware of that we could be doing >>> this week to help prepare for a good release. > [...] > >>> Development: >>> 1. Len did some excellent work on ubuntustudio-controls this cycle, >>> but we needed to revert back to something like the state it was at >>> Revision 128. I tried to do this, but may have made some mistakes >>> (r130). It crashed when I tested it, and I haven't had time to get >>> back on it. It may be too late to get a freeze exception for this, but >>> if someone was keen to try. > Prepared & waiting for the Release Team to confirm the Freeze Exception. > We should maybe ping them on IRC next week. > >>> 2. There has been a mass rebuild of the archive, and there are a few >>> build failures of our packages that someone could look into: >>> http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-zesty.html#ubuntustudio >>> >>> http://qa.ubuntuwire.com/ftbfs/#ubuntustudio >>> >>> Testing: >>> 1. No-one from the team (that I am aware of) did any real testing of >>> the Final Beta, so the Ubuntu Release Team asked that we give the >>> daily ISOs a good bash between now and the release: >>> http://iso.qa.ubuntu.com/qatracker/milestones/369/builds >>> 2. We could do with a smoke test of our important applications. There >>> are test cases that can be used here: >>> http://packages.qa.ubuntu.com/qatracker/milestones/370/builds >>> Testing >>> Please submit a bug if you find something bad, and let us know. Please >>> also record your results if you found no problems, then others can >>> decide to concentrate on untested ones if they are short of time. >>> >>> Bugs: >>> Lots of people have already reported bugs against our packages: >>> https://bugs.launchpad.net/~ubuntustudio-bugs/+packagebugs >>> Feel free to triage some of these bugs to see if any of our packages >>> contain serious bugs, and let us know. There is some advice here for >>> triaging bugs in Launchpad: >>> https://wiki.ubuntu.com/Bugs/Triage/ >>> >>> I hope we can all "muck in" and make it a good release! > Do we have someone to man the website & blog about the release? > > Also, our support for the Ubuntu Studio Trusty 14.04 (LTS) release ends > with the release of 17.04 (3 years). We should announce this here, the > users list and on the website ahead of time. > > Cheers, > > Ross > -- 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] check-in and reminder release candidate on April 6th
On Tue, 4 Apr 2017 06:02:20 +0200, Ralf Mardorf wrote: >https://lists.ubuntu.com/archives/ubuntu-users/2017-April/289831.html >https://lists.ubuntu.com/archives/ubuntu-users/2017-April/289831.html Oops! The second link should read: https://lists.ubuntu.com/archives/ubuntu-users/2017-April/289788.html -- 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] check-in and reminder release candidate on April 6th
Hi, there's no cpufreq/scaling_governor when running Linux as a guest in a virtual machine. https://lists.ubuntu.com/archives/ubuntu-users/2017-April/289831.html https://lists.ubuntu.com/archives/ubuntu-users/2017-April/289831.html Regards, Ralf -- "Michael" described Floyd as "an idiot savant", and added, "Give him any two numbers, and he can multiply them in his head, just like that." Homer, testing Floyd, said, "Five times nine", and Floyd instantly responded "Forty-five", which impressed Homer. -- 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] check-in and reminder release candidate on April 6th
On 03/31/2017 10:36 AM, eylul wrote: > I will be around for testing April 11,12,13th, and will be available in > chatroom the (european) evenings during that time. Will probably try to > do some more tests before that too if I can. > > I'll also start the notes so that we can all add items on it. (nag me if > it is not done by next tuesday). (unfortunately probably not much help > on development side tasks). Thanks for volunteering for that. It can easily be forgotten in the rush of testing the ISO images. > we should probably also email users ML to see if there is anybody who > can help us test there as well. :) Done - just now > On 03/30/2017 01:56 PM, Ross Gammon wrote: >> Thanks Eylul - you must have read my mind! >> >> On 29/03/17 20:43, eylul wrote: >>> Hi! >>> >>> Zesty release is right around the corner and we will have release >>> candidates out starting April 6th. Where are we with things? Who do we >>> have available to test the week of April 6th/13th? >>> >>> Best >>> >>> Eylul >> I am afraid I have availability problems for this particular release >> week. I might have some time on the 6th to test the first Release >> Candidate. And I should be back on the 13th to try and help with the >> release, but with no guarantee that I will have much time to spare. >> >> So it would be great to have some volunteers for testing one or two of >> the days during that week. Please reply to this message if you can, >> otherwise we might need to inform the Ubuntu Release Team that we >> would like to defer our release until after the Easter Holidays. >> >> There are also some tasks that I am aware of that we could be doing >> this week to help prepare for a good release. [...] >> Development: >> 1. Len did some excellent work on ubuntustudio-controls this cycle, >> but we needed to revert back to something like the state it was at >> Revision 128. I tried to do this, but may have made some mistakes >> (r130). It crashed when I tested it, and I haven't had time to get >> back on it. It may be too late to get a freeze exception for this, but >> if someone was keen to try. Prepared & waiting for the Release Team to confirm the Freeze Exception. We should maybe ping them on IRC next week. >> 2. There has been a mass rebuild of the archive, and there are a few >> build failures of our packages that someone could look into: >> http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-zesty.html#ubuntustudio >> >> http://qa.ubuntuwire.com/ftbfs/#ubuntustudio >> >> Testing: >> 1. No-one from the team (that I am aware of) did any real testing of >> the Final Beta, so the Ubuntu Release Team asked that we give the >> daily ISOs a good bash between now and the release: >> http://iso.qa.ubuntu.com/qatracker/milestones/369/builds >> 2. We could do with a smoke test of our important applications. There >> are test cases that can be used here: >> http://packages.qa.ubuntu.com/qatracker/milestones/370/builds >> Testing >> Please submit a bug if you find something bad, and let us know. Please >> also record your results if you found no problems, then others can >> decide to concentrate on untested ones if they are short of time. >> >> Bugs: >> Lots of people have already reported bugs against our packages: >> https://bugs.launchpad.net/~ubuntustudio-bugs/+packagebugs >> Feel free to triage some of these bugs to see if any of our packages >> contain serious bugs, and let us know. There is some advice here for >> triaging bugs in Launchpad: >> https://wiki.ubuntu.com/Bugs/Triage/ >> >> I hope we can all "muck in" and make it a good release! Do we have someone to man the website & blog about the release? Also, our support for the Ubuntu Studio Trusty 14.04 (LTS) release ends with the release of 17.04 (3 years). We should announce this here, the users list and on the website ahead of time. Cheers, Ross -- 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] check-in and reminder release candidate on April 6th
On Fri, 31 Mar 2017 15:27:15 -0700 (PDT), Len Ovens wrote: >On Fri, 31 Mar 2017, Ross Gammon wrote: >> On 03/31/2017 10:50 PM, Ralf Mardorf wrote: >>> VitualBox emulates a CPU, by using the real CPU. The guest is not >>> able to change settings of host and I could imagine there's no >>> simulated CPU frequency scaling available. >> >> Makes sense! Hopefully Len can confirm all is OK on real hardware. > >Ross, the package you have in testing performs to the extent of >development at that time. That is performance is only during the >current session and will reset at boot. > >we do not install cpufrequtils at this time either. The new -controls >will depend on it for booting in the governor mode the session was at >session end. (so if I upload a new version without that in depends I >made a mistake) Apart from this, it would be good to know how VMs or at least VBox handles CPU frequency scaling settings of the virtual/guests environment. To be honest, I simply could restore any of my current Ubuntu or Arch Linux Backups in at least VBox (other VMs are to complicated), but at the moment I dislike to do this ;). The crux here is that virtualisation vs real hardware. Theoretically for the guest there could be a virtual CPU frequency scaling, OTOH it doesn't make much sense to emulate this, given that VMs likely relay on CPU features for virtualisation. OTOH if the virtual CPU should be a very old CPU, then a gov set to performance likely would be slower than the slowest possible governor for a modern AMD or Intel CPU of the host. I doubt that VM hosts "play" with this, since here are already enough problems VM developers have to fight, so I doubt that something quasi useless, like a CPU freq gov for guests is available. I try to remember this and will test it, if I have nothing better to do ;). Regards, Ralf -- "Michael" described Floyd as "an idiot savant", and added, "Give him any two numbers, and he can multiply them in his head, just like that." Homer, testing Floyd, said, "Five times nine", and Floyd instantly responded "Forty-five", which impressed Homer. -- 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] check-in and reminder release candidate on April 6th
On 04/01/2017 05:47 AM, Ross Gammon wrote: > On 04/01/2017 12:27 AM, Len Ovens wrote: >> On Fri, 31 Mar 2017, Ross Gammon wrote: >> >>> Makes sense! Hopefully Len can confirm all is OK on real hardware. >> Ross, the package you have in testing performs to the extent of >> development at that time. That is performance is only during the >> current session and will reset at boot. > Excellent. I will try and get the Release Team to approve. > If it gets in, we should mention these details about -controls in the > release notes. > https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-controls/+bug/1678316 -- 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] check-in and reminder release candidate on April 6th
On 04/01/2017 12:27 AM, Len Ovens wrote: > On Fri, 31 Mar 2017, Ross Gammon wrote: > >> Makes sense! Hopefully Len can confirm all is OK on real hardware. > > Ross, the package you have in testing performs to the extent of > development at that time. That is performance is only during the > current session and will reset at boot. Excellent. I will try and get the Release Team to approve. If it gets in, we should mention these details about -controls in the release notes. -- 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] check-in and reminder release candidate on April 6th
On Thu, 30 Mar 2017, Ross Gammon wrote: Zesty release is right around the corner and we will have release PS: I have probably forgotten something. Oh yeah - is there someone around from the website team to blog about the release once it happens? Ross, thankyou for all the help. I notice that Ardour 5.5 is in proposed. I downloaded it and tested. Everything I have tested so far works. Recorded audio and midi. played back successfully. Plugin GUI doesn't seem to crash things. Except ... calf plugins :( of course calf plugins are known for that and other things. Anyway, is there someone who would want to know my findings on a proposed package. where would I report that it runs for me? -- 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
Re: [ubuntu-studio-devel] check-in and reminder release candidate on April 6th
On Fri, 31 Mar 2017, Ross Gammon wrote: On 03/31/2017 10:50 PM, Ralf Mardorf wrote: echo powersave | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor >/dev/null 2>&1 echo ondemand | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor >/dev/null 2>&1 I did not have "cpufreq/scaling_governor" file in the VM, and if I ran cpufreq-info it complained that there were no CPUFreq drivers available. VitualBox emulates a CPU, by using the real CPU. The guest is not able to change settings of host and I could imagine there's no simulated CPU frequency scaling available. Makes sense! Hopefully Len can confirm all is OK on real hardware. Ross, the package you have in testing performs to the extent of development at that time. That is performance is only during the current session and will reset at boot. we do not install cpufrequtils at this time either. The new -controls will depend on it for booting in the governor mode the session was at session end. (so if I upload a new version without that in depends I made a mistake) -- 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
Re: [ubuntu-studio-devel] check-in and reminder release candidate on April 6th
Thanks Ralf. On 03/31/2017 10:50 PM, Ralf Mardorf wrote: > echo powersave | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor > >/dev/null 2>&1 > echo ondemand | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor > >/dev/null 2>&1 I did not have "cpufreq/scaling_governor" file in the VM, and if I ran cpufreq-info it complained that there were no CPUFreq drivers available. > VitualBox emulates a CPU, by using the real CPU. The guest is not > able to change settings of host and I could imagine there's no > simulated CPU frequency scaling available. Makes sense! Hopefully Len can confirm all is OK on real hardware. I have submitted a Feature Freeze Exception bug. But I need to sleep now. So if Len reports that he is happy, I will upload the debdiff to the bug in the morning and subscribe the Release Team to see if they will allow it in so close to the release. Thanks guys! Sorry it took so long to "fix up" my "stuff up" with the bzr reversion. Ross -- 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] check-in and reminder release candidate on April 6th
On Fri, 31 Mar 2017 22:31:48 +0200, Ross Gammon wrote: >The file that is modified to add the "performance" setting does not >exist. It could just be a Virtual Box thing, but it makes me wonder if >the files & paths change according to the CPU type and kernel drivers? There is one difference for CPUs, so I sometimes run scripts like this: echo powersave | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor >/dev/null 2>&1 echo ondemand | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor >/dev/null 2>&1 "powersafe" for Intel and "ondemand" for AMD, >/dev/null 2>&1 to redirect error messages. "performance" is equal for Intel and AMD and by default this should work! VitualBox emulates a CPU, by using the real CPU. The guest is not able to change settings of host and I could imagine there's no simulated CPU frequency scaling available. Regards, Ralf -- "Michael" described Floyd as "an idiot savant", and added, "Give him any two numbers, and he can multiply them in his head, just like that." Homer, testing Floyd, said, "Five times nine", and Floyd instantly responded "Forty-five", which impressed Homer. -- 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] check-in and reminder release candidate on April 6th
On 31/03/17 22:44, Len Ovens wrote: If I know where the new upload is I will test on metal. https://launchpad.net/rosco2/+archive/ubuntu/testing I will push commits to bzr in a tick as well. -- 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] check-in and reminder release candidate on April 6th
On Fri, 31 Mar 2017, Ross Gammon wrote: On 30/03/17 12:56, Ross Gammon wrote: Development: 1. Len did some excellent work on ubuntustudio-controls this cycle, but we needed to revert back to something like the state it was at Revision 128. I tried to do this, but may have made some mistakes (r130). It crashed when I tested it, and I haven't had time to get back on it. It may be too late to get a freeze exception for this, but if someone was keen to try. OK - looks like I made a mess of the revert. Replacing the glade file with the one from revision 128 (which I thought is what I did before) works. I am in the middle of testing to be sure. But just to note, that for me the CPU governor setting does not stick for me in a US Zesty VM. Looking at the code, I think it is because the file layout is different in the VM. The file that is modified to add the "performance" setting does not exist. It could just be a Virtual Box thing, but it makes me wonder if the files & paths change according to the CPU type and kernel drivers? Ok, I am just installing zesty. It would be _really_ nice to get a newer Ardour in there than 5.0 (5.8 at ardour.org now) and telling people they should get newer from kxstudio... Anyway, I will prepare an upload and see how it goes. We can keep working on it in the next cycle. If I know where the new upload is I will test on metal. -- 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
Re: [ubuntu-studio-devel] check-in and reminder release candidate on April 6th
On 30/03/17 12:56, Ross Gammon wrote: Development: 1. Len did some excellent work on ubuntustudio-controls this cycle, but we needed to revert back to something like the state it was at Revision 128. I tried to do this, but may have made some mistakes (r130). It crashed when I tested it, and I haven't had time to get back on it. It may be too late to get a freeze exception for this, but if someone was keen to try. OK - looks like I made a mess of the revert. Replacing the glade file with the one from revision 128 (which I thought is what I did before) works. I am in the middle of testing to be sure. But just to note, that for me the CPU governor setting does not stick for me in a US Zesty VM. Looking at the code, I think it is because the file layout is different in the VM. The file that is modified to add the "performance" setting does not exist. It could just be a Virtual Box thing, but it makes me wonder if the files & paths change according to the CPU type and kernel drivers? Anyway, I will prepare an upload and see how it goes. We can keep working on it in the next cycle. -- 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] check-in and reminder release candidate on April 6th
belated answer to this since my hosting service email system went down yesterday. I will be around for testing April 11,12,13th, and will be available in chatroom the (european) evenings during that time. Will probably try to do some more tests before that too if I can. I'll also start the notes so that we can all add items on it. (nag me if it is not done by next tuesday). (unfortunately probably not much help on development side tasks). we should probably also email users ML to see if there is anybody who can help us test there as well. :) Best Eylul On 03/30/2017 01:56 PM, Ross Gammon wrote: > Thanks Eylul - you must have read my mind! > > On 29/03/17 20:43, eylul wrote: >> Hi! >> >> Zesty release is right around the corner and we will have release >> candidates out starting April 6th. Where are we with things? Who do we >> have available to test the week of April 6th/13th? >> >> Best >> >> Eylul > > I am afraid I have availability problems for this particular release > week. I might have some time on the 6th to test the first Release > Candidate. And I should be back on the 13th to try and help with the > release, but with no guarantee that I will have much time to spare. > > So it would be great to have some volunteers for testing one or two of > the days during that week. Please reply to this message if you can, > otherwise we might need to inform the Ubuntu Release Team that we > would like to defer our release until after the Easter Holidays. > > There are also some tasks that I am aware of that we could be doing > this week to help prepare for a good release. > > Release: > We could prepare some release notes based on the last release > (https://wiki.ubuntu.com/YakketyYak/ReleaseNotes/UbuntuStudio), and > the Final Beta release > (https://wiki.ubuntu.com/ZestyZapus/Beta2/UbuntuStudio). Then they > would only need a final tweak and check on the day of the release > (updating known bugs & package versions). > > Development: > 1. Len did some excellent work on ubuntustudio-controls this cycle, > but we needed to revert back to something like the state it was at > Revision 128. I tried to do this, but may have made some mistakes > (r130). It crashed when I tested it, and I haven't had time to get > back on it. It may be too late to get a freeze exception for this, but > if someone was keen to try. > 2. There has been a mass rebuild of the archive, and there are a few > build failures of our packages that someone could look into: > http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-zesty.html#ubuntustudio > > http://qa.ubuntuwire.com/ftbfs/#ubuntustudio > > Testing: > 1. No-one from the team (that I am aware of) did any real testing of > the Final Beta, so the Ubuntu Release Team asked that we give the > daily ISOs a good bash between now and the release: > http://iso.qa.ubuntu.com/qatracker/milestones/369/builds > 2. We could do with a smoke test of our important applications. There > are test cases that can be used here: > http://packages.qa.ubuntu.com/qatracker/milestones/370/builds > Testing > Please submit a bug if you find something bad, and let us know. Please > also record your results if you found no problems, then others can > decide to concentrate on untested ones if they are short of time. > > Bugs: > Lots of people have already reported bugs against our packages: > https://bugs.launchpad.net/~ubuntustudio-bugs/+packagebugs > Feel free to triage some of these bugs to see if any of our packages > contain serious bugs, and let us know. There is some advice here for > triaging bugs in Launchpad: > https://wiki.ubuntu.com/Bugs/Triage/ > > I hope we can all "muck in" and make it a good release! > > Cheers, > > Ross > > PS: I have probably forgotten something. Oh yeah - is there someone > around from the website team to blog about the release once it happens? > -- 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] check-in and reminder release candidate on April 6th
Thanks Eylul - you must have read my mind! On 29/03/17 20:43, eylul wrote: Hi! Zesty release is right around the corner and we will have release candidates out starting April 6th. Where are we with things? Who do we have available to test the week of April 6th/13th? Best Eylul I am afraid I have availability problems for this particular release week. I might have some time on the 6th to test the first Release Candidate. And I should be back on the 13th to try and help with the release, but with no guarantee that I will have much time to spare. So it would be great to have some volunteers for testing one or two of the days during that week. Please reply to this message if you can, otherwise we might need to inform the Ubuntu Release Team that we would like to defer our release until after the Easter Holidays. There are also some tasks that I am aware of that we could be doing this week to help prepare for a good release. Release: We could prepare some release notes based on the last release (https://wiki.ubuntu.com/YakketyYak/ReleaseNotes/UbuntuStudio), and the Final Beta release (https://wiki.ubuntu.com/ZestyZapus/Beta2/UbuntuStudio). Then they would only need a final tweak and check on the day of the release (updating known bugs & package versions). Development: 1. Len did some excellent work on ubuntustudio-controls this cycle, but we needed to revert back to something like the state it was at Revision 128. I tried to do this, but may have made some mistakes (r130). It crashed when I tested it, and I haven't had time to get back on it. It may be too late to get a freeze exception for this, but if someone was keen to try. 2. There has been a mass rebuild of the archive, and there are a few build failures of our packages that someone could look into: http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-zesty.html#ubuntustudio http://qa.ubuntuwire.com/ftbfs/#ubuntustudio Testing: 1. No-one from the team (that I am aware of) did any real testing of the Final Beta, so the Ubuntu Release Team asked that we give the daily ISOs a good bash between now and the release: http://iso.qa.ubuntu.com/qatracker/milestones/369/builds 2. We could do with a smoke test of our important applications. There are test cases that can be used here: http://packages.qa.ubuntu.com/qatracker/milestones/370/builds Testing Please submit a bug if you find something bad, and let us know. Please also record your results if you found no problems, then others can decide to concentrate on untested ones if they are short of time. Bugs: Lots of people have already reported bugs against our packages: https://bugs.launchpad.net/~ubuntustudio-bugs/+packagebugs Feel free to triage some of these bugs to see if any of our packages contain serious bugs, and let us know. There is some advice here for triaging bugs in Launchpad: https://wiki.ubuntu.com/Bugs/Triage/ I hope we can all "muck in" and make it a good release! Cheers, Ross PS: I have probably forgotten something. Oh yeah - is there someone around from the website team to blog about the release once it happens? -- 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
