[13:24] <len-dt> scott-work, astraljava  This move to final appears not to need retest. Is that correct?
[13:33] <astraljava> len-dt: Yes, that's my understanding too.
[13:52] <len-dt> astraljava, and then release (when it comes) will be what we base 12.10 on I would guess.
[13:52] <scott-work> just this morning i signed the release manifest to change the status as "approved for release"
[13:52]  * len-dt is new to this stuff as this is his first cycle...
[13:55] <len-dt> As some people have talked about AWN as a panel for US, I downloaded it to look at. It pulls in gnome3 fallback and unity... some 118 packages.
[13:56] <len-dt> It looks pretty, but in the end it is just another panel and I think I could get the same functionality out of the xfce panel.
[13:58] <len-dt> scott-work, astraljava  I think if we are going to do workflows with changing menus similar to what I had mocked up, it would be best to work on them as an xfce panel applet.
[14:02] <scott-work> len-dt: that is the reason that we haven't really made more progress with AWN (re: dependecies)
[14:03] <len-dt> scott-work, I think we could make xfce panel look the same minus the fancy graphics.
[14:04] <len-dt> I don't see a vast difference in the underlying function.
[14:04]  * len-dt is off to work, will read back log on return.
[14:06] <scott-work> len-dt: re: work flows - if we create any new applications we need to especially cognizant of the time it will take to get into the repositories (which could be months)
[14:10] <len-dt> scott-work, if there is nothing out there now, we have no choice. What I have  done is all script... no source. That could be dropped into our "look" package.
[14:12] <scott-work> len-dt: it could possibly, but the package approval process is in place for a variety of reasons, including vetting new code for security (along with other items) and shouldn't be abused unecessarily
[14:13] <scott-work> we should think through this before making any decisions
[17:40] <astraljava> len-dt: There'll usually be huge changes when the archives open again, but probably not this time as Debian is frozen for a new release as well.
[17:40] <astraljava> Not really sure about how's it going to be this time.
[17:49] <astraljava> Right, new amd64 images.
[17:49] <astraljava> ;./
[17:59] <astraljava> bug #899001 is haunting us, so please check if you can help with that. I'll be testing it within the few next hours, but I could use some backup if possible.
[18:02] <astraljava> Err... sorry, the image isn't yet available. I'll shout out again when it is.
[18:35] <astraljava> Ok, go fetch!
[18:41] <knome> what? i didn't hear. shout louder
[20:21] <len-dt> astraljava, I can't help with the amd64 stuff... 
[20:23] <len-dt> astraljava, http://iso.qa.ubuntu.com/qatracker/milestones/216/builds still shows the test results from before the respin for adm64 ISOs
[20:31] <len-dt> astraljava, scott-work and whoever else can test the amd64 ISO, the page to post results is http://iso.qa.ubuntu.com/qatracker/milestones/214/builds
[20:42] <acmeinc> I'm confused regarding the Testcases page.  Is it asking us if *only* the install passed with no bugs, or if install AND testing passed with no bugs.
[20:48] <len-dt> acmeinc, Which page? (url) I think the two tests are live works and install works.
[20:49] <acmeinc> len, yes that's the one...so I'm assuming I would say "Passed with no bugs" if my install worked from both the Live and Install mode, even though I'm seeing bugs post installation?
[20:50] <acmeinc> in short, is this page only asking to be sure the installation from both modes is working properly?
[20:50] <scott-work> len-dt: i can test the 64bit this evening
[20:50] <len-dt> acmeinc, There are some known bugs that will not be fixed before release.
[20:50] <len-dt> scott-work, Ok .
[20:51] <len-dt> acmeinc, we would only be looking for bugs that make things unusable at this point.
[20:54] <len-dt> acmeinc, so after install, it should reboot and the installer should be able to login and run something (irc or browser for example.)
[20:56] <len-dt> acmeinc, Installer means the person who installed, not the installer software.. 
[20:56]  * len-dt is not a great communicator.
[21:10] <acmeinc> len, ok, thx for the clarifation, install works just fine, and sample apps as well.
[21:10] <acmeinc> i'll mark it
[21:11] <len-dt> acmeinc, Good.
[21:12] <len-dt> I think thats our release then.
[21:13] <acmeinc> would you rather me post general 12.04 questions to the non-devel area?
[21:15] <len-dt> acmeinc, I don't know really, if it is about how to then yes, if it looks like something that could use changing here is good.
[21:15] <acmeinc> well it seems bluetooth has gone away since 11.04-studio, which is a concern of mine
[21:16] <acmeinc> unless its just done differently...in that case, i'd post to the general
[21:16] <len-dt> acmeinc, I think that would be a bug. I think that was mentioned before... none of us has the hardware to check that I know.
[21:17] <len-dt> Oh that was you all ready :)
[21:18] <acmeinc> len, i have a bluetooth dongle i used successfully in pairing on 11.04.  on 12.04 the applet is gone..i tried bluemon and installing th e applet manually, but neither find the "adapter".  
[21:19] <acmeinc> Would you like me to file a bug, or note an existing bug, or try-out something for you?
[21:19] <len-dt> It needs a bug report. Is there an existing bug?
[21:19] <acmeinc> i wouldn't know :)
[21:21] <len-dt> acmeinc, if there was an applet before it should still be there. If we are missing it. That is a bug.
[21:25] <len-dt> acmeinc, I don't see a BT applet listed in the available panel applets. I don't know if that is because my hardware doesn't support BT though.
[21:26]  * len-dt is gone to pick kids up at school.
[21:38] <acmeinc> report filed under Ubuntu Studio Project, I hope that was right.
[21:45] <scott-work> was typing something on another channel and thought i should share here, hopefully the paste works well:
[21:45] <scott-work> [16:39] <scott-work> _guitarman_: what if we scripted opening qjackctl, starting jack with certain settings, open ardour + hydrogen + whatever else, and make all the connections? [16:39] <scott-work> _guitarman_: what if we applied that same idea to work flows for creating graphics?  or editing video? [16:40] <scott-work> _guitarman_: what if we made this use a gui and had rectangles for each "process" for a work flow
[21:45] <scott-work> crap, no
[21:46] <scott-work> [16:39] <scott-work> _guitarman_: what if we scripted opening qjackctl, starting jack with certain settings, open ardour + hydrogen + whatever else, and make all the connections?
[21:46] <scott-work> [16:39] <scott-work> _guitarman_: what if we applied that same idea to work flows for creating graphics?  or editing video?
[21:46] <scott-work> [16:40] <scott-work> _guitarman_: what if we made this use a gui and had rectangles for each "process" for a work flows with choices and a default chosen?
[21:46] <scott-work> [16:40] <scott-work> for example, let's consider editing video:
[21:46] <scott-work> [16:40] <scott-work> user starts the app
[21:46] <scott-work> [16:41] <scott-work> see's that there are choices for editing audio, editing video, creating a title screen, and publishing to web
[21:46] <scott-work> [16:41] <scott-work> so each process (e.g. editing audio vs editing video) is in a rectangle and the various choices are under it
[21:47] <scott-work> [16:42] <scott-work> the user clearly now understands not only what work flow we intended, which applications are available, but also which apps we suggest as "preferred"
[21:47] <scott-work> [16:42] <scott-work> what if we could generate a script for the user once they have their preferred work flow or tool chain (chosen applications)
[21:47] <scott-work> [16:43] <scott-work> that is just a sample of what i mean by "user improvements" or "usage improvements" = making it easier for users
[21:47] <scott-work> [16:44] <scott-work> also we are considering a "record mode" for audio, maybe it turns off network manager, pulse audio, blue tooth, ubuntu one if they are running
[21:47] <scott-work> [16:44] <scott-work> maybe it also changes or adds a dock on the side of the screen that shows only applications for audio, maybe even have then sequences to mimic the work flow
[21:47] <scott-work> [16:45] <scott-work> this idea could also be applied for video or graphics or photography or ebook
[21:49] <scott-work> also, we could even consider that different workspaces can be named, have their own backdrops, and maybe even have their own docks (i'm guessing on this one)
[21:49] <scott-work> maybe have an "video" workspace that has applications in the dock for video work
[21:59] <len-dt> ScottL, I don't like the workspace idea for at least two reasons :)
[22:00] <len-dt> ScottL, 1) I normally use more than one WS for just audio (or just other workflows for that matter)
[22:02] <len-dt> ScottL, 2) having workspaces with different BGs an panels increases the system load all the time.(memory at least)
[22:03] <len-dt> ScottL, 3) (I said two right? :)  it would encourage people to leave unrelated apps running in an unseen WS which would also use extra resources
[22:05] <len-dt> ScottL, KDE (apparently) already offers such a setup, so installing kubuntu and playing with it might give you an idea how it would work out.
[22:06] <len-dt> ScottL, KDE was not chosen for US  because it is a resource hog.
[22:17] <acmeinc> seems like a lot of work to benefit a select few.  i have a script which opens my audio recording suite in succession, but really, how many people will do the same? my 2c
[22:48] <ScottL> len-dt, dont' sweat about it yet ;)
[22:48] <ScottL> these are just ideas, nothing concrete and i wanted to bring these and others up to the group and try to find a good direction forward
[22:48] <len-dt> ScottL, no sweat, just my two cents.
[22:48] <ScottL> i imagine as we talk through these issues (like you mentioned) we will find our path
[22:50] <len-dt> ScottL, the more ideas we have the more ideas that are left over once we shoot down the unusable ones...
[22:54] <ScottL> len-dt, acmeinc, i saw you talking about the latest image, how did the testing go?  any concerns for release (not small ones)?  is there a reason not to tell #ubuntu-release that it is ready for release?
[22:54] <len-dt> ScottL, I have no concerns...
[22:55]  * len-dt must have missed _something_
[22:55] <len-dt> ScottL, That is with 32bit.
[22:58] <acmeinc> i can finish testing 64 (latest) tonight at midnight...im at work now
[22:58] <len-dt> -queuebot/#ubuntu-release- ISO Tracker: Ubuntu Studio DVD amd64 [Precise Pre-release] has been removed
[22:58] <len-dt> -queuebot/#ubuntu-release- ISO Tracker: Ubuntu Studio DVD amd64 [Precise Final] has been updated (20120425)
[22:59] <ScottL> acmeinc, testing is done my friend :)
[22:59] <ScottL> i have to finish release notes tonight as well and then start emailing people/places/lists
[23:00]  * len-dt is busy trying to figure out backup order for all the computers around here.
[23:01] <acmeinc> well then...