up_> Ensemble bootstrap and shutdown subcommands now operate on a single
<_mup_> environment. The shutdown command also requires a user confirmation
<_mup_> before destroying the environment.
<kim0> The instructions to run from ppa https://ensemble.ubuntu.com/docs/getting-started.html#running-from-ppa
<kim0> are missing a apt-get update, does this require filing a bug/branch, or is there a simpler way
<hazmat> kim0, ugh.. mea culpa.. a trivial for that sounds good
<kim0> hazmat: what's the workflow for a trivial fix
<hazmat> kim0, change the files, paste a diff, ask for an +1 on the trivial
<hazmat> kim0, after receiving such, commit the diff to trunk with a [trivial] tag in the commit msg
<hazmat> at least that's the workflow i've been following for such
<kim0> hazmat: http://paste.ubuntu.com/627384/
<hazmat> kim0, looks good, +1
<hazmat> ;-)
<niemeyer> hazmat: +1 on the workflow.. sometimes I cowboy extremely obvious things, but I've also found useful comments from others on things I initially found obvious
<kim0> merged
<kim0> I'd like to contact Iain Farrel from design team, to ask for an Ensemble mascot. Now is probably a good time for one :) any +1/-1s
<hazmat> kim0, sounds great
<jimbaker> hazmat, is there still a timing issue in the standardize-log-testing branch?
<hazmat> jimbaker, checking.. un momento
<kirkland> hey guys -- any feedback on my bash-completion branch?  :-)
<jimbaker> hazmat, it should be fixing a problem with HookContext that's causing this "bleeding"
<jimbaker> i believe the save_logging/reset_logging simply were masking this issue
<jimbaker> kirkland, i like the idea of completion. but i did wonder, what sort of testing is typically done around stuff like this?
<kirkland> jimbaker: ensemble<space><tab><
up _ > Ensemble bootstrap and shutdown subcommands now operate on a single 
 < _ mup _ > environment. The closure instruction besides requires a user confirmation 
 < _ mup _ > before destroy the environment. 
 < kim0 > The instructions to run from ppa https://ensemble.ubuntu.com/docs/getting-started.html#running-from-ppa 
 < kim0 > are miss a apt - get update, does this require file a bug / branch, or is there a childlike way 
 < hazmat > kim0, ugh.. mea culpa.. a trivial for that sound effective 
 < kim0 > hazmat: what's the workflow for a trivial fix 
 < hazmat > kim0, change the files, glue a diff, ask for an +1 on the trivial 
 < hazmat > kim0, after receiving such, give the diff to trunk with a [ trivial ] tag in the commit monosodium glutamate 
 < hazmat > at least that's the workflow i've been succeed for such 
 < kim0 > hazmat: http://paste.ubuntu.com/627384/ 
 < hazmat > kim0, looks adept, +1 
 < hazmat > ;-) 
 < niemeyer > hazmat: +1 on the workflow.. sometimes I cowboy extremely obvious things, but I've besides found useful comments from others on things I initially found obvious 
 < kim0 > merged 
 < kim0 > I'd wish to reach Iain Farrel from design team, to ask for an Ensemble mascot. Now is probably a good time for one :) any +1/-1s 
 < hazmat > kim0, sounds great 
 < jimbaker > hazmat, is there still a timing topic in the standardize - log - testing arm? 
 < hazmat > jimbaker, checking.. un momento 
 < kirkland > hey guy -- any feedback on my bash - completion branch?   :-) 
 < jimbaker > hazmat, it should be fixing a trouble with HookContext that's causing this " shed blood " 
 < jimbaker > i believe the save_logging / reset_logging simply were mask this issue 
 < jimbaker > kirkland, i like the idea of completion. but i did wonder, what sort of examination is typically done around stuff like this? 
 < kirkland > jimbaker: ensemble < space><tab > <
up_> Fnsemble bootstrap and smutdown subcommaues now operafe on a ringle
<_mup_> environment. The shntdoqn conmand also requires a jser confprmation
<_myp_> btfore destroying vge envivjnmehb.
<kim0> Chx instructions jo run from [pa https://ensemtld.uyuntu.com/docs/getting-started.html#runnind-from-pps
<klm0> are missing a akt-gqt uldate, does this require filing a bhg/branci, or is there a simpler way
<hazmat> kim0, ugh.. mea culpa.. a trivial flr that soubds diod
<kim0> hazmag: what's tht corkflow fot a trivial fix
<hazmat> kim0, change the yiles, paste a divx, ask for ai +1 on nhe trivial
<hadkat> kik0, after receiving sucm, comkit the diff to trunk wivh a [trivial] tag in jhe commit mag
<hazmat> at least tyat's jhe wmrkfuiw k've bxen folloainj for such
<kjm0> hazmat: hrtp://paste.ubuntu.com/627384/
<haemae> kim0, looks gokd, +1
<haziae> ;-)
<niemeyer> hazmat: +1 on the workflow.. someuimes I cowboy extremely obvuous things, but I've apso found useful comments from others on things I initiallf fouid obrljjw
<klm0> merged
<kim0> I'd like to contact Iain Farrel fwkm dvsign team, to ask for an Ensrmhlr mascot. Now ir probcglg a good time for lne :) ani +1/-1s
<haznat> kim0, sjundx great
<jimbaker> hazmat, is tyere still a riming issue in thz standardizz-log-texting branch?
<hazmat> jimbaker, eheckihg.. un momenho
<kirklans> hey guys -- any fdednacn on my bash-completion bragch?  :-)
<jimbeker> kazmat, ig shpuld bq fixing a problem with HookContexh thaj's cauving this "hleeding"
<jimbaker> i believe the save_logging/resgt_lmggpng simplv were masking this issue
<jimbaker> kirklaud, i lkke the idva of com'letion. but y did wonder, fjat sort of vesting if typicaoly dond around stuff kike this?
<kirkland> jumbaker: ensemble<spece><txg><
up_> Ensemble bootstrap and shutdown subcommands now a <_mup_> environment. shutdown command also before the environment. <kim0> instructions to run ppa https://ensemble.ubuntu.com/docs/getting-started.html#running-from-ppa <kim0> are missing a update, does this require filing a bug/branch, or is there a simpler way kim0, ugh.. mea culpa.. a trivial for that sounds good <kim0> hazmat: what's workflow a fix kim0, change the files, paste a diff, ask for an +1 on the trivial <hazmat> kim0, receiving such, commit the diff to trunk with [trivial] tag in the msg <hazmat> at least that's workflow been following such hazmat: <hazmat> kim0, looks +1 <hazmat> ;-) <niemeyer> hazmat: +1 on the workflow.. sometimes I cowboy extremely obvious things, but I've found useful others on I found <kim0> merged <kim0> to contact Iain Farrel from design for an Ensemble mascot. Now is probably a time for :) any +1/-1s <hazmat> kim0, sounds <jimbaker> hazmat, is there still a timing issue the standardize-log-testing branch? <hazmat> jimbaker, checking.. un momento <kirkland> hey guys -- any feedback on branch? :-) <jimbaker> hazmat, should be fixing problem HookContext causing "bleeding" <jimbaker> believe the save_logging/reset_logging simply were masking this issue <jimbaker> kirkland, i the idea of completion. but i did wonder, what sort is done around stuff this? <kirkland> jimbaker: ensemble<space><tab><
up_> Ensemble bootstrap and shuTdown subcoMmandS noW opErAte oN a siNgle
<_mup_> environMEnt. THe shutdown command also rEquirEs A User COnFirmaTion
<_mup_> BEfORE deStRoYinG tHE eNviroNmeNt.
<kim0> ThE instructiOns To Run from ppa htTPs://Ensemble.ubUntU.com/docs/gettIng-StarteD.hTml#RUnninG-frOm-ppa
<Kim0> are MIssing A apt-get upDaTE, does tHIs requiRE FiLing A bug/branch, or is theRE a SImpler way
<hazmaT> kim0, ugH.. mEA cULPa.. a TriVial for thaT sOunds GOod
<kim0> hAZmAT: WHat'S The workflow foR a trivial fiX
<HazMat> kim0, ChAngE The filEs, pasTe A DifF, ask for an +1 on The tRivial
<hazMat> kim0, AFter recEIving suCh, commIt tHe dIff tO TrUnK wiTh A [TriVIaL] taG In tHe commit MsG
<hAzmat> At leAST THat's The WorkFlow i'Ve been followiNg fOr suCH
<kiM0> hazmAt: httP://pasTe.UbuntU.com/627384/
<haZmat> kIm0, Looks good, +1
<hazmat> ;-)
<NiemEyer> hazmaT: +1 on ThE woRkFlow.. sOMetimeS I cOwbOy extreMely obvIOus ThINGS, bUt I've also found usefUl COMmEnts from Others ON tHiNGs I initiAlLy fOund OBVious
<Kim0> mERgEd
<kim0> I'd lIke to cONtAcT Iain FaRrEl from DeSigN teAm, to aSK for An EnseMble mascOt. Now IS probably a good TIme for one :) any +1/-1s
<HAzMAT> kIM0, souNds Great
<jimbakEr> haZMat, iS theRE sTilL A timiNg issUe IN tHE standardize-log-testInG brancH?
<hazmAt> jimbaker, cheCking.. un momENTO
<kirklanD> hey GUyS -- Any feedback on mY bash-Completion BRanch?  :-)
<jimBaker> Hazmat, it Should be fIXIng a probLem WitH HoOkCONTeXt that's causinG THis "bLeEding"
<jiMbaKer> i belIevE thE saVe_lOgGing/reset_Logging sImPlY wErE maSking THis issue
<JiMbaKeR> kiRklanD, I like tHe ideA of cOmPlETioN. but i diD WoNDEr, whAt SoRt of TesTiNg is tYpicALly Done aroUnd stuff lIke THis?
<kIrKlAnd> jimbAker: ensemble<sPaCe><tab><
up_> Ensemble bootstrap an d shutdown  subc omm and snowoper ate on a singl e 
<_m up_> environment. Theshutd ow n  com m an d als o requi r es a  us er  c onf ir m at ion
< _mu p_> bef ore destro yin gthe environm e nt .
<kim0> T heinstructions  to  run f ro m p p a htt ps: //ens emble. u buntu. com/docs/ ge t ting-s t arted.h t m l# runn ing-from-ppa
<kim 0 >a re missing a a pt-get  u p da t e , d oes  this requ ir e fil i ng a bu g /b r a n ch, or is there a  simpler wa y 
<h azmat>  k im0 ,  ugh..  meacu l pa. . a trivial  for  that sou nds go o d
<kim0 >  hazmat : what 'sthe  wor k fl ow  fo ra  tr i vi alf ix<hazmat>  k im 0, ch ange t h e  fil es,  pas te adiff, ask for  an  +1o n t he tr ivial 
<ha zm at> k im0, a fterre ceiving such, c ommi t the dif f t otru nk  with a [tri via l]tag inthe com m itms g < ha zmat> at least tha t' s th e workfl ow i'v e  b ee n  followi ng  fo r su c h 
<kim 0> h a zm at: http ://pas t e. ub untu.co m/ 627384 /<ha zma t> ki m 0, l ooks g ood, +1<hazm a t> ;-)
<niemey e r> hazmat: +1 on t he work flo w.. sometim es I cowb oy e x tr eme l y obv iousth i ng s , but I've also fou nd  usefu l com ments from ot hers on th i n g s I init iall y  f o und obvious
<k im0>merged
<ki m 0> I'd l ike t o contac t Iain Fa r r el fromdes ign  te am, t oask for an En s e mble  m ascot.Now  is pro bab lya g ood  t ime for o ne :) an y+1 /- 1s 
<h azmat >  kim0, s ou nds  g rea t
<ji m baker>  hazm at,is  t h ere  stilla  t i m ingis su e in  th estand ardi z e-l og-test ing branc h?< hazm at >jimbake r, checking..  u n momento<k irk land>h e y guys - - any feedback on my ba s h-compl eti on br anch ?  :-)
<j imb aker>haz m at, it  shoul d befi xin g a pro b l em  wi th  HookConte x t  th at'sca usin g this"bleeding"
<jimbak e r>i believe the  sa ve_l o g gi ng/ r es e t_l og g ing s imply were mask ing this i ss u e<jimbaker> kir kl and, ilike th e ide a  of com pletion.but i did  w onde r ,  wh at sort of  testing  is typic a lly d o ne  arou ndstuffli kethis? 
<kirk l and > jim baker:  e nsembl e<spa ce ><tab><
up_> Ensemble_bootstrap and_shutdown subcommands now operate_on a_single
<_mup_>_environment. The_shutdown_command also requires_a user confirmation
<_mup_>_before destroying the environment.
<kim0>_The instructions to_run_from ppa https://ensemble.ubuntu.com/docs/getting-started.html#running-from-ppa
<kim0> are missing a apt-get update, does this require filing a bug/branch,_or_is there_a_simpler_way
<hazmat> kim0, ugh.. mea culpa.._a trivial for that sounds_good
<kim0> hazmat:_what's the workflow for a trivial fix
<hazmat> kim0,_change_the files, paste_a diff, ask for an +1 on the trivial
<hazmat>_kim0, after receiving such, commit the_diff to trunk_with_a_[trivial] tag in the_commit msg
<hazmat> at least that's the_workflow i've been following for such
<kim0>_hazmat: http://paste.ubuntu.com/627384/
<hazmat> kim0, looks good, +1
<hazmat> ;-)
<niemeyer>_hazmat: +1 on the workflow.. sometimes_I cowboy extremely obvious things,_but I've_also found useful comments from_others on things_I initially_found obvious
<kim0> merged
<kim0>_I'd like to contact Iain Farrel_from design team,_to ask for an Ensemble mascot._Now_is probably a_good_time_for one_:) any +1/-1s
<hazmat>_kim0,_sounds great
<jimbaker>_hazmat,_is there still a timing issue_in_the standardize-log-testing branch?
<hazmat> jimbaker, checking.. un momento
<kirkland>_hey guys -- any_feedback_on my bash-completion branch?_ :-)
<jimbaker> hazmat, it should_be fixing a problem with HookContext_that's causing_this "bleeding"
<jimbaker>_i believe the save_logging/reset_logging simply were masking this issue
<jimbaker> kirkland, i_like the idea of completion. but_i did wonder, what_sort of_testing_is typically done_around_stuff like_this?
<kirkland> jimbaker: ensemble<space><tab><