#ubuntu-uds-community-1 2013-03-05
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Track: Community | Testing ubuntu onÂ new platforms | Url: http://summit.ubuntu.com/uds-1303/meeting/21669/community-1303-quality
<smartboyhw> hello
<zyga-uds> hey everyone
<SergioMeneses> smartboyhw, \o
<jono_> #ubuntu-uds-community-2
<balloons> hey everyone.. this should be a fun first session
<jono_> #ubuntu-uds-community-2
<jono_> oops
<smartboyhw> baloons please give me updates of session as I'm on mobile and not enough bamdwidth for Hangout
<SergioMeneses> jono_, jajaja
<balloons> smartboyhw, ahh
<smartboyhw> jono_ what's room 2 on about?
<balloons> zyga-uds, mmrazik u guys wanting to join in the hangout?
<SergioMeneses> balloons, we're going to have a fun session :D
<balloons> anyone else? trying to make sure we have proper folks in the session
<zyga-uds> balloons: yes
<ogra_> what are the proper folks ? :)
<zyga-uds> balloons: I'm interested to know how this overlaps with hardware certification
<smartboyhw> I would lov to if I had my computer here.............
<smartboyhw> lol
<mmrazik> balloons: I can if there are enough hangout slots but I don't have to
<smartboyhw> eh?
<SergioMeneses> dholbach, balloons hi!
<smartboyhw> mmrazik: I think we have enough...
<smartboyhw> uhoh zyga-uds left
<ogra_> plars, ! what a beard !!!
<smartboyhw> lol
<plars> ogra_: :)
<smartboyhw> So who's on Hangout?
<dholbach> smartboyhw, I'm on the left ;-)
<VencaCZ_> where i can get hangout adress?
<dholbach> VencaCZ_, http://summit.ubuntu.com/uds-1303/meeting/21669/community-1303-quality-testingstrategy/
<VencaCZ_> ty
<smartboyhw> dholbach I"m on mobile how can I see?
<dholbach> smartboyhw, http://www.youtube.com/watch?v=D7LpRcllyYA
<diwic> dholbach 's video feed disappeared
<dholbach> diwic, can you see the other people's feeds?
<ogra_> dholbach, just you
<ogra_> (are gone)
<smartboyhw> dholbach There was a problem while playing
<ogra_> ah, back
<smartboyhw> Touch to retry.....
<diwic> dholbach is back
<dholbach> do you see whoever's speaking?
<zyga-uds> is that testing stack public? how can other developer use it?
<ogra_> dholbach, yup
<dholbach> I just momentarily stopped my video feed to try out something else
<dholbach> you don't need to see me ;-)
<dholbach> I'm not really part of this discussion :)
<smartboyhw> dholbach I can't get to it....
<dholbach> smartboyhw, it's just a normal youtube video?
<ogra_> dholbach, but you have the funniest headphones !
<diwic> dholbach, ok, just made sure you were aware
<dholbach> diwic, thanks
<dholbach> ogra_, I like them :)
<dholbach> ogra_, shall I use these instead?
<cwayne> +1 exploratory testing
 * ogra_ didnt say he doesnt :)
<zyga-uds> what kind of tests are you running? is that testing the software stack more or the hardware enablement?
<sebsebseb> hi
<gema_uds_> hi
<smartboyhw> dholbach: There was a problem while playing. Tap to retry
<cjohnston> smartboyhw: it sounds like you are having trouble with your mobile and playing hangouts. there isn't really anything we can do about htat
<smartboyhw> yeah
 * smartboyhw condemns his ARMv6 A
<smartboyhw> Samsung Android
<balloons> zyga-uds, did your question get answered?
<zyga-uds> plars: where is the dashboard?
<dholbach> anyone else who wants to be part of this discussion? who wants to be part of the "fishbowl"? :)
<zyga-uds> balloons: I don't think so
<cjohnston> zyga-uds: reporst.qa.ubuntu.com I believe is what he is referring to
<zyga-uds> dholbach: I would love to be
<gema_uds_> zyga-uds: http://reports.qa.ubuntu.com/
<cjohnston> reports too.. ^
<gema_uds_> cjohnston: you don't know the URL yet? :P
<cjohnston> I don't know how to spell
<dholbach> zyga-uds, sent you a link in an irc query
<cjohnston> and I don't use the URL
<mmrazik> took an external USB cam :)
<dholbach> mmrazik, might want to mute yourself while typing ;-)
<cjohnston> mmrazik: mute yourself while your playing
<zyga-uds> dholbach: it works but I don't know how to attend, I guess I have to reload -- typing in private does not work
<mmrazik> balloons: srry. It must be when I plugged the camera in. it has yet another mic
<dholbach> zyga-uds, does http://summit.ubuntu.com/uds-1303/attend_meeting/21669/ work?
<vila> mute the dog ;)
<zyga-uds> reloading didn't help, sorry
<zyga-uds> I lost the previous message
<cjohnston> zyga-uds: what are you wanting?
<gema_uds_> we are still working on the views for memory and eventstat
<gema_uds_> those views are not in production yet
<ogra_> zyga-uds, !
<balloons> anyone else wish to join in the hangout.. or have questions?
<ogra_> balloons, well, i'D really like to know how we plwan to handle the android parts, they are an essential bit of phablet (no need that i'm in the hangout though)
<balloons> u can pop in for a moment if you wish to ask
<dholbach> balloons, ogra_ would need to get dressed first :-P
<smartboyhw> lol
<ogra_> lol, no, i'm showered and dressed, but couldnt say much beyond that
<VencaCZ_> where i can get source for ubuntu mobile? i want part it for my phone
<VencaCZ_> port
<diwic> I'd just like to say I really appreciate the community resources we have for testing; e g before releasing a new PulseAudio version into 13.04 we were able to have some community people testing it in a PPA. Thanks to everyone helping out with this!
<ogra_> VencaCZ_, in #ubuntu-tablet :)
<VencaCZ_> ok ty
<ogra_> LOL, ok
<ogra_> someone paste me a link
<ogra_> hmm, the join button just hangs :/
<cjohnston> ogra_: are you referring to the fact that the phablet image currently uses Android stuff, and are we going to keep that in the image or remove it?
<ogra_> cjohnston, we will keep it
<cjohnston> was taking a shot in the dark to see if I could interpret the question
 * ogra_ canzt join it seems, sorry
<balloons> ogra_, ahh.. well try rephrasing the question then ;-)
<ogra_> well, how do we make sure we get testing of the android layer in the phablet images, automated and by manual community testing
<dholbach> does the hangout still work? for me it just broke
<diwic> broke here too
<vila> googgle hangout just broke
<josepht> broke for me too
<cgregan_> down here too
<cking> broke for me
<dholbach> bah
<vrruiz> Yup
<rfowler_> uh oh
<ogra_> same here
<zyga-uds> try reloading
<cjohnston> works for me
<ogra_> yep, works again
<balloons> whoa.. a bit a hiccup
<SergioMeneses> reload it
<vrruiz> Back
<plars> we're stress testing google hangout today!
<vrruiz> lol
<ogra_> note that ubuntu just runs in a container on top of a minimal android
<ogra_> its not just the kernel
<ogra_> its a full minimal android
<ogra_> the complete HW stack is android
<ogra_> (way more than the kernel)
<ogra_> it is waht we currently have and will very likely also keep
<ogra_> we need that part since we dont have any other way of getting drivers
<gema_uds_> ogra_: do you want to try to join the hangout again?
<ogra_> gema_uds_, i tried over and over, the "join" button is greyed out
<gema_uds_> ogra_: you need to click on the acceptance button that you don't mind your image to be broadcasted
<gema_uds_> did you click on thata?
<ogra_> the driveras also require the userspces framework
<ogra_> gema_uds_, i didnt have that
 * ogra_ tries again
<ogra_> bah !
<cking> but the android kernel has not been tested with our user space, so it makes sense to test it
<dholbach> mmrazik, balloons^
<Limurx> hey daniel :D
<dholbach> hi Limurx :)
<balloons> cking, yes, i agree
<vila> testing all layers is good, testing each layer is good, in the end we'll need all kind of tests
<vila> but starting with the autopilot ones, testing all layers at least give us some guarantee that things will run for the user
<vila> devs will prefer to know which layer is at fault when something breaks though...
<udsbotu> uds-community-1: 5 minutes left in this session!
<smartboyhw> uh oh
<udsbotu> uds-community-1: 4 minutes left in this session!
<ogra_> vila, exactly, i just wanted to make aware that we need code for that ... i.e. we dont use the ubuntu input layer at all in the phablet images
<joe-uds> are there virtual environments for those w/o HW to use for testing?
<dholbach> ogra_, muted you while typing
<ogra_> joe-uds, we will have a discussion about VM and emulator at 7pm in the SDK session
<cking> ogra_, perhaps a work items is for you to figure out what needs testing
<ogra_> dholbach, thanks
<ogra_> cking, sure
<udsbotu> uds-community-1: 3 minutes left in this session!
<vila> ogra_: good point, I think someone mentioned that the autopilot session later will need to care about that
 * ogra_ wont be able to attend many more testing session, thats why i'm here and thourgh i shoudl bring it up :)
<ogra_> *thought
<udsbotu> uds-community-1: 2 minutes left in this session!
<ogra_> mmrazik, we might just build x86 android/phablet images
<ogra_> to run in any VM you like
<mmrazik> ogra_: yup. might be one of the options
 * joe-uds claps
<udsbotu> uds-community-1: This session has ended.
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-1303/community-1/ - http://ubottu.com/uds-logs/%23ubuntu-uds-community-1.log
<Limurx> Gonna be a hot discussion right now ;)
 * mainerror takes seat
<mainerror> These walks from room to room are exhausting ...
<stgraber> dholbach: can you invite me to the hangout for community-1303-rolling-release? (assuming you're the one running it)
<cjohnston> stgraber: if you are required then the link is available for you in summit
<dholbach> stgraber, above the video there should be link
<stgraber> cjohnston, dholbach: right, refreshing fixed it
<FunnyLookinHat_> Who is running this session? jono ?
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Track: Community | Should Ubuntu adopt a monthly cadence/rolling release? | Url: http://summit.ubuntu.com/uds-1303/meeting/21683/community-1303-rolling
<YoBoY> FunnyLookinHat_, it's dholbach
<dholbach> YoBoY, salut mon ami
<YoBoY> bonjour, comment Ã§a va ? :)
<FunnyLookinHat_> dholbach, CarlRichell and I are here from System76 and we'd love to be pulled into the Hangout if there's room
<rickspencer3> YoBoY, stgraber nous parlons en franÃ§ais pout cette session?
<dholbach> trÃ¨s bien - et toi - il fait beau ici - beaucoup de soleil Ã  Berlin
<rickspencer3> hi FunnyLookinHat_
 * philipballew feels language isolation
<FunnyLookinHat_> rickspencer3, Yo
<YoBoY> rickspencer3, avec plaisir :)
<rickspencer3> dholbach, can you invite the System76 guys?
<jcastro_> heya CarlRichell!
<CarlRichell> heya Jorge!
<cjwatson> pgraner: Can you include me in the hangout for this one?
<philipballew> if you need more people to give a "loCo" perspective, I can join the hangout here as well.
<YoBoY> dholbach, un peu malade, mais il fait beau aussi :)
<cjwatson> dholbach: ^- or if it's you
<FunnyLookinHat_> Go ahead and invite Carl on Gplus
<FunnyLookinHat_> he's driving the webcam
<pgraner> cjohnston, https://plus.google.com/hangouts/_/f087d7d5109cb66b16cbbdb4b4c7153a846ee9f6
<cjwatson> Shame that this session has conflated rolling release and monthly cadence, which really have a bunch of separate issues associated - I'd suggest that people try to work separately
<cjohnston> pgraner: do you mean me?
<pgraner> cjohnston, no cjwatson  ^^^^^^^^
<cjwatson> ta
<pgraner> cjohnston, change your nick damn it
<cjwatson> 1 2 3 tab
<cjohnston> pgraner: no.
 * mitya57|uds tries to fix his microphone
<mitya57|uds> does anybody hear me
<mitya57|uds> ?
<philipballew> not currently mitya57|uds
<fisch246> ha people are already using Mir... why would you do that this early?
<snwh> oh those crazy bleeding-edge folks
 * mitya57|uds hopes he fixed it
<dholbach> does it work for you too?
<pitti_uds_> if "it" == video, then not yet
<Laney> i had to refresh
<Laney> works now
<philipballew> video is great
<dholbach> perfect
<me4oslav> video is great on this end too
<snwh> finally got video :D
<jonobacon> pitti/Laney - did you want to join?>
<Laney> sure
<ahayzen> o/
<jonobacon> dholbach: can you invite Laney?
<mitya57|uds> ok, looks like it still doesn't work, so I'll just sit in IRC
<dholbach> jonobacon, yep
<gema_uds2> mitya57|uds: reload the page
<mdeslaur> how is this any different than os x that comes out every 18-24 months?
<mpt> Windows often goes years between versions. OS X recently switched from new versions every 18-24 months to a new version every 12 months.
<dholbach> people marked as bold at the bottom of the page should have a link saying "join hangout" or some such above the video
<rbasak> CarlRichell: what would be your ideal cadence then? Six months still? Or something else?
<mitya57|uds> gema_uds2: well, anyway I don't have much to say :)
<philipballew> How does this affect LoCo's who need to advocate the rolling release? Or should we be showcasing the lts release only?
<jcastro_> mdeslaur: people can install new software on old OSX/Windows easily, not so much in ubuntu
<slangasek> hmm, I certainly wouldn't agree that every Ubuntu release has been better than the previous
<jcastro_> mdeslaur: if you want a newer libreoffice for example, you're either  in backport or PPA land.
<timrc> Is it weird that I can actually picture adconrad happily frolicking in fields of time, money, and cheesecake?
<mdeslaur> jcastro_: that's a different problem, and one that will kind of solve itself if everyone is using LTS
<jcastro_> mdeslaur: on other OSes that's just a quick download for users
<slangasek> they may be more fit to purpose at the time they come out due to changes in the requirements for software
<slangasek> but I don't think each Ubuntu release has been "better"
<dobey> windows releases approximately every 5 years
<tumbleweed> dobey: I suspcet that may speed up now
<xnox> System76Chi: are you providing security support beyond 18m cycle? or do you upgrade all of their users to next non-lts?
<victorp__> rickspencer3: we (in canonical) are working with HP,DELL and Lenovo PCs and Laptops only using LTS releases already
<xnox> System76Chi: i don't want to buy laptop which will star saying it's obsolete in less than 12months.
<tumbleweed> I think if we have less releases putting more work into LTSs would be vital
<victorp__> so I am not sure OEMs do what quicker cycles for PCs
<mpt> Windows Vista, 2006-2007: Windows 7, 2009: Windows 8, 2012.
<victorp__> specially thanks to the hardware updates in point releases
<barry> http://en.wikipedia.org/wiki/Os_x
<TheMuso> mpt: Agreed, WIndows every 2 years.
<TheMuso> OS X was every 2 until last year.
<barry> (scroll down for versions - release dates are ~2yrs)
<snwh> albeit XP still has a huge chunk
<snwh> rolling release would avoid version stagnation if updates are continuous
<dmj_nova> People don't care that things don't change, they care that they don't break unpredictably
<mpt> Some different meanings of "stability": (1) error rate <http://errors.ubuntu.com/> (2) amount of UI change (3) amount of API change (4) number of SRUs
<tumbleweed> snwh: the plans look like just dropping 6-monthly releases, not doing significantly more work on the development release than happens at the moment
<gQuigs> so let's cut support for the 6 month release to 8 months?
<dmj_nova> Who will the rolling release be suitable for?
<mdeslaur> dmj_nova: developers, and tech enthusiasts
<smartboyhw> Why don't we release 13.04, cancel 13.10 and make it rollling for a year, then review and see of we are to implement only LTSes + rolling release forever?
<jonobacon> mpt: do you want to join the session?
<xnox> Would you ship rolling?
<snwh> tumbleweed, oh yes I know :)
<dmj_nova> 2 years is *far* too long to go without a stable system with fresh software
<mpt> dmj_nova, "software" is a vague term
<tumbleweed> dmj_nova: for some classes of users, not all
<dobey> dmj_nova: what do you mean by "fresh" there?
<mpt> in this context, at least
<slangasek> dmj_nova: this comes back to the disagreement about what "stable" means
<me4oslav> is 2 years, really THAT much? People still stick to god know how old XP.
<dmj_nova> Would you recommend the rolling release in production environments (workstations, not servers)
<slangasek> I would not
<dobey> no
<mdeslaur> no
<me4oslav> no
<slangasek> I wouldn't recommend the 6-month releases in a production environment either
<slangasek> I only recommend the LTS
<dmj_nova> me4oslav: it can be a huge amount of time, especially with a fast-moving platform
<YoBoY> I only recommand LTS in production enviironments
<slangasek> I only *deploy* the LTS on family machines that I have to support
<mathor> I think the argument is that 12.10 wasn't completely stable in comparison to 12.04. With features you lose stability. That is all a rolling release is suggesting.
<dmj_nova> Already, we are having trouble supporting Precise
<slangasek> dmj_nova: what trouble, why?
<dmj_nova> (without backporting gstreamer, webkit, python, udisks2, etc
<mdeslaur> dmj_nova: hrm?
<dobey> slangasek: the thing cjwatson is saying in the hangout right now
<txwikinger-uds> Already using "rolling releases" on different level in production environment
<pmk1c> I also only recommend LTS, since most of the people I recommend Ubuntu to are used to Windows. They would be irritated by updates more regular than every 2 years.
<xnox> CarlRichell: would you ship rolling ?
<dobey> we have too many releases to support at once, so it's difficult to spend time both developing the new release and supporting all the existing releases
<dmj_nova> the alternative being to stick with old tech until the next LTS (and thus not track upstream at all)
<philipballew> Its to risky as somene recommending software to someone to recomend that is not lts for nots us, and the user. There computer is more likely to not funtion well with Ubuntu, and cause their Ubuntu experience to not be as good as it might be.
<noahl> what about either a) reducing the support for the 6-month releases
<mathor> 12.10 was buggy, and a daily iso will be buggy, but both are stable enough to use if you do not need complete stability, which you can only get in an LTS.
<jdstrand> cjwatson: firefox is also self-contained
<dmj_nova> pmk1c: Windows ismoving to a yearly cycle
<noahl> or b) using a different cadence for different "levels" of system? So maybe glibc is on a 2-year cycle, but Unity is on 6 months?
<slangasek> dobey: I was asking dmj_nova what trouble they were having in particular, not what trouble *Ubuntu* has had supporting the LTS
<slangasek> I'm well familiar with the latter :)
<dobey> dmj_nova: you're working under the assumption that LTS will *never* get updates
<dmj_nova> slangasek: basically it was beginning to take about 3 man-days to backport every month
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Track: Community | Should Ubuntu adopt a monthly cadence/rolling release? | Url: http://summit.ubuntu.com/uds-1303/meeting/21683/community-1303-rolling-release/
<dobey> slangasek: ah, I read that as the royal "we" :)
<tumbleweed> shipping hardware with a dev release sounds crazy
<mdeslaur> dmj_nova: backporting what?
<cjwatson> jdstrand: well.  yes it mostly is now that we threw all the extensions out of the archive ...
<YoBoY> for the ubuntu documentation (in my langage) it's also hard to support lot of branches, but I don't know how we will support a rolling release yet, seems tricky tooâ¦ :]
<cjwatson> (almost all, actually - there are still a few)
<pitti_uds_> rickspencer3: I hope it's not yet decided whether we do the monthly release thing at all? (as opposed to monthly planning and install images)
<dmj_nova> in this case we were backporting gstreamer 1.0 and a couple other things
<slangasek> dmj_nova: I don't understand what your use case is that you need backports of "gstreamer, webkit, python, udisks2, etc"
<achiang> tumbleweed: and yet, OEMS supported by Canonical did precisely that. in the *bad* old days
<mainerror> Google Chrome
<tumbleweed> achiang: not with daily updates
<slangasek> dmj_nova: the "old" tech is the /stable/ tech - why would backporting python, gstreamer, etc be a priority for you?
<dmj_nova> and also having to hold back on using useful new functionality from updated versions of say python
<jdstrand> cjwatson: sure. point I was making that unlike unity, it is more or less a leaf application
<vila> rickspencer3: I think most devs want to run their own "trunk" may are more conservative with everything is that is not part of their strong dependencies
<achiang> tumbleweed: i think we're agreeing? shipping hardware with a dev release is crazy
<tumbleweed> achiang: :)
 * mitya57|uds agrees with infinity's mail â it's not a good idea to leave "monthly" users without critical updates
<jcastro_> CarlRichell: Server users. :)
<vila> rickspencer3: getting updates from everybody at once may not suit everybody
<tumbleweed> achiang: but slightyl less crazy, if it' sa snpshot of a dev release, with security support
<dmj_nova> slangasek: there's a big difference between "latest stable" and "old"
<smoser_> i think "real users" want the LTS.  they are generally annoyed by windows downloading updates and rebooting 6 times.
<Darkwing> I'm on LTS because ATI drivers don't work with anything later right now.
<gQuigs> so the rolling release would be our general release, and LTS is for those who need really really stable things?
<smoser_> they want stuff to work and to use their OS.
<achiang> tumbleweed: not from my POV. LTS is the only thing that makes sense to support OEMs on from where i sit
<jsjgruber-uds> they may also be adding their own software that has dependencies
<FunnyLookinHat_> jcastro_, I'm not sure "server users" should be using LTS though.
<mpt> The more of an OS's user base is made up of institutions, the slower that user base upgrades on average, so the longer the optimal release cycle.
<tumbleweed> achiang: well, it comes with free security support from canonical...
<mathor> LTS systems support schools, office buildings, etc.  My university runs 12.04, and they cannot afford to change every six months, so they stick with the LTS.
<cjwatson> Universities indeed love LTS releases
<FunnyLookinHat_> jcastro_, There are better tools available to address the issues of stability + managing updates ( a la Landscape ) that are much more elegant and efficient, right ?
<cjwatson> Because upgrading a PhD student's laptop in the middle of their three/four/whatever-year PhD is REALLY BAD
<philipballew> I dont want people showing up to my Ubuntu hour complaining "Their Ubuntu is not working" and this is because they installed a dev release. Even the not lts release now is unsafe to the average user who does not want any problems.
<kyleN> does it make sense to find a middle ground on LTS period: perhaps yearly
<jcastro_> FunnyLookinHat_: most server users I know want/need the 5 years of support of an LTS.
<slangasek> dmj_nova: I don't really feel that you're articulating why this difference matters in your case.  I can't imagine ever taking a decision to backport a newer version of infrastructure like gstreamer and python instead of just using the platform that exists.
<mdeslaur> maybe we need a separation between the OS itself, and the apps such as LibreOffice...you want the OS to be stable, but you want to get the latest libreoffice
<pitti_uds_> TBH, most of my family and friends is using LTSes, too -- much less hassle and potential breakage of what you got used to
<jdreed> Universities also liked the interim releases, because their user base of enthusiastic undergrads was clamoring for the latest software.
<Darkwing> If ATI, Nvidia and others would keep their drivers updated, I would be good. But, I can't run my desktop without LTS.
<mpt> That explains why mobile OSes have new versions more frequently, for example
<cjwatson> (I've heard this specifically from University of Cambridge sysadmins)
<smoser_> the number, frequency and size of updates honestly make using any sort of ubuntu development release unreasonable.
<sbeattie> mdeslaur: +1
<rbasak> There's a whole class of users who are happy with the software they have and don't need anything newer. For them, it's easier if things don't change on them all the time.
<ev> mdeslaur: +1;
<FunnyLookinHat_> jcastro_, how many people do you know using 8.04 ?  I know none.  :)  A two year upgrade schedule is more than reasonable for many use cases
<xnox> mpt: sure but enterprise managed phones are upgraded every 18m.
<noahl> mdeslaur: +1
<olafura> The problem with rapid updates is Update Manager which is stupidly slow, maybe use apt demon with indicators. And most importantly Libreoffice and a lot of other debs are just to big.
 * achiang is still using 12.04 quite happily
<dmj_nova> slangasek: using the old gstreamer would mean investing significant development effort improving undeveloped old branches
<xnox> mpt: or not updated at all.
<smoser_> over the course of any development cycle, we're probably looking at a 700M delta in downloads every week.
<slangasek> mdeslaur: I'm much more nervous about behavior changes in applications than I am in the base OS :)
<rbasak> Sometimes one of these users finds he needs something newer, and then he's happy to trade of for the latest release (or rolling release or whatever)
<jcastro_> FunnyLookinHat_: plenty of people using 12.04 (and there's probably 8.04 around as well)
<dmj_nova> It would be like us developing in linux kernel 2.4
<smoser_> that is absurd to believe is acceptable for any consumer level user.
<smoser_> (server or desktop)
<cjwatson> Right, the university use case where behaviour changes are scary is absolutely about applications, not the base OS
<mainerror> My family uses interim releases ever since 10.04
<mpt> olafura, Update Manager aka Software Updater already does use aptdaemon. Adding indicator pixie dust wouldn't make it any faster. :-)
<timrc> achiang, I tried to stay on 12.04 but running armhf lxc containers on Raring is so much better :)
<dobey> dmj_nova: as novacut is not a stable application/system, and it's a seriously complex system, i think targeting the LTS at this point is probably just a poor decision for novacut
<philipballew> We update Firefox in lts, and all people generally do for computing these days i live in a browser. Especially people who do not need anything beyond an lts.
<cjwatson> If your scientific application changes its syntax three months before you submit that's disastrous
<mainerror> Not quite sure what stability issues everyone is talking about.
<mitya57|uds> I am using quantal currently, but it's already hard to develop raring from quantal â for me mostly because of python 3.2 vs 3.3
<dmj_nova> dobey: yes
<FunnyLookinHat_> jcastro_, Yeah - I understand what you're saying... I guess my point is, the reasons that people take slow upgrade paths can be replaced with better solutions...  we've stopped trying to reform the process and instead are using the same processes that we did in 1999
 * balloons pops in
<xnox> stgraber: and victorp__ win the best backdrop award of this hangout.
<dmj_nova> However, as we are NOT targeting hobbyists
<olafura> mpt my problem is that it's tied to the update process
<dobey> dmj_nova: once novacut is an actual stable product, you will almost certainly want to only target the LTS
<dmj_nova> so we have to consider the cycle once we are ready for professionals
<olafura> mpt I use apt-get, most of the time
<mpt> olafura, if you want updates to be faster, there are a bunch of ideas at <https://wiki.ubuntu.com/SoftwareUpdates#Ideas>
<philipballew> It's more trouble for me to recommend something thats not a lts.
<dobey> dmj_nova: you can't choose to support both a stable platform, and a constantly changing platform, without a cost
<rbasak> rickspencer3: good summary. +1
<cjwatson> We really ought to sort out the half-completed debdelta project
<dmj_nova> We will likely have issues with recommending Rolling release
<FunnyLookinHat_> What's the solution for ISVs who need to update software frequently, but also be able to target solid releases ( instead of a rolling / moving target ) ?
<tumbleweed> cjwatson: that'd be fantastic
<smoser_> i think that anyone "non-geek" probably hates updates
<dmj_nova> 6 month cycles are different
<dobey> dmj_nova: we have the same problem with Ubuntu One. there is a cost to supporting multiple versions of Ubuntu, and we're currently paying that cost to do so
<txwikinger-uds> On server you might no change ubuntu release but you change i.e. ruby via rvm.. or drupal
<mainerror> I mean they generally don't feel any difference between an LTS and interim version. As the supporter I don't feel any difference either.
<cjwatson> (Since people keep bringing up upgrade bandwidth volume issues)
<smoser_> on windows, on OS/X, on iphone ....
<dmj_nova> we could easily recommend them because they're at least predicable
<smoser_> they do not want their OS to change. its just an annoyance.
<achiang> +1 smoser_
<cjwatson> smoser_: Or their applications
<smoser_> maybe hteir applications.
<smoser_> yes, there is some sort of line there.
<cjwatson> Usually applications changing is even worse
<smoser_> and that is hard to identify.
<cjwatson> Because they're the things you interact with directly and learn
<smoser_> (i do go into the app store and look for updates)
<rbasak> Do we need to move on?
<dobey> dmj_nova: then novacut made a poor decision to build on an unstable platform, instead of the stable one. you need to find the balance between what your users need and what you want to build, and make necessary compromise
<mdeslaur> cjwatson: but it seems to be accepted on all other oses and devices
<utlemming> smoser_: to your point...one of the things that I hate about android is how my apps are always updating.
<jsjgruber-uds> QUESTION: It seems to me that people fix the easy bugs as they come up but the hard ones wait for the freeze. I think that's human nature. Will the freeze time be extended for this to happen for the LTS releases? Will people have the energy (and patience) to fix difficult bugs that have accumulated over 2 years.
<timrc> It's probably easier to manage support with well-defined releases
<cjwatson> I hear more complaints about Firefox changing its UI du jour than just about any other software change
<kyleN> observation: the six month release schedule provides key milestones (String Freeze) that enable the translation community to organize their work
<cjwatson> So I have never bought the idea of an OS/application divide
<slangasek> yes, like firefox deciding to embed its pdf viewing
<jdreed> Here at MIT, we did annual releases of our Ubuntu derivative on the .04 release.  We couldn't stick with LTSes because faculty and students wanted new things every year.  But at the same time, we cannot possibly support rolling release in a public environment because my users will freak out when the UI changes (it's taken us a _year_ to get people used to Unity from)
<slangasek> :)
<tumbleweed> but not the new bugs... :/
<timrc> Easier to train support people on an OS that is relatively static (or only getting security updates)
<smoser_> ok. so i'll admit i was wrong.  both techy-geeks *and* real users hate updates.
<smoser_> so lets not suggest to anyone that devleopment release is good for them.
<smoser_> thats just absurd.
<danjared> things like the cloud archive are a better solution than non-LTS releases for servers
<rbasak> You don't have a choice of not installing updates, since you have to for security updates.
<dmj_nova> Sticking with LTS *for development* means that when the next LTS comes around you've got months of work to fix things based on the massive changes
<balloons> rickspencer3,you made a new meme
<mfisch> sounds like we have similar wives
<smoser_> rickspencer3: +1. your wife is a non-geek.
<YoBoY> rickspencer3, and she's right not to change if she feels confortable with her mac :)
<smoser_> i have one of those too
<rbasak> So what do security teams base their updates on?
<danjared> (instead of a constant upgrade to non-LTS releases)
<jdstrand> people *need* to install their updates (the security updates). that is probably the single most important thing people can do security wise
<timrc> smoser_, I'm a geek and hate change :)
<pitti_uds_> mfisch: who hasn't :)
<mfisch> moved buttons seem to really upset wives
<pmk1c> rickspencer3: completely right. many people don't like updates on their system
<dmj_nova> While not *everyone* will be comfortable with non-LTS among our customers,
<dobey> dmj_nova: yes. like i said, as a developer you have to make a decision, and compromise
<ben-linuxfan> change is never a issue for me
<xnox> My sister was using Oneiric when quantal was about out the door, and she was happy.
<pitti_uds_> jdstrand: yeah, but they don't change behaviour (except for firefox)
<mainerror> Good point, with a rolling release, if you make sure not to introduce too much of a big change at once people are likelier to adapt without noticing. I think.
<pitti_uds_> jdstrand: ideally, there should be zero visible change after installing security updates
<dmj_nova> The interim releass make it viable for some of our users to track our development more closely
<slangasek> jdreed: I understand you wouldn't want to support a rolling release; but if you just had to do a release every 2 years instead of 1 year because there was no 13.04 (15.04) to base on, what would be the consequences for your use case?
<pitti_uds_> which is distinctly not the case for RR or dist-upgrades
<jdstrand> pitti_uds_: I was referring to a comment in the video stream where people have a choice
<cjwatson> Our innovations are the things users curse at when they upgrade
<dmj_nova> This feedback loop is *very* important
<smoser_> so by all means LTS is desireable. thats clear.  from what i'm hearing here is that there is very little value in development release.  no one (even many of you here in this channel) is actually going to use it!
<pitti_uds_> jdstrand: ah, yes; I interpreted this as dist-upgrading every 6 months
<xnox> I guess the point is that on the day one ships we want the newest software. But how to support security and bugfixes wise is an interesting question.
<slangasek> jdreed: I understand that users will want newer things every year, but maybe they don't actually need them?
<jdstrand> pitti_uds_: well, of course I agree in principle. the firefox issue is contentious and we don't have to rehash it here. I think we are doing the right thing still, but admit there are problems
<mdeslaur> but out lack of a new libreoffice version that _finally_ unbreaks the documents they want to read is _also_ the things users curse at
<txwikinger-uds> there are already eevry day updates in the software manager today
<theDoctor> I've got my non-techy parents in Indiana running the latest LTS. It would be awesome for me not to have to make a special trip in just to upgrade the release when the time comes. Rolling release would be great for us
<jdreed> slangasek: Then I have some faculty clamoring for a newer version of $foo, because it doesn't support $bar.
<smoser_> can someone identify a class of users who we think is going to use a monthly release?
<Limurx> ^this
<pitti_uds_> pgraner: or more importantly, why at all? :-) (seriously, there hasn't been a satisfying answer yet)
<timrc> smoser_, Canonical QA
<jdreed> We have no problem pushing back on people who want the latest and greatest "just because", but with evolving products, we get people who seriously need new versions
<tumbleweed> smoser_: enthusiasts?
<timrc> ;)
<rbasak> Monthlies to provide sync points for people who want less frequent updates? Perhaps optionally to base security updates on, perhaps not?
<mitya57|uds> -1 for updating monthly
<mpt> My concern with monthly snapshots has three parts:
<mpt> 1. I haven't seen a compelling use case for it to exist, other than "cool for enthusiasts".
<pitti_uds_> that combines the hassle of upgrading with the cost of doing releases
<mpt> 2. There are high development costs in creating and maintaining monthly snapshots, and user base fragmentation costs in advertising their existence.
<smoser_> rbasak: do you know anyone that fits into that class ? (other than Canonical QA)?
<pitti_uds_> and makes both worse
<rrnwexec> "monthly" is just a label. it will allow people to quickly describe to others what they are using.
<mpt> 3. If there are credible use cases, it is possible (depending on the use case) that we might be able to address them with the updates UI instead.
<barry> "normal" users never upgrade (or even update) because they're much more risk adverse.  they're afraid something they love and or depend on will break, which outweighs getting something new that will be marginally cooler
<dobey> indeed. monthly "supported" release makes no sense to me
<mitya57|uds> we can't be sure there are no critical bugs in monthly snapshots
<jdstrand> rbasak: the current thinking is that if there is a monthly snapshot, high priority updates will be pushed to it. others people will get in the next monthly
<jtaylor> do transitions freeze on the monthly date? what if one crosses the border?
<dmj_nova> Why not reduce the support timeframe for the 6-monthly releases?
<mitya57|uds> in fact, we even have critical bugs in stable updates (in chromium, for example)
<smoser_> i really think those people will very quickly decide "this sucks, too many updates" or "this is too slow". and move to LTS or rolling very quickly.
<mathor> if the user is averse to change, why wouldn't the LTS be sufficient?
<txwikinger-uds> if you want user to decide, you need to have parallel versions of packages available for selection
<rrnwexec> as a user looking for support, i need to be able to tell system76 what i am using.
<utlemming> I'm not adverse to change, I want my computer to work. If updating requires rebooting and/or critical path breakages.
<xnox> jtaylor: no freezes.
<utlemming> then I am not interested
<pitti_uds_> rickspencer3: that's fine -- monthly planning cadence doesn't need to imply monthly releases
<rrnwexec> that needs a label, even if arbitrary
<theDoctor> would a monthly release schedule even give developers enough time to change/improve anything?
<slangasek> dmj_nova: why would you not have that same feedback loop from users of a rolling release?
<smoser_> no one "outside the project" will use montly releases.
<YoBoY> question : for an install, do we start with a LTS for everyone (like starting with a 12.04.2 and upgrade to have the rolling release up to date on the november 2013 for example) ? or do we have daily/monthly images ?
<rbasak> smoser_: say for example a development team who work on PHP but develop against 5.4. LTS only has 5.3. Then they can all install the same monthly and know they're developing against the same thing.
<jdreed> +1 rrnwexec
<snwh> surely if there were monthly releases people could still grab one every six months if they wanted to
<dmj_nova> slangasek: We couldn't get our users on a rolling release
<xnox> theDoctor: python 3.2 -> 3.3 got switched in 12 days.
<czajkowski> surely you're just creating a label for the sake of it then
<Limurx> Custom update cycles are best suggestion ever
<dmj_nova> not for any extended testing
<xnox> theDoctor: so yes.
<rbasak> smoser_: and same deal with deployment
 * txwikinger-uds feels like being back at LFS
<mpt> (The mailing list summary doesn't fairly cover monthly snapshots yet, because I haven't got to that part of the thread)
<rbasak> (and testing and CI)
<timrc> People will probably select a monthly snapshot based on what it introduces
<mitya57> xnox: but people still keep discovering bugs / incompatibilities
<smoser_> rbasak: i dont know. i tihnk even then they'll just be annoyed at the speed of change.
<dobey> if there's no extra testing, freezing, etcâ¦ then there's nothing special about calling a release on the last day of the month, the monthly release. there's no guarantee for the user, and if we have to do all that work, it's extra work for us, that doesn't really gain us anything
<theDoctor> yeah but can't we get small updates like that through update manager? is it really worth a monthly release schedule?
<jtaylor> xnox: without a freeze whats the significant of the monthly?
<dmj_nova> slangasek: Would you use a rolling release on a production workstation?
<jdreed> rrnwexec: This is the question I asked last week.  How can a user tell me (or how can I tell a vendor) what I'm running on my system, short of "dpkg-query -W"
<timrc> So though they may not update monthly, they can find a snapshot that includes whatever they want
<slangasek> jtaylor: transitions are staged in -proposed and aren't copied over to another pocket until they're complete
<rbasak> smoser_: they will be, but that's an unavoidable cost of not using the LTS
<dmj_nova> We need at least some users who are
<smoser_> rbasak: why would those people not use the lts. and put their new php package on it.
<rrnwexec> another way to identify a "build" is to checksum all the packages... and that would result in a LOT of versions ;)
<rbasak> smoser_: sorry, I mean web developers developing PHP, not developing PHP itself
<pmk1c> thing is: everyone updates as he wants. I know a lot of people don't caring about updates even when they pop up right in their faces
<jjed_> Simply put: insulation for RR SNAFUs
<smoser_> rbasak: so i assert they'll use LTS.
<dmj_nova> with 6 monthly releases many are comfortable with that
<slangasek> dmj_nova: no, I've said I wouldn't.  But I don't have any idea who your users are, sorry, I find you've been a bit vague about what exactly it is you're developing
<olafura> The security repo would solve that
<utlemming> smoser_: what about per package rolling release?
<rbasak> Perhaps they just need a backport.
<mpt> "You are safer on monthly snapshot than on the rolling release" is true only if we have tested monthly-to-monthly upgrades.
<slangasek> my expectation is that there /will be/ users of a rolling release
<jtaylor> slangasek: so we target all rebuilds to proposed, but what stops them from going to out?
<utlemming> smoser_: where you flag the packages that you want to update on rolling release basis?
<dmj_nova> slangasek: We're developing a video editor for professional artists
<slangasek> dmj_nova: ah, nova == novacut? :)
<utlemming> smoser_: if you want the latest greatest PHP, then you can have it
<slangasek> that makes more sense
<dmj_nova> slangasek: yep
<mathor> My question is, if I choose a monthly snapshot then decide I'd like to be on the cutting ege daily, do I have to then get a whole new iso?
<tumbleweed> mpt: yeah
<smoser> utlemming, well, where I carry my delta on my own (quite possibly through juju or some other mechanism)
<ogra_> if we have to do monthly testing at all, whats the point of rolling ?
<xnox> Everyone knows that the daily after the milestone has always been so much better!
<philipballew> mathor, probably just change tour sources?
<rickspencer3> mathor, I think you would just change the frequencing that you update
<balloons> xnox, yes +1
<philipballew> *your
<fisch246> jonobacon: what if Ubuntu went the route of creating a rolling release VERSION of Ubuntu? Ubuntu-rolling?
<slangasek> jtaylor: that question is backwards; *all* updates are only allowed out if they don't break the consistency of the release pocket
<balloons> I agree.. if we're monthly releasing/testing, we're not rolling
<utlemming> smoser: that is a server perspective, but it could apply to the desktop too. Like always tracking the latest unity. But then again we do some of that with PPA's already
<xnox> cjwatson: I would like to phase all package updates in rolling, such that one gets a dial that one can set to stable.
<dmj_nova> If we have to stick with LTS for both development and end users, we'll be having problems every time the LTS cycle comes around
<achiang> dmj_nova: honestly, i think every app developer on every platform has this issue, they have a branch for $CURRENTOS and a branch for $NEXTOS
<smoser> utlemming, right. some stack that you're interested in. you may want to track that.
<smoser> anything else is noise and annoyance.
<dobey> achiang: exactly
<utlemming> smoser: I think that sort of option would be compelling...and something I would use.
<dmj_nova> If we develop on rolling, then we have to either spend enormous amounts of work on backports (some of which may break other things on the LTS) or just not get any feedback
<rrnwexec> i think we need to think in terms of "labeling" rather than "releasing". if we have daily quality, then we can label at any interval. it's just a label.
<Tribaal> rrnwexec: +1, similar to tags in DVCS
<jdreed> +1 rrnwexec
<balloons> rrnwexec, I would prefer we simply don't label the "rolling" at all.. It sort of confuses the issue
<tumbleweed> dmj_nova: we *do* develop on rolling
<fisch246> or... with the update manager, selecting lts, non-lts, or rolling might be an option
<cjwatson> xnox: Some, certainly
<jdstrand> cjwatson: I'm confident we can do just that
<jtaylor> what is with transitions for packages not having a proper versioning scheme, like python?
<slangasek> dmj_nova: well, I guess I don't see how this is different from development of any other software where you need to support a range of versions on different platforms
<smoser> rickspencer3, its reality.
<smoser> your wife will not use it.
<stgraber> cjwatson: would it make sense to start using the priority field for the cadence bypass?
<theDoctor> @smoser - True story
<mainerror> That's just not true. We use non-LTS in production as well.
<tumbleweed> jtaylor: ?
<gQuigs> very important point rick spencer
<Riddell> PROPOSAL: don't make any changes for raring, it's very short notice considering we all agreed to doing raring and there's obviously issues still to be worked out
<mitya57> rickspencer3: "people outside the project will use the LTS" == "rolling is for developers"?
<xnox> cjwatson: the beauty of sticking phased-updates logic into update-manager is that if told, apt will resolve additional dependencies needed to pull in a particular phased update.
<dmj_nova> slangasek: I'm saying that by not having the interim release, all our users are forced to the LTS
<mpt> rickspencer3, those other frequent-landing software organizations are usually making apps, not platforms. (Facebook may be an exception.)
<slangasek> dmj_nova: if 12.04 and 12.10 have different versions of gstreamer, and you intend to support both, your software needs to be written in a way that works with both... rather than backporting gstreamer
<jsjgruber-uds> Riddell: +1
<dmj_nova> which makes it difficult to support both the LTS and the rolling with current development
<txwikinger-uds> Riddell: +1
<pitti_uds_> it's not about quality (although we aren't anywhere near LTS quality with raring yet), but about what you want to use
<timrc> How many other OSes do rolling releases?
<ogra_> rickspencer3, if we really do it like that, whats the point in monthly image or monthly updates  ? lets drop that stuff if every daily is installable there is no need for montly stuff
<achiang> rickspencer3: the problem here is that our apps are too tightly tied to the platform. no other OS does that
<gQuigs> maybe montly upgrades need to be automatic?
<me4oslav> timrc: arch.
<dmj_nova> slangasek: that's a huge amount of work, and would entail huge differences in functionality
<rbasak> cjwatson: +1
<achiang> (the release cadence, that is, not the APIs)
<cjwatson> xnox: it already has phased-updates logic :)
<balloons> ogra_, exactly.. make it work daily, only care about keeping everything working day to day
<mitya57> +1 to Riddel and to ogra_
<xnox> cjwatson: naughty ;-)
<ogra_> balloons, ++
<olafura> rickspencer3 if we are going to have a rapid update them we need to allocate disc space that can be used if the disc is full. If we try to update when it's almost full then it's a mess.
<rbasak> I used to do that with Ubuntu. I used 6-monthly releases, but not every one.
<dobey> dmj_nova: it's not terribly hard to support both; at least in Python. it's much harder in other languages.
<txwikinger-uds> Rolling releases are very agile.. but we also need the other site.. the automated testing for that
<cjwatson> stgraber: Maybe - I haven't thought much about the priority suggestion yet
<dmj_nova> gstreamer is lucky in that it doesn't have issues with installing both side by side
<gQuigs> maybe cut support for raring to 9 months?
<philipballew> Would making changes "destroy potential quality"?
<xnox> CarlRichell: rickspencer3: what if 12.04.3 is better than 12.10?
<dmj_nova> dobey: there's all sorts of gstreamer issues with python
<timrc> rickspencer3, you should take the people using Ubuntu into consideration...
<kamal> cjwatson++
<timrc> especially the people paying money for support and what not
<isantop> xnox: It still only has features that are a year old.
<dobey> dmj_nova: gir vs. static bindings problems/
<philipballew> We have spent three months on this thing. It seems harmful to all the sudden change now?
<dobey> ?
<jjed_> How about transitioning raring directly into the rolling release? ("We will support this until the first RR snapshot happens")
<dmj_nova> dobey: yep
<dmj_nova> and python2 vs 3
<gQuigs> or don't release Ubuntu Unity for 13.04?
<xnox> isantop: it has 12.10 kernel and X stack. So in 12.04.3 we can push out latest unity.
<dmj_nova> we were actually depending on having *both* python 2 and 3 because of gstreamer 0.10
<dobey> dmj_nova: 2 vs 3 should be less of an issue. it's only an issue if you're using static bindings
<dshimer> It's just such short notice.  Problems with waiting are well taken, but seems necessary.
<BigWhale> 13.04 should be released as scheduled, but it doesn't have to be supported
<Sweetshark> Isnt "there isnt a 13.04 - surprise!" merely a psychological problem?
<sebsebseb> BigWhale: nope should be supportd 18 months at least 13.04
<skellat> Sweetshark: Yes, a big one.
<rrnwexec> how about reducing the support duration for 13.04? 6 months?
<mitya57> PROPOSAL: if we won't release raring, can we release 12.10.1 / 12.10.2 / ... to have something to point people to until 14.04 is released
<cjwatson> xnox: mvo was the naughty one
<barry> dmj_nova: :(
<cjwatson> he did it ages ago
<xnox> cjwatson: hehe.
<mpt> Would allowing and testing 12.10-to-14 upgrades be noticably harder than 13.04-to-14 upgrades?
<pitti_uds_> mitya57: we'd have to extend 12.10's life by half a year, which seems a lot cheaper than supporing 13.04 as a whole
<dobey> dmj_nova: well, if it's any consolation, we have the same issue in U1, because of apport
<xnox> ev: apt has phased updates support thanks to mvo tinkerings ^ =)
<dmj_nova> Shortening the maintenance period could be a good alternative to rolling
<tumbleweed> mitya57: what would tha tmean? that sounds like an entirely new thing
<xnox> ev: grep cjwatson/xnox.
<Sweetshark> You get a 13.04 that gets constant updates and that you can get a week earlier even without feeling guilty.
<balloons> you could release 13.04 now if you wish.. upgrade to raring (which is continues to roll as the rolling release)
<dobey> dmj_nova: also, iirc, novacut is targeting python 3.3, which isn't on precise anyway, so trying to support precise seems like a problem regardless
<balloons> doesn't that meet your need to release something?
<gQuigs> why not just support it for less time?
<dmj_nova> perhaps a 7-12 month period for interim releases going forward
<noahl> rickspencer3: just a thought, but if the main issue is the number of releases you have to support at once, then actually the release frequency doesn't affect that
<dmj_nova> dobey: yes, precise was becoming a problem for us
<skellat> cjwatson: If you're going that close to canceling it without finishing it, just finish it off
<kyleN> which would means that RR cannot equal "rolling release".  a small price :)
<mitya57> tumbleweed: currently the download page suggests 12.10, if it won't change until 14.04, people who have just installed Ubuntu will either use old and unsecure package versions
<ChrisLAS> How will users be expected to keep that straight?
<noahl> the thing that affects that is (release support time / release frequency)
<cjwatson> skellat: I'm not sure I agree
<mitya57> or have to install 1GB of updates
<balloons> transition period is simple enough.. if you running 12.10 you move to 13.04/rolling.. if your on lts you stay on lts
<Limurx> Security and stability updates could be "forced"/suggested daily and other updates could be hold back for a custom amount of time (default 1 month). So there are no snapshot to snapshot updates, that have the drawbacks of support, and no annoying bunch of updates each week
<dmj_nova> without raring, we would have zero releases we could recommend to our users
<balloons> it gets weird if you release 2 "stable" versions
<slangasek> balloons: 12.10 itself still has 18mo support
<noahl> so maybe you should fix the number of releases you want to support at once, and then play with frequency given that
<mpt> Ah, pitti pointed out the error in my equation :-)
<dobey> dmj_nova: but i don't think that's related to ubuntu having interim releases or not. it's more that it's just a bad time for writing something large like that in python 3, due to the transition to python 3.
<ogra_> cjwatson, rickspencer3, we offer opt-in  milestone freezes for flavours, cant we offer an opt in release for then as well ?
<pmk1c> dmj_nova: why can't you recommend 12.04.2?
<balloons> slangasek, sure.. but we don't want to release 13.04 with the same support levels
<BigWhale> sebsebseb, supported as releases are supported now, it would start rolling
<czajkowski> mpt: you made an error :o are you sure ;)
<ogra_> *them
<cjwatson> xnox: No, apt does not have phased updates support; update-manager does
<cjwatson> ev: ^-
<mitya57> yes, we can recommend 12.04.2 in the download page
<slangasek> balloons: I mean that users on 12.10 aren't required to upgrade to the RR
<xnox> cjwatson: ok. so i had it right.
<dobey> pmk1c: the problems are the same. it's not a kernel issue. it's major API changes that aren't in 12.04.2
<mpt> The number of releases we're providing updates for is not a reason to introduce a rolling release. It is a reason to drop non-LTSes. (That's why I separated the two in the thread summary)
<balloons> slangasek, ohh certainly.. so no one who didn't want to change/move would have to
<dmj_nova> pmk1c does 12.04.2 have up-to-date gstreamer, python, webkit-gtk, udisks2, etc?
<Riddell> ogra_: there's a differece between a milestone release and a final release, the archive gets frozen
<noahl> rickspencer3: that makes sense. thanks
<dobey> dmj_nova: no, 12.04.2 is not 13.04 :)
<dmj_nova> and if it does, how is it different from quantal or raring
<dmj_nova> so 12.04.2 does nothing for us that 12.04 does
<balloons> mpt, that's actually a nice distinction, but a bit lost here
<txwikinger-uds> that is just the defaults
<jdreed> _you_ don't uninstall software, but apt might decide to.
<cjwatson> Only if there's a conflict
<tumbleweed> it wouldn't have a reason to, though
<mainerror> CarlRichell: I guess that's where the new UDS model will kick in.
<jdreed> autoremove?
<pitti_uds_> rickspencer3: the woudl have dobey's new player installed
<pitti_uds_> pitti_uds_: but indeed also keep RB
<mpt> Each of (a) dropping non-LTSes, (b) rolling release, and (c) monthly snapshots, could be done without either of the other two.
<dmj_nova> Also, say there are new features in rolling, we wouldn't be able to support them or benefit from them until potentially 2 years later
<cjwatson> If you choose to use autoremove, then you need to review what it removes, certainly
<txwikinger-uds> underlying dependencies might cause uninstall by apt
<slangasek> dmj_nova: well, I think that goes right back to the point that I (and many others) would never deploy anything other than an LTS in production anyway, so the fact that the LTS is hard for you to support because it uses older technologies is orthogonal to the question of 6-mo. releases vs. rolling releases
<mitya57> dobey's new player?
<YoBoY> I think we just need a smaller ubuntu-desktop-core without the default apps
<dobey> dobey is not writing a new player
<cjwatson> mpt: To me, rolling release is effectively synonymous with dropping non-LTS
<cjwatson> Perhaps with better testing
<mpt> cjwatson, Microsoft Windows is a counterexample.
<ogra_> ++
<cjwatson> mpt: ?
<xnox> stgraber: i thought it was a plant and a mountain in a distance, but it's a folded desk! you just lost the backdrop award.
<cjwatson> I mean "rolling release as we have discussed in the context of Ubuntu up to now"
<mpt> cjwatson, of roughly-two-yearly releases without a rolling release.
<cjwatson> Not some other hypothetical thing
<dmj_nova> slangasek: There are many contexts here, and it's not that we want *every* user on the current ubuntu or the current Novacut
<balloons> xnox, lololol
<slangasek> dmj_nova: but for something like novacut, "in production" might mean something else - I might have a dedicated machine/VM for it, running whatever OS is required... whether that's a rolling release, an LTS, whatever
<dmj_nova> but with rolling, we couldn't recommend *any* of our users to use rolling
<cjwatson> mpt: OK, sure, we could drop interim releases and also take all our intermediate development private.  I don't consider that worth discussing.
<dobey> dmj_nova: at some point you just have to stop supporting the older releases
<Michaeljwjr> Why not have a separate check box for optional software installation to not bloat systems?
<Limurx> If I uninstall the default software, it will be reinstalled with every update????
<slangasek> dmj_nova: well, then that simplifies your support matrix too :)
<balloons> dmj_nova, so you don't want LTS or rolling?
<dobey> dmj_nova: but that's a decision the developer has to make, not that Ubuntu makes for them
<dmj_nova> dobey: we do not support precise right now
<FunnyLookinHat_> There's still an issue of stability with the rolling release - is the current daily essentially what we're calling "good enough" to be called a rolling release?  Speaking from experience - it still frequently crashes, etc.
<dmj_nova> supporting it for 2 years would not work
<mainerror> jono_: You really want to call it crap? I mean a month before it was state of the art and the Ubuntu community said it was good. :)
<mpt> cjwatson, that's a false dichotomy. There's a difference between the current development release model, and the rolling release model.
<dmj_nova> I'm pointing out issues that we are having and will have if the rolling release is chosen
<Riddell> One idea for Kubuntu to stay aligned to KDE releases is to do Kubuntu releases on LTS+PPA, would this be possible? (currently it goes against tech board policy)
<cjwatson> mpt: Name it
<slangasek> 14.06! victorp__ is slipping our release schedule
<mpt> And it isn't the presence or absence of LTSes.
<victorp__> cjwatson: can you point me to the session?
<Laney> xnox: hahaha, I thought it was a bridge
<Laney> with some mist
<Laney> and a tree in the distance
<jono_> mainerror, lol
<xnox> stgraber: so deceptive!
<victorp__> slangasek: didnt say it was the first one ;)
<dmj_nova> Because Ubuntu needs to consider what its release pattern means for the ecosystem
<dobey> dmj_nova: the issues you're pointing out will exist regardless of whether there is an interim release every 6 months, or not
<cjwatson> victorp__: Not off the top of my head, sorry, I was just fairly sure it was on the appdev track somewhere
<mathor> I don't know, FunnyLookingHat, I've been running 13.04 for two months and haven't had any bug at all?
<dmj_nova> Ubuntu is not valuable becuase it's an OS for people to use Unity on
<FunnyLookinHat_> mathor, but it's completely relative to hardware, drivers, specific installed applications, etc.
<isantop> It exacerbates the existing problem.
<mathor> So in that case, there's no reason for me to sit on 12.10 for 6 months when things are running smoothly on 13.04
<dmj_nova> Ubuntu is valuable because it is a great platform for application development
<mpt> cjwatson, it's the degree to which we are able to recommend it to people who aren't Ubuntu developers. I think it was Colin Watson who said, "If it's for developers only then I would account that a failure".
<FunnyLookinHat_> mathor, the problem is exactly that - You, as a dev, could be not having any issues, but the rest of us could have apport throwing errors left and right
<dmj_nova> and its these applications that make Ubuntu valuable to users
<FunnyLookinHat_> And because we're regular "users" we're not constantly filing bugs ( as we should be ) but instead are just getting frustrated
<cjwatson> mpt: That's a difference of intent, but there is no difference I'm aware of in the underlying model
<balloons> cjwatson, mpt is correct. We could simply switch to only releasing LTS's, without rolling.. We are effectively doing both here. also, we could drop lts's and only do rolling.. they aren't tied persay
<dmj_nova> If Ubuntu hurts this development ecosystem, that hurts the platform
<dobey> dmj_nova: but is novacut going to migrate to Qt/Qml now, because Ubuntu has decided to do so?
<cjwatson> balloons: I disagree that there is a real difference; I also fail to see how this is more than an academic discussion anyway :)
<victorp__> cjwatson: I will keep my eyes peeled ;)
<balloons> cjwatson, I agree it's academic.. not really a discussion point here
<dmj_nova> dobey: We may, particularly qtwebkit but that's another matter
<dmj_nova> and doesn't impact this disccusion
<cjwatson> mpt: To clarify, I consider it a failure if our current development release is for developers only
<mpt> cjwatson, well it has consequences in the degree to which PPAs are used, or a new -experimental pocket, or both. But I'm here mainly because I'm interested in the things that aren't the underlying model, e.g. how we talk about the release to people who aren't developers.
<cjwatson> mpt: So your attempt to use my words to prove your point fails, I'm afraid :)
<kyleN> the point about fragmentation of targets of development also applies to translation. they may end up focusing on LTS leaving intermediate releases irregularly translated.
<balloons> LTS
<mitya57> GNOME guys were also going to request changing that policy, IIRC
<Riddell> Laney: we do have a PPA for 12.04 now and it's not much work
<cjwatson> (Specifically, I've been working for well over a year to make sure that our development releases are usable by reasonably technical users who are not Ubuntu developers)
<timrc> LTS should just be truncated to S (for supported vs not-supported)
<slangasek> stgraber: is this actually a TB policy, or does the issue come back to Canonical trademark policy?  I'm not clear on this
<mathor> I just do not understand why a user cannot use an LTS in the case that they need their system to have complete stability.
<dobey> rickspencer3: perhaps it's worth discussing providing policy to allow for exceptions for the release+PPA situation
<Laney> mmm
<xnox> cjwatson: translations, documentations, making images fit the size, the "6-monthly" tasks.
<Laney> It works if KDE have a strong policy about bumping deps
<stgraber> slangasek: it's some mix of both IIRC, it's a TB document defining what flavours can do, what remix can do, ... and the actual use of the name is covered by the trademark policy
<FunnyLookinHat_> mathor, because, at this point, they'd have 2-year-old applications ( for the most part ) and any ISVs might be saying "you're on the old version, too bad" to their support requests
<kyleN> translations requires string freeze, would that exist in rolling elease?
<Riddell> Laney: well we either backport the dep or drop it in that case
<mathor> A rolling release is for those who would like to be on the cutting edge. Those people will not have the most stable release, but it will be usable
<cjwatson> xnox: None of those differ between "just drop the non-LTS releases and otherwise keep our current development model" and "rolling release" - again, I consider them synonymous
<stgraber> slangasek: so last time the TB got a proposal for a policy change, we reviewed it, voted on it, then someone had an action to get the trademark policy updated accordingly
<dmj_nova> In that case, why not drop support for old interim releases much shorter?
<kyleN> :)
<mathor> My problem with your argument. Is that 12.10 gave me apport errors out of the box on release day
<balloons> kyleN, i think string freezes would be closer to a package level than system level
<stgraber> slangasek: (I believe that was for the Ubuntu business stuff)
<mathor> If anything 13.04 was more stable than 12.10
<ogra_> slangasek, for the panda images (that shipped a PPA installer) i was asked to either call them remix or drop the PPA installer by the TB
<mathor> What is the point of releasing software if it isn't completely stable
<mainerror> mathor, +
<FunnyLookinHat_> mathor, That's because they forgot to turn off apport ;)
<dobey> dmj_nova: next month there will only be 1 interim release in play, assuming 13.04 is not released
<mitya57> dholbach: is that you editing the notes? :)
<dmj_nova> dobey: And if the window were shortened, then we'd never have more than 2
<cjwatson> It seems clear that the TB would have to update some of those kinds of policies to keep up with events
<cjwatson> One way or another
<didrocks> rickspencer3: +1 :)
<ogra_> yep
<philipballew> thats why we have proposed repos
<txwikinger-uds> Good luck rickspencer3
<kyleN> maybe we need unittest coverage to report that strings have changed
<Riddell> QUESTION: what do we do with beta and RC releases from upstream?
<kees> what happens to release stability when we start auto-import from debian when debian unfreezes?
<stgraber> ogra_: that's indeed how things currently work, but I'm happy to rediscuss this and change policies if that's what we need for the LTS+rolling scenario
<mpt> e.g. a KDE beta?
<BigWhale> If you're adding new code (or strings) in the release you _have_ to make sure it works.
<xnox> CarlRichell: what is interesting to you? is python3.2 vs python3.3 interesting? or only new unity is interesting (leaf packages)?
<slangasek> in practice, I don't think we have a very good workflow today for getting translations in /before/ the upload
<pmk1c> dmj_nova: I don't think you can support interim releases for only a half year. that would mean forcing the update. But I think 1 year should be enough support
<mathor> I jus think if you release 12.10 or 13.04 on a computer, you will not ge the stability of 12.04, and those cases LTS works best for users, and I would think System76, Dell, HP, etc should only ship 12.04 in that particular case
<dmj_nova> xnox: python 3.3 is very interesting to Novacut
<cjwatson> kees: I know ScottK has raised concerns about that.  I'm not sure I think it's as big an issue as all that, but neither of us really have data
<mdeslaur> kees: it breaks, what else? :P
<pitti_uds_> rickspencer3: we'll have to have some kind of staging areas for transitions, betas, etc. anyway
<xnox> dmj_nova: available or default?
<dmj_nova> pmk1c: why not support it for 1 year
<slangasek> ogra_: heh, calling it a remix if it's using a ppa is explicitly contrary to the trademark policy anyway
<cjwatson> However, from past experience dealing with stabilising after auto-syncs, I genuinely think that most of those should have been addressed by proposed-migration
<ogra_> stgraber, ++, sounds like a valid solution for flavours
<Riddell> mpt: yes
<dmj_nova> so the user must update to 13.04 sometime before 13.10?
<Sweetshark> Riddell, fwiw: My plan for LibreOffice is to release ~alpha/~beta to ppa and only bring it to raring on .0/.1/.2 depending on quality/feedback.
<pmk1c> dmj_nova: yeah as I said: one year of support should be considered
<ogra_> slangasek, it was only an installer icon on the desktop that enables the PPA , not even a PPA in teh build :)
<dmj_nova> xnox: we don't care if there are several pythons but we need 3.3
<slangasek> ogra_: heh, ok
<xnox> dmj_nova: we are planning to extend 12.10 support length to get overlap with 14.04.
<xnox> dmj_nova: point taken.
<dmj_nova> xnox: We're already dropping 12.10
<slangasek> xnox: that's been proposed, FWIW I wouldn't say that it's an agreed plan quite yet
<FunnyLookinHat_> It seems like we're going in this direction with a lot of unknowns - and if it hits the fan, we haven't necessarily planned for an "eject" button of sorts .
<didrocks> Sweetshark: also, you still have ppas to evaluate how good/bad the LibreOffice release is beforehand
<tumbleweed> xnox: that wouldn't be necessary with a 13.04 release, though
<kees> I just worry that the "rolling release" topic comes up every time debian is frozen. as soon as debian opens the flood gates, it's going to be a lot of constant pain, I worry. I hope it's okay. I'd prefer a rolling release.
<timrc> how are rolling releases going to affect PPA building? Will I have a choice to build a package against: daily, monthly, or LTS?
<timrc> cjwatson, ^
<kees> I used debian unstable day-to-day before ubuntu existed.
<jdstrand> slangasek: didn't you have some numbers on this topic (Debian unfreezing and its affect on the monthly release)?
<dmj_nova> (though only because at the moment we *don't* want users playing with a couple dangerous changes until 13.04)
<xnox> timrc: you can build against LTS or rolling. No other options.
<cjwatson> timrc: That depends.  Don't know yet.
<dmj_nova> (this is a rare one off situation)
<jdstrand> slangasek: maybe they weren't metrics :)
<mdeslaur> How much of main is synced directly from debian?
<cjwatson> xnox: It's not decided yet.  Other discussions this week affect that.
<mathor> Again, FunnyLookingHat.  Just keep users on the LTS
<cjwatson> mdeslaur: chart at the bottom of merges.ubuntu.com/main.html
<pitti_uds_> kees: yeah, I'd also prefer a model where we sync from "unstable minus 5 days" and check for new Debian RC bugs
<xnox> mdeslaur: check merges.ubuntu.com it has graphs =)
<balloons> With the idea of the rolling release, I don't feel like a little breakage (should it happen) is unacceptable
<slangasek> jdstrand: not on that specifically... I had numbers on how many packages on the desktop CD are unmodified from Debian
<pitti_uds_> kees: as a kind of middle ground between unstable and testing
<mdeslaur> oh duh, yes, the graphs :P
<ogra_> Riddell, Do IT !
<dmj_nova> Generally, we like to support at least the development and the current interrim
<ogra_> err
<cjwatson> (Bear in mind most of "local" is language packs)
<ogra_> sorry Riddell
<dobey> rickspencer3: just drop 13.04 release and do it :)
<ogra_> rickspencer3, Do IT !
<dmj_nova> we don't care about interrim releases from over a year ago in any way
<ogra_> rickspencer3, but forget that monthly insanity ;)
<Laney> Can we come to a conclusion on raring?
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-1303/community-1/ - http://ubottu.com/uds-logs/%23ubuntu-uds-community-1.log
<mathor> only ship LTS
<kees> the reason I switched to Ubuntu originally was because of the release cycle. if the goal is just "switch to LTS releases", that's different.
<dobey> Laney: indeed. "is there a feature freeze on thursday?"
<smartboyhw> So what's the discussion result?
<isantop> cjwatson: But we can't ship a two year old release.
<Laney> fnar bot
<achiang> the plan B should be for system76 to ship LTS, not a rolling release
<rickspencer3> ogra_, I dunno, I think the monthly cadence is good for users who like Interim releases today
<cjwatson> isantop: As it stands now
<ogra_> rickspencer3, they should ues the well working daily
<Sweetshark> didrocks: right, this is why I want a armhf builder for the LibreOffice ppa. to have at least one build see some enduser testing before I hit raring.
<vila> cjwatson: why not a simple dual-boot LTS + RR
<tumbleweed> Laney: please :/
<dholbach> 4 minutes left until plenaries!
<cjwatson> vila: That's not realistic for ordinary users
<didrocks> Sweetshark: need help with that? I know who to bribe :)
<mathor> ubuntu needs to find a solution to continue updating software in LTS
<Laney> bah
<Laney> seems not
<Sweetshark> didrocks: nah, seems mostly ok now.
<theDoctor> Good session guys!
<txwikinger-uds> cjwatson: rolling releases with snapsshots?
<sebsebseb> dholbach: intersting convo
<didrocks> Sweetshark: then, you can have pocket copy :)
<dobey> mathor: this is part of that solution
 * ogra_ gets a break because rickspencer3 said so (my loung cancer is all your fault !)
<quesh> didrocks: you rocks
<Riddell> Laney: that's up to the tech board n'est pas?
<kamal> rickspencer3: excellent session, thanks all
<rickspencer3> ogra_, nooooo
<vila> cjwatson: may be. But 1) may be made usable for ordinary users 2) Using RR is for devs right ?
<ogra_> hehe
<Laney> Riddell: well, the support situation is a Canonical decision
<cjwatson> txwikinger-uds: Maybe, but I think those are broken in other ways
<txwikinger-uds> thanks guys
<Limurx> *claps hands*
<quesh> bye
<cjwatson> vila: I would rather make 1) usable and sufficiently up to date that it doesn't make everyone go "oh my god it's so old"
<utlemming> rickspenscer3: can we get an updated doc on what was decided/changed?
<dmj_nova> In the case of our users, it is important not to have updates break things at unpredictable or unfortunate times
<cjwatson> Released two years ago doesn't fundamentally have to mean that it looks stale
<Riddell> utlemming: no decisions that I saw
<skellat> Riddell: Strange, that
<skellat> Riddell: I wonder if and when we'll know an outcome
<slangasek> Laney: so, did we answer any of the open questions that were in the whiteboard? :-)
<tumbleweed> cjwatson: it does mean we need to move faster with HWE, though
<cjwatson> Rick did say at the start of the session that he didn't expect any actions from this session and was mostly trying to gather feedback
<dmj_nova> So upgrading every 6 months on average isn't a problem so long as they can choose when the potentially breaking changes happen and test them on a non-production environment beforehand
<txwikinger-uds> I wonder if rolling releases only work when you have different streams
<utlemming> Riddle: that is what I thought...but people react emotionally. I would rather I react -- and people react -- to a document then what they think they saw.
<utlemming> er, Riddell: ^
<Riddell> skellat: this isn't the best forum for decisions, little notice and timezone dependent and it's up to tech board (or bits to canonical) anyway
<slangasek> cjwatson: indeed... I was hoping we would at least get a consensus wrt what to do Thursday for the FF
<dmj_nova> But updating every month, could be a big problem, especially if there isn't much choice there about the timing
<tumbleweed> that's the only reason I wanted this session...
<dmj_nova> say 3 days before a deadline and no way to roll back
<vila> slangasek: if no decision to change has been taken, nothing has changed :) 13.04 should be released ;)
<Riddell> vila++
<Laney> slangasek: Well, none of mine about what to do in the immediate future
<skellat> Riddell: Well, off to the showers for me and and I've got a couple hours until next round
<Laney> this week and for raring
<Laney> my preference is to carry on as planned and consider all this thereafter
<Riddell> Laney++
<vila> slangasek: I'm all for RR myself which is why I would rather delay it for a few months that fails by rushing (but that's just MHO)
<tumbleweed> Laney: +1
<slangasek> Laney, Riddell: yes, I think there is a consensus to carry on with the release schedule as written for now
<Laney> slangasek: I think so, but I would like to know that it will be a useful use of time
<slangasek> though I don't think that necessarily means we'll still do a 13.04 release
<slangasek> Laney: indeed, and I don't think we can answer that until e.g. the TB have weighed in
<Laney> not that we're going to review exceptions for a month and then have the doors thrown open again
<mathor_> I think there needs to be another blueprint about this topic
<mathor_> Developers are still torn on this issue, and so much time was spent arguing for a rolling release, that it was hard to even really discuss abandoning 13.04
<Laney> We started to have a discussion about this and I *think* people were receptive to keeping 13.04, but then we moved on
<X3MDroid> I think rolling release is a bad idea
<dmj_nova> Rolling is bad for developers
<dmj_nova> We already effectively have all the rolling we need thanks to daily quality
<Laney> slangasek: â - don't know if there will be an opportunity to finish it off some other time this UDS
<dmj_nova> but we can't reach end users as easily without the interrim releases
<X3MDroid> And is bad for bussines. Enterprises want stability sensation, and LTS versions are the best way to do that
 * Riddell objects to the term 'interim release' it only got created to make the idea of dropping them seem more favourable
<smartboyhw> lol
<tumbleweed> yeah
<dmj_nova> Riddell: non-lts release?
<slangasek> Laney: I suspect that may require some Canonical-internal discussions that are out of scope for UDS, as far as what resources Canonical is willing to put into carrying 13.04 forward
<vila> Riddell: how were they name before ? dev releases ?
<smartboyhw> same feeling dmj_nova
<Riddell> vila: just release
<smartboyhw> Yes call them dev releases
<Laney> slangasek: Hmm, yeah
<Laney> I at least get the feeling that it's on the table which is positive for me
<Riddell> smartboyhw: they're used by much more than devs
<smartboyhw> ph
<smartboyhw> *oh
<skellat> Much of this can come up at the Xubuntu Contingencies discussion tomorrow
<dmj_nova> Most users I know do not use the LTS
<Sweetshark> rickspencer3: Cant we 'release' 13.04 with an announcement as a rolling release? That is: announce it as being the rolling one and pitch the awesome fact that you even get quicker updates for it? Essentially its a policy change only: instead of SRUing stuff, we are trying to make every distro upload a good one -- not only the stuff we SRU back.
<dmj_nova> they do use a stable release
<vila> Riddell: mixed feelings on that, I have a few friends to which I had to say: can't help you with bug X, revert to LTS. They did so and were happy
<dmj_nova> but it's generally the regular most recent releast
<dmj_nova> Most of those would not use rolling
<vila> Sweetshark: + 1 on the idea, the wording needs to be better though
<mathor_> My university will only use LTS, and a full-scale deployment of ubuntu  on pre-installed machines, for instance, if my university or another university or an office building were to choose to purchase a computer preinstalled, this is what they'd want as well.   Just as rolling releases only contribute to enthusiasts, interim releases only contribute to enthusiasts as well.
<dmj_nova> One nice buffer with the 6-month cycle is that in most cases (and the others are arguably bad judgement) there is time to discuss and refine new big changes
<X3MDroid> Stand up users maybe, but the 2 SME's I know are using LTS with a paid support to canonical
<vila> Sweetshark: i.e. use 13.04 to experiment with RR and decide how to continue from there
<dmj_nova> so that only the devs get bombarded with controversial changes
<Sweetshark> vila: developers dont lie ;) this is why you keep them away from the mics
<dmj_nova> whereas a monthly pulse could result in upsetting changes hitting everyone before there has been an opportunity for refinement
<vila> Sweetshark: hehe, yeah, they are notoriously bad to communicate with users ;)
<dmj_nova> and good community feedback
<mathor_> the Ubuntu On Air, and what they are trying to do with that sort of addresses this issue
<mathor_> if it becomes a case where talks such as this are happening every day or once a week, there is no point for a UDS,  it leads to a rapidly-changing ecosystem
<X3MDroid> I think that the 6 month rhythm is very good for desktops
 * smartboyhw agreea
<mathor_> so if anything, the landscape has become more transparent than it was
<mathor_> So a rolling release paired with constant community feedback leads to development at a much quicker pace
<dmj_nova> Rick Spencer: Does anybody include professional users?
<dmj_nova> rickspencer3: ^^
<caryhartline> aw man I'm too late.
<rickspencer3> dmj_nova, not sure what you are referring to
<dmj_nova> rickspencer3: as in people who depend on their machine for work project who are not developers
<rickspencer3> dmj_nova, I guess I would say if a user prefers to update eveyr 6 months today ...
<rickspencer3> the rolling release should be good for them
<rickspencer3> if they prefer the LTS, they can/should stick with that
<mpt> mathor_, yes, we still have the worst aspect of UDS, i.e. "let's discuss everything all at once"
<dmj_nova> rickspencer3: One big difference is how can the user choose when the big changes happen
<dmj_nova> or would you support say the last three monthlies?
<rickspencer3> dmj_nova, as we discussed ...
<dmj_nova> which doesn't sound like it saves you much
<rickspencer3> there are 2 things
<rickspencer3> 1. Rolling release
<rickspencer3> 2. Update cadence
<rickspencer3> rolling release means that we only support LTS and the latest and greatest
<rickspencer3> I proposed that we also have a monthly update cadence, so users can choose to update monthly
<mpt> mathor_, but there's nothing to prevent the lead of any particular feature saying "that's daft, I'm going to organize a hangout on topic X, and let interested people register what times would suit them"
<rickspencer3> but they *have* to update to get support
<rickspencer3> dmj_nova, ^
<dmj_nova> rickspencer3: the tricky thing for many of our users is not that they need "stable" in the LTS sense, so much as updating several times mid-project
<mathor_> and what is wrong with that, mpt?
<dmj_nova> Now shortening the support cycle substantially for non-lts is certainly fine
<mpt> mathor_, nothing! I'm proposing that as an escape route. :-)
<dmj_nova> rickspencer3: wrt sunk cost, it sounds like many players would have an issue going forward with no raring release
<rickspencer3> dmj_nova, yes
<rickspencer3> there's been a bit of a spread in the reaction
<mathor_> Ubuntu could essentially get to a point where UDS is continuos with the all-web concept
<dmj_nova> Why not make the rolling a 6 month rolling
<dmj_nova> instead of the monthly
<rickspencer3> dmj_nova, that's a very fair proposal
<dmj_nova> and only have enough overlap to ensure people have a bit of time
<rickspencer3> we keep doing the interim releases, but we don't support them past the next one
<dmj_nova> say 1-6 months
<rickspencer3> dmj_nova, well, I think we would not do that
<rickspencer3> or it's not rolling
<dmj_nova> so each release gets 7,9, or 12 months , whichever time period to choose
<rickspencer3> to get support you have to update, I would think
<Limurx> or stay with the LTS, sounds pretty fair to me
<dmj_nova> rickspencer3: should be a tiny bit of overlap I think
<rickspencer3> could be
<dmj_nova> to give a bit of leaway for updating
<rickspencer3> well ... I don't think we would want to do an SRU or security updates
<mathor_> with our current options, users are forced to upgrade every 6 months, which really means re-installing their OS.  Upgrading from 12.10 to 13.04 is not an easy process
<dmj_nova> so you have a bit of time to get eggs in order or get through the deadline next week before rocking the boat
<rickspencer3> dmj_nova, I think if updating rocks your boat, you are an LTS user
<smartboyhw> rickspencer3 how about 3-month rolling release?
<rickspencer3> smartboyhw, all good ideas
<mpt> I see lots of people wanting lots of different frequencies :-)
<dmj_nova> rickspencer3: I'm talking very short term update qualms
<rickspencer3> well, then they could just not update
<mpt> Almost like it's a job for a slider in a dialog somewhere
<Limurx> As mentioned, if the 3 month release needs more testing or other effort than the daily images, there's something wrong...
<dmj_nova> so you don't get surprises on a bad day, even when updating is not a general problem
<rickspencer3> mpt, it's not that easy
<dmj_nova> rickspencer3: what about security?
<rickspencer3> dmj_nova, that's my point
<rickspencer3> we don't want to duplicate support across relesaes
<dmj_nova> rickspencer3: I'm trying to suggest a happy medium
<mathor_> This is why LTS works. If you need stability and you do not like change, it just works.  You cannot have your cake and eat it too, so you cannot have the latest and greatest and have  the amount of stability to warrant shipping software on a system.   LTS is the only good option for enterprise customers, professional users, institutional users, and OEMs in general
<timrc> this is more of a Fireside Chat w/ jcastro than a plenary :)
<dmj_nova> reduce duplicate support a lot
<rickspencer3> dmj_nova, understood
<mpt> rickspencer3, I know, we couldn't just update to latest if we want it to be more stable than the development version. But maybe we could update to latest-known-good.
<timrc> erm
<jcastro> timrc: ask questions then
<jcastro> :)
<dmj_nova> but provide just enough to make life easier on certain kinds of pro users
<rickspencer3> mpt, it's a matter of providing security support
<dmj_nova> which is why I suggested the small overlap
<dmj_nova> like say a 7 month support cycle for a 6 month release
<smartboyhw> yep
<mpt> rickspencer3, AIUI, the issue is that security updates will sometimes depend on non-security packages. First is there any data on how often that happens, and second would it matter?
<dmj_nova> and that means that for part of a year you do have an additional release to support
<rickspencer3> mpt, yeah, if we force an update of a subset of newer packages for a security update ... that is a terrible experience and very difficult to support
<dmj_nova> but your efforts are otherwise much reduced from current
<dmj_nova> while not rocking the boat for developers like us
<rickspencer3> dmj_nova, yeah, I understand what you are saying
<mpt> rickspencer3, terrible in what way?
<dmj_nova> or vendors like system76
<rickspencer3> mpt, you take a "security update" and it updates some of your apps?
<rickspencer3> then you may was well be on a daily upgrade cadence
<mpt> rickspencer3, ah, so you'd have unexpected UI changes as a consequence of a security update. Understood.
<mathor_> I just do not understand the viepoint of a vendor releasing a 6 month release on their hardware. Why would System76 want to release ubuntu on a computer if it's obsolete in 6 months?
<mathor_> LTS makes the most sense
<dmj_nova> mathor_: 6 month releases have much better hardware support
<dmj_nova> new drivers, graphics stack etc
<mpt> mathor_, from what I understood in the talk, it's because the improvement in big things like Unity and HW compatibility is worth the cost of users having to upgrade sooner.
<mpt> That surprised me, tbh.
<dmj_nova> mpt is right
<CarlRichell> Yes, new drivers and improvement in the release drive our decision to ship non-LTS releases
<dmj_nova> mpt: so imagine using a release as old as Natty
<mathor_> But, essentially, what you are releasing is not the same as what they will have on their computers in, say, 9 months time
<dmj_nova> and then compare to Quantal or raring
<CarlRichell> mathor: same goes for LTS
<mathor_> so, at that point, they are running different software than was shipped with them
<mathor_> they get software so they can abandon it?
<mpt> dmj_nova, I think that was a *bit* of an unfair example, because part of the reason for landing a ropey Unity in 11.04 was to give it more time to bake for the LTS. :-)
<CarlRichell> That is the nature of software.
<CarlRichell> It progresses. The hardware is static when manufactured
<dmj_nova> mpt: a *bit* but generally changes will be quite large and beneficial to users over a 2 year period
<mathor_> it is the nature of software, but goes against the argument that vendors needs a very current yet stable system.
<dmj_nova> mpt: perhaps compare 10.04 vs 12.04?
<FunnyLookinHat> mathor_, the current release schedule is very current yet stable - not sure I follow your argument ?
<dmj_nova> If we can't ship anything but LTS, that's not good
<FunnyLookinHat> dmj_nova, Agreed - it leaves a gaping "middle ground" hole
<dmj_nova> the issue with hardware shipping is a big BIG deal for novacut
<mathor_> I'm not going to purchase a new Ubuntu laptop from System76 every 6 months, but I might every 2 years.  If, as a user, I chose to get constant updates, then what  I am running will be different than what I was shipped.  If I want my system to remain secure because I am a professional user, then I will use the LTS and continue with the software I was shipped and remain happy.   In fact, the LTS backports a lot of softw
<FunnyLookinHat> I think we need to realize that, if there is no good solution for OEMs, then coincidentally, there is actually no good solution for a large chunk of Ubuntu users.
<mathor_> will suffer
<dmj_nova> We have to support at least the newest release that users can buy hardware for
<dmj_nova> right now, that is the 6 month releases
<FunnyLookinHat> rickspencer3, ping?  Will users be able to upgrade from 12.10 to 14.04 or from 13.04 to 14.04?  We need to make sure that we aren't leaving customers on an island
<rickspencer3> hi FunnyLookinHat
<dmj_nova> We really don't want to have to cripple our software for years at a time or alternatively introduce radical changes back into the LTS
<FunnyLookinHat> rickspencer3, howdy ( s76 guy here )
<rickspencer3> if we chose to go to a rolling release today (*if*), we'd have to extend the support period for 12.10
<FunnyLookinHat> What does that mean specifically?  With the network upgrade option to 14.04?  As I understand it, 18 months of 12.10 support leads right to 14.04
<mathor_> This question you ask was the original point that I brought up.  If  you buy a computer with 12.10 there is no easy way to upgrade to 13.04 in a way that leads to a stable system.  So every six months, essentially, the user is left on an island
<danjared> fwiw, Dell has switched to preloading only LTS releases
<FunnyLookinHat> danjared, That's because they are building their own kernel and it would be literally impossible for them to support anything more
<danjared> FunnyLookinHat: we're not building our own kernel
<FunnyLookinHat> danjared, I was misinformed I guess - last I checked you had to pull in some patches for your sputnick project
<FunnyLookinHat> My mistake :)
<danjared> FunnyLookinHat: are you talking about the PPA for Sputnik?
<FunnyLookinHat> danjared, I'm talking about the linux-image that is being generated for the XPS 13 Laptops
<danjared> FunnyLookinHat: We have a PPA for Sputnik, which includes a couple bug fixes and a driver Cypress generously wrote for us, but all those changes are being upstreamed. The PPA kernel is a temporary measure.
<danjared> FunnyLookinHat: This is not done for the many, many other systems we ship with Ubuntu (though not currently in the US)
<FunnyLookinHat> danjared, Ah ok - that is different than I had read. Thanks for clarifying :)
<FunnyLookinHat> Do you think shipping 12.04 for the next 14 months is a good product decision for Dell ?
<danjared> Shipping every release, LTS or not, is possibly feasible for a small company like System76. It's a miserable migraine for a company like Dell.
<FunnyLookinHat> Understood.  Good point.
<danjared> FunnyLookinHat: not speaking for the company as a whole, we're happy about the HWE stack for 12.04
<danjared> (by we I mean the engineers)
<danjared> It's easier to revalidate a small part of the release than an entirely new release
<FunnyLookinHat> My feeling is that 12.04 is going to be a horrible solution for your customers within two months...  and even moreso in 10 ( right before 14.04 ) - you're essentially stuck shipping two year old software.
<kamal> FunnyLookinHat, danjared: fyi, at this point the kernel enhancements for Sputnik have all been upstreamed already (the Cypress driver and the backlight control fixes):  Those fixes all appear in mainline Linux 3.9 kernel
<FunnyLookinHat> To put it in perspective, that would be like shipping 11.04 today - which, if you even run it for a day, will feel like 1997
<danjared> kamal: right, I forgot to mention that they're all upstream now though not in 3.5 AFAIK. thank you so much for all your work!
<danjared> FunnyLookinHat: I would surmise that our customers are more concerned with receiving a system that will still work after they first update their system than having something closer to bleeding edge. Keep in mind that, for us, our customers include companies.
<kamal> danjared: my pleasure -- happy to have the slick XPS machines working so well in Ubuntu (and other Linux)
<danjared> kamal: my pleasure too. my personal system is an XPS 13 :)
<kamal> kamal: me too :-)
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Track: Community | Ubuntu Advocacy Kit - next steps | Url: http://summit.ubuntu.com/uds-1303/meeting/21642/community-1303-uak-next-steps/
<philipballew> Alright, feel free to invite me to the hangout whenever works.
<philipballew> lets get this adk going
<dholbach> hello my friends
<philipballew> rrnwexec, I marked myself as essential to the session, Can you invite me?
<philipballew> hey dholbach
<dholbach> philipballew, let me see if I can get that done
<philipballew> dholbach, alright
<dholbach> I think we still have 5
<philipballew> ah, no hurry
<V3n3RiX> hello all :)
<dholbach> philipballew, if you reload the session page, you should see a "join hangout" link or some such
<philipballew> I see it now
<mainerror> Whoa! I didn't even know that an Ubuntu Evangelists team existed, that's mainly what I do. :)
<dholbach> http://summit.ubuntu.com/uds-1303/meeting/21642/community-1303-uak-next-steps/
<mainerror> That's because the most visible example was the UDS which is big, awesome and stuff.
<wendar> press releases :)
<wendar> It sounds like the messaging around a 1-month cadence is very important to get right.
<jonobacon> wendar: good idea :-)
<wendar> (wrong channel)
<X3MBoy> I can't attend the hangout from my work. I'll read you from here
<czajkowski> surely sorting out where its resting plce is the last bit to think about
<czajkowski> putting the content in to the kit is the main thing
<philipballew> yeah, good point czajkowski
<czajkowski> eh no whack
<mainerror> :D
<philipballew> :)
<czajkowski> philipballew: I've been known to make the odd one from time to time!
 * philipballew laughs and smiles
<czajkowski> is there a specific editor to write this restucted text on ?
<mainerror> czajkowski, every normal text editor you want.
<czajkowski> nods
<Cracknel> czajkowski: I've seen something that displays a preview so that you know how it will look rendered
<mainerror> There's quite a big cross-over between RsT and Markdown. We've switched to RsT in CouchDB as well.
<czajkowski> jonobacon: well the big thing is a person may think they write good docmentation and the person reviewing may not think it's great, and then it can also be a case of it reviewing of text can become rather long winded
<czajkowski> Cracknel: thats what I would have thought of
<Cracknel> czajkowski: found it: http://www.webupd8.org/2012/03/retext-30-released-text-editor-for.html
<Sid_Payton> QUESTION: Are you planning on creating a unified website which could be used by LoCo Teams to run on their own server and customize it to their needs? It would be nice to have a unified Loco Website expirience which automatically shows news on all Loco sites etc.
<czajkowski> recommendation: not long winded sentences :) concise and to the point sentences are far better.
<czajkowski> aye acctive writing is good point
<mainerror> czajkowski, if you are a Sublime Text 2 (or 3) user there's also an RST preview plug-in as well as RST snippets.
<czajkowski> jonobacon: would putting this on the ltp as the resouce there, again adding another incentive to go there, currently we haev the wiki, AU, and then spreadubuntu, and it'd be nice to have it in one location.
<jonobacon> czajkowski: would you like to join the hangout?
<czajkowski> sure
<jonobacon> cool
<jonobacon> dholbach: can you invite czajkowski ?
<dholbach> sure
<mainerror> Doesn't sound so happy at the moment. :/
<eps> I wish there was a "Reference Sheet" ... one double-sided page (Letter or A4) designed for a three-ring binder.
<eps> It's very difficult for someone new to Ubuntu to find where the "useful" information is ... it's all scattered.
<eps> I'd been using Ubuntu for years before I found out about the Ubuntu Manual Project
<eps> I didn't know about Ubuntu Friendly
<dholbach> yeah, a link to "blessed resources" might be good :)
<YoBoY> the actual licence : Â« Version: 0.1. Â© Copyright 2012, Ubuntu LoCo Community Â»
<YoBoY> not open
<Cracknel> http://bazaar.launchpad.net/~uak-admins/uak/trunk/view/head:/COPYING
<dholbach> hum... you can read the license of everything on /usr/share/doc/uak-en/copyright
<YoBoY> (on the bottom of the generated html)
<dholbach> YoBoY, how is that a license?
<dholbach> YoBoY, that's maybe a copyright holder, but not a license
<bob_> got a link for the google hangout?
<dholbach> the majority of the stuff in there is CC-BY-SA-3.0 - some logos and css bits are under other licenses as they were borrowed from somewhere else
<czajkowski> the Uak is already Creative Commons - Attribution Share Alike
<czajkowski> https://launchpad.net/uak
<Sid_Payton> dholbach: Will you be at the Ubuntu LoCo-Metting in Berlin on 13th  of March?
<YoBoY> dholbach, so it's just a bug on the generated html ^^
<dholbach> YoBoY, yep, that might be - will file a bug
<mainerror> dholbach, I think the disclaimer and the license got mixed together there.
<mainerror> If you scroll way down there is a CC notice.
<dholbach> Sid_Payton, is that the wednesday meeting in c-base?
<Sid_Payton> dholbach: Yes
<dholbach> Sid_Payton, I might - not 100% sure yet - I might be travelling - but it'd be good to hang out with you in c-base again :)
 * mainerror nods
<Sid_Payton> dholbach: would definitly be nice. would like to talk about the advocacy kit a bit more in detail and my involment in Ubuntu to hekp
<dholbach> awesome :)
<bob_> is it possible for me to join the google hangout ?
<dholbach> Sid_Payton, if you drop me an email I'll let you know about my plans next wednesday
<Sid_Payton> dholbach: which adress? you got so many
<dholbach> Sid_Payton, dholbach at ubuntu.c
<Sid_Payton> dholbach: will do
<YoBoY> lot of things in the actual documentation in the uak are (or should be) in the loco team portal directly
<czajkowski> YoBoY: yup
<YoBoY> do we plan to add them soon ?
<dholbach> YoBoY, yes, I noted down an action item
<YoBoY> ok, :p
<dholbach> I'll reach out to the folks, they can probably reuse some bits from what we do with the packaging guide
<dholbach> http://developer.ubuntu.com/packaging/
<YoBoY> sorry, I need more screens and eyes
<YoBoY> thanks everyone
<Billynkid> Should it link in ubuntu-tour and ubuntu-advert even though those teams are kinda quiet
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Track: Community | LoCo Community - what's next? | Url: http://summit.ubuntu.com/uds-1303/meeting/21640/community-1303-loco-community/
<quesh> bye
<jono_> rrnwexec, https://plus.google.com/hangouts/_/9ed4c7672878100c61fc46b147522b5e19b4d0a8?authuser=0&hl=en
<philipballew> jono_, If there is room, id like to join this hangout
<philipballew> did not see the link to join pop up in summit and i marker essential
<skellat> And I've merely got static saying we're not started yet
<philipballew> skellat, were gonna start in just a few
<jonobacon> can you folks see us?
<jonobacon> philipballew: you are invited
<skellat> Yes
<ElderDryas> yes
<skellat> You're up Jono
<skellat> Yes
<BobtheBober> are we referencing Loco member community growth specifically, or growth in the community as a whole?
<jonobacon> BobtheBober: primarily LoCo team member growth
<skellat> Interstate LoCo cooperation is not necessarily an issue.  I have a hard enough time working to string people together across The State of Ohio since we are so spread apart.
 * YoBoY waves :D
<YoBoY> (and we also have "failures" in france for our events :p no global jam for example)
<skellat> Our last virtual statewide event for Ubuntu Ohio: https://wiki.ubuntu.com/OhioTeam/IRC20130128
<BobtheBober> isn't every ubuntu user a type of "loco" member, as they are using, and ultimately a part of the process to help improve Ubuntu as a whole?
<BobtheBober> its more so a question of how do we engage the users to help..
<weddle> what about loco type teams that are not purely geographically based?  user based communities around interest rather than just geography?
<BobtheBober> organization
<YoBoY> it's hard to be enthousiast when we have so many good and bad surprises provided by canonical and have to explain and defend them with people
<skellat> Probably quite a bit is change management.  Within the past seven days there has been an awfully large amount of changes to digest in one fell swoop.  A glide path to transition into these changes would be nice.
<skellat> Convergence is great but we needed to ease into it a bit more.
<skellat> A community is made up of many people and turns like an overloaded warship which is to say it does not make turns on a moment's notice.  Ohio got caught by this with people unable to make schedule changes to be able to participate.
<YoBoY> an example, the shopping lens was a great privacy problem, we work in france with lot of groups defending the internet neutrality, the privacy, etcâ¦ and it was hard to explain this new direction
<BobtheBober> Canonical cant express every change in advance due to leaked information.
<YoBoY> (and we still can't explain where we are going with that)
<BobtheBober> it wouldn't be news
<eps> I perceive a growing lack of transparency, and that's a fundamental paradigm shift.
<weddle> EXACTLY - re posting to locos
<BobtheBober> maybe there is a bigger question there. If canonical cant pre-inform supporters and Loco members, how can loco members and supporters support those changes that they dont know about.
<skellat> BobtheBober: We can't hit everybody with Non-Disclosure Agreements
<weddle> if we could give the locos "sales collateral" it would be great
<YoBoY> transparency it's not a problem for me, lake of information when the news is released is the problem. We only have blogs, twits,â¦ no roadmap on where canonical is going with the feature announced
<BobtheBober> understood, but loco members can support or help build products they have no option to assist with.
<YoBoY> where are those links ?
<winael> @yoboy in fact after chatting with David CallÃ© I understood that there were more privacy issues with third apps before the shopping lens
<YoBoY> winael, yes, but not on the home dash
<skellat> Horse burgers!
<BobtheBober> fragmentation
<weddle> like android ;)
<winael> for ex lens utility sent privacy info to weather website or other third services without any proxy server
<winael> and was access directly in the home lens
<BobtheBober> we should evaluate our incentives for users to join the loco community and contribute. Maybe why they are interested
<skellat> Paradigm shifting without a clutch
<skellat> I blogged about that on planet
<eps> What if, two years from now, phones and tablets have ended up as relevant as netbooks are today? Desktops are still relevant, particularly for content creators.
<BobtheBober> fair summary
<jasnow> Question: How do you know that a LoCo has fallen apart?
<BobtheBober> incentive
<skellat> AGAIN...change management was needed
<YoBoY> +1 the uds change is difficult to explain, my point of view is we are loosing lot of fun
<commandoline_> YoBoY: but the upside is more community members can attend. I've never been to a physical UDS, and wouldn't be there this time if it was still physical.
<quesh> laura +1
<BobtheBober> what is the reasons, the incentives for someone looking to join the loco team. if we understand this, maybe we can grow those reasons, or re-evaluate what isn't working
<YoBoY> commandoline_, not reallyâ¦ it was already online for people who can't attend physically, we just added video hangouts, and a better summit website for that
<quesh> czajkowski: +1 once a month
<skellat> Maybe we could revitalize the Team Reports at a glance facility on the Wiki
<BobtheBober> a meeting, that the loco leaders must attend?
<czajkowski> BobtheBober: never going to happen due to timezones
<czajkowski> and work commitments
<quesh> Reports + meeting is a good idea
<BobtheBober> question? the point of moving UDS online was that people wanting to attend couldnt due to the physical world. It was a benefit to move it online so that everyone can attend. Why dont we take this same approach with loco teams?
<quesh> czajkowski: it may be necessary to have two different times
<commandoline_> YoBoY: and that's a real improvement. I've followed an audio stream at an earlier UDS, but it's completely different.
<snap-l> I think the biggest reason to join a loco team is just to know you're not alone in your geographic regioin
<snap-l> jono_: you're just not a joiner. ;)
<philipballew> good point snap-l
<BobtheBober> ha
<YoBoY> commandoline_, seeing the people is great yes, but I assure you, it's not the same with a real face to face ;) last uds we had hangouts too, it was great too, not like the ones now
<YoBoY> but this discussion on the uds online, is for another day ;)
<commandoline_> YoBoY: agreed :)
<skellat> BobtheBober: Doing LoCo events virtually is interesting.  We've been experimenting with it in Ubuntu Ohio and had some push back against using Google Hangouts.  We haven't had an alternative to it located yet but use IRC & the mailing list heavily.
<skellat> CYLONS!
<snap-l> *cough* team reports.
<snap-l> ++
<snap-l> jono_: ++
<snap-l> How does this affect reapprovals, then?
<skellat> Well, there goes a few months work for Ubuntu Ohio relative to reapproval work then
<BobtheBober> you couldnt strip all approvals, you would have to grant some form of unity
<snap-l> jono_: amen
<theDoctor> what if we ditch the approvals but keep the notion of "unnapproved"
<YoBoY> what's the point to be "observed" by the loco council if there is no more a small distinction ?
<BobtheBober> I cant wait to join that unnapproved loco team. life on the WiLd side !!
<theDoctor> ^lol!
<YoBoY> unnaproved is worse than approved ^^
<snap-l> I've had several thoughts of "what would we lose if we bacame unapproved"
<theDoctor> That way there aren't approved teams, but dysfunctional teams can be disapproved
<YoBoY> nothing
<snap-l> and honestly, outside of prestige, not a lot
<YoBoY> just live cdsâ¦
 * commandoline_ doesn't see the difference between the loco team I'm in before and after the approval, either.
<system76chick> What if the approved, unapproved was completely removed and the Loco council was in place to recognize LoCo groups and the more work each group is doing, the more they get recognized
<snap-l> recognition is awesome. We should do more of that
<snap-l> but the approved / unapproved process is overhead
<system76chick> If we're doing this to advance the Ubuntu project, why does approval matter? Labels do more harm than good
<BobtheBober> redefine loco teams and members, rebrand. Loco isnt what it used to be.
<snap-l> Lcoo is still an important word, though
<YoBoY> system76chick, it's why we are looking for another term
<snap-l> but approved / unapproved lost meaning
<system76chick> Nomination/ Recognition remove the negativity all together. The last thing a Loco group wants to hear is that the work they did wasn't good enough
<snap-l> system76chick: ++
<BobtheBober> i dont personally get the importance of distinguishing loco teams by location
<weddle> +1 it would be great to see teams form around communities of interest and not just geographies
<BobtheBober> here here weddle
<weddle> e.g....  people using ubuntu in corporate contexts
<system76chick> How about a point system for Loco Groups and the loco council was in charge of assigning the points? "U Points"
<weddle> people using ubuntu to do XYZ
<BobtheBober> loco > projects, ideas, work
<YoBoY> in my country, if someone want's to create a local group, we help to create it, because it's important for people to fill they have a real group, where they can meet others. Each country is different for that
<weddle> @Bob totally agree that location is less relevant...  we are on a virtual UDS here
<BobtheBober> bullet points on pad
<snap-l> If I never have to fill out a team report ever again, I'll be a happy man. :)
<weddle> could totally have virtual locos
<JoseeAntonioR> did you guys get to discuss the LoCo name thing?
<theDoctor> <-- this guy agrees with Jono
<system76chick> Takes away from the focus of what Loco teams are here for
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-1303/community-1/ - http://ubottu.com/uds-logs/%23ubuntu-uds-community-1.log
<BobtheBober> touch on weddles point
<BobtheBober> local is not what local is anymore
<philipballew> good thoughts system76chick
<BobtheBober> here we are on a virtual UDS, talking about Loco
<system76chick> Thank you
<system76chick> lol
<BobtheBober> Thanks everyone
<theDoctor> good sessio guys!
<theDoctor> *session
<YoBoY> thanks everyone
 * YoBoY is starving ^^"
<airurando> thanks all
<quesh> utc time
<quesh> :)
<Billynkid> thanks
<philipballew> thanks for the good input!
<jasnow> thanks
<BobtheBober> are the google hangouts recoreded
<snap-l> Thank you, everyone!
<BobtheBober> and watchable later?
<JoseeAntonioR> BobtheBober: they are
<jasnow> yes
<BobtheBober> any links?
<YoBoY> BobtheBober, yes
<YoBoY> just refresh the page in a couple of minutes
<BobtheBober> alright sweet
<BobtheBober> no other events for today right?
<JoseeAntonioR> nope
<system76chick> Short and sweet
<system76chick> Time for lunch! Have a great day everyone!
<YoBoY> I'm going to make some crepes for my dinner :)
<thaman> except for 12.10
<quesh> YoBoY: \o/
<YoBoY> quesh, avoue que t'en veux :D
<quesh> YoBoY: oui
<melodie> hi
<YoBoY> hi melodie
<melodie> he YoBoY !
<melodie> this is a web chan so we are not notified, right ? :)
<YoBoY> don't really know how the web irc client works
<YoBoY> I use xchat
#ubuntu-uds-community-1 2013-03-06
<tvtue> hi all
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Track: Community | IRC team | Url: http://summit.ubuntu.com/uds-1303/meeting/21674/community-1303-irc-team/
<AlanBell> hi all
<AlanBell> no hangout yet . . .
<AlanBell> jono is on the case
<UbuPhillup> hi
<UbuPhillup> yes
<Tm_T> hi
<AlanBell> jono: can you add "Jussi âTm Tâ Kekkonen"
<AlanBell> anyone else got a google plus name to add?
<AlanBell> jono: IdleOne / Giovanni Chiazzese
<Tm_T> stupid google not allowing Tm_T as nickname
<AlanBell> indeed
<Myrtti> I'll just lurk and watch and annoy you via IRC
<Tm_T> Myrtti â¥
<AlanBell> ok, so lets chat on IRC too and you can all watch me type
<Myrtti> I see you're at the office AlanBell
<Myrtti> nice business gear, button up shirt and tie and all
<AlanBell> yeah, we keep it formal
<UbuPhillup> nice
<cm-t_phone> hi
<UbuPhillup> hi
<baizon> sehr gut!!! http://www.spiegel.de/wirtschaft/unternehmen/olg-duesseldorf-haelt-netzentgelte-befreiung-fuer-verfassungswidrig-a-887209.html
<baizon> sorry wrong channel :(
 * tsimpson_ pokes his head in
<Myrtti> in case it hasn't been obvious from my moanings of late, I'll probably move over to Debian on my personal systems. Will stick around in some of the channels, but dropping some channels out and probably my Ubuntu membership as well.
<Unit193> Heya, tsimpson_.
<Myrtti> and of course still a freenode staff member.
<IdleOne> Good morning, sorry I am late
<UbuPhillup> #ubuntu-de is good
<Mamarok> sorry, have to go...
<Tm_T> wouldn't hurt asking "what kind of communication you would need?" in time to time (:
<popey> jono: s/the mistake we have made/among the many mistakes we have made/
<AlanBell> o/ popey
<popey> o/
<jono> popey, yup
<popey> i am unconviced "lack of info for the community" is the big issue at hand.
<UbuPhillup> there is no officel wiki for ubuntu in germay we have ubuntuusers.de instead
 * IdleOne checks
<IdleOne> Yup, human.
<tsimpson_> apparently we have ~100 members https://launchpad.net/~ubuntu-ops
<Myrtti> it's not because we particularly want to help, but it's easier to help with things going right on the first try than try to put off the fires when they've been done the wrong way and there's a great hurry to fix them, because X Y and Z start in 5  minutes
<Tm_T> yeah I rather help when it causes less work and damage (:
<Tm_T> and also I rather help than watch things go wrong just because
<Myrtti> jono: you have to excuse us for thinking it's already been decided when a lot of things have seem to be told to people on a 5 day notice without much discussion. It kinda sets people's teeth on edge
<Myrtti> but I'm sure this has been said by many people already, so w/e
<Myrtti> there was at one time some mirroring of the bots
<Myrtti> when the responsibility of running them moved from Seveas to others
<Myrtti> and jussi's was just one of the mirrored ones, I had one mirrored one as well ready to be launched if something goes sour
<tsimpson_> and while we are talking about bots, we do have an issue with ubot2
<IdleOne> yup
<tsimpson_> the issue being that it's horribly out of date and not maintained
<tsimpson_> I'd like to have the bots decentralized, but that seems like something that requires much more planning and coordination that I can do on my own
<Myrtti> tsimpson_: I think people would be happy with functioning backups for a start
<tsimpson_> and then there's the long awaited open-sourcing of the floodbots
 * Unit193 more or less considers his a backup.
<jussi> bringup later or?
<AlanBell> yeah, the bans database is probably the main thing that isn't very redundant
<tsimpson_> someone (smart) needs to come up with a way to integrate LP and ChanServ (access lists)
<Mirv> QUESTION: where are the etherpad notes? :)
<AlanBell> tsimpson_: I did get some way on that
<tsimpson_> Mirv: http://pad.ubuntu.com/uds-1303-community-1303-irc-team
<AlanBell> hi Mirv I haven't been making any as such
<popey> outrage!
<Mirv> AlanBell: ok, I was just joining after other session to get some sort of summary
<AlanBell> Mirv: about to start making some
<Mirv> tsimpson_: reading that instead now
<Tm_T> Mirv: basicly "we want better communication and usage of our services" (:
<popey> Mirv: in summary: Canonical are evil.
<Mirv> tsimpson_: I mean the IRC log
<tsimpson_> nothing much to read atm
<Tm_T> popey: awww
<IdleOne> lol popey
<ahayzen> popey, where is evilpopey today?
<vibhav> popey: NoTheyArent
<vibhav> (tm)
<tsimpson_> logs are on ubottu.com and (please use) irclogs.ubuntu.com
<evilpopey> boo
<ahayzen> o/ evilpopey
<UbuPhillup> i must left
<UbuPhillup> by
 * ahayzen runs to next session
<roadmr> hello again X)
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Track: Community | Quality in a rolling release world | Url: http://summit.ubuntu.com/uds-1303/meeting/21670/community-1303-quality-rolling/
<balloons> hello :-)
<balloons> just speak up if you'd like to be in the hangout
<vibhav> balloons: o/
 * stgraber waves
 * gema_ shouts
 * cjohnston pops balloons 
<balloons> ohh look
<stgraber> balloons: can you send me the link to the hangout?
<balloons> my missing notes
<balloons> yes.. one sec to all those who pinged
<cjohnston> lmap
<cjohnston> lmao
<vibhav> balloons: You will eed to invite me to another email, is that fine
<vibhav> need*
<ElderDryas> Can whoever is in charge of the video feed let us know when it sactually tarts for this session, so I don't have to refresh every 30 seconds?
<balloons> ElderDryas, sure thing
<ElderDryas> danke :)
<gema_> balloons: can I have a spot in the hangout?
<vibhav> balloons: me too!
<balloons> k I sent the url to all I believe
<balloons> anyone else who wants to join the hangout?
<balloons> starting the broadcast
<balloons> anyone else who wants to join the hangout?
<janof> invite please
<balloons> anyone else who wants to join the hangout?
<cjwatson> I'd like to
<ElderDryas> Names and nicks?
<balloons> anyone else who wants to join the hangout?
<philipballew> balloons, if theres room, i can
<plars> restored
<pitti_uds> balloons: would that include things like "we have a PPA with a proposed new X.org stack"?
<plars> ah, sorry, I thought you were looking for it still. Feel free to delete
<plars> I can join if you have room
<gema_> plars: your lower third
<skellat> PPAs are going to screw those of us who use things like the BeagleBoard-xM in a desktop role
<plars> gema_: yes, one sec
<pitti_uds> skellat: I didn't mean PPA literally as we have them today; obviously we need some kind of "staging areas" which include ARM
<micahg> I think we need a second britney instance to give us human testing before packages hit most end users in a rolling release
<skellat> pitti_uds: Definitely.  I look forward to seeing that coalesce.
<micahg> ramping up backports would be great as well, if be able to automate some of the backports testing, that could certainly make approving backports easier
<jasnow> what is SRU?
<pitti_uds> stable release update
<stgraber> stable release updates
<balloons> stable release update
<jasnow> thank u
<gema_> https://wiki.ubuntu.com/StableReleaseUpdates
<cjwatson> https://wiki.ubuntu.com/StableReleaseUpdates for the current ruleset
<cjwatson> heh
<roadmr> jasnow: hehe :) it's the updates you get offered by e.g. update manager to an stable, released version of ubuntu
<cjwatson> micahg: right, there's a work item on another spec for that
<jtaylor> micahg: displaying backports that need testing in some public place would be good, I don'T think people see the bugtracker
<jtaylor> (also drop the rdepend build deps requirement)
<micahg> cjwatson: WI for second britney?
<cjwatson> yes
<tumbleweed> any idea which spec?
<micahg> cool
<bjf> if we are going to take the resources we use for putting out a 6 month release to doing more SRUs and backporting more packages we should limit those to the last LTS and not to every previous release
<cjwatson> the first rolling release session yesterday IIRC
<vibhav> jtaylor: Do you mean a dedicated page for backported packages?
<cjwatson> bjf: yes
<tumbleweed> oh, didn't realise it hady any work items :)
<micahg> cjohnston: the problem with that is that some people don't want their apps changing out from under them in an LTS
<jtaylor> vibhav: I was maybe thinking software-center
<cjwatson> right, new versions that introduce interface changes are exactly what some people run LTSes to specifically avoid
<plars> hangout plugin just crashed
<diwic> plars, works here
<vibhav> jtaylor: ah
<cjwatson> so I don't think we can just dump -backports into -updates
<cjwatson> (say)
<barry_> backports may be more difficult to support because they can sometimes cascade into updating a bigger dependency stack
<janof> isn't the point of moving to a rolling release to free up resources, devs are not working to support 3-4 versions of Ubuntu, and doing backports will defeat this purpose?
<diwic> plars, if you mean the live stream
<cjwatson> janof: it's a trade-off
<janof> the trade of is not having to deal with this when moving to a rolling release, its the main point IIRC
<cjwatson> janof: we can't just drop stuff and leave users without a replacement that's acceptable - trying to figure that kind of thing out is exactly why we're having these discussions
<cjohnston> janof: not really, its only going back one vs multiple
<cjwatson> and I would hope much more targeted
<janof> cjohnston, so the plan is to support the existing, and the next future rolling release, no past versions, is that correct?
<ara> why we are mixing the rolling release with the LTS in terms of stability?
<theDoctor> Am I understanding correctly: the LTS is separate from the rolling release?
<janof> ara, exactly
<cjwatson> at the moment developers generally SRU to every affected stable release regardless of whether there's any pressing reason to believe that there's any users
<cjohnston> janof: continue supporting old releases until the EOL.
<micahg> I don't think the main archive LTS criteria should change since it needs to be stable, it'll be much easier to backport newer stuff from a rolling release to the LTS though as we currently have to backport through the regular releases
<cjwatson> janof: there is no fixed plan as yet; there are proposals
<skellat> Upgrade from CD was deprecated once the alternate discs went away, no?
<jasnow> security fixes too
<janof> cjohnston, this would mean that the benefits that we desperately need for the next version, 13.04, would not be feasable until EOL of older versions.
<cjwatson> ara: the proposal to withdraw non-LTS stable releases means that some users will need an acceptable replacement
<cjohnston> janof: how so? not everything would get backported
<ara> cjwatson, yes, I agree with that, but the LTS will stay stable
<cjwatson> janof: let me be clear: we are not going to put the newest version of everything into the LTS
<balloons> if anyone else who wants to join the hangout, let me know
<cjwatson> but that is not to say that the current constraints are 100% fixed either
<vibhav> jtaylor: Instead of software-center, I think it should be more sensible for a universal resource which could be accessed from everywhere
<jasnow> upgrade from 12.04 to 13.04?
<yofel> why would you upgrade from 12.04 to 13.04?
<yofel> policy should still be 12.04->12.10->13.04
<cjwatson> because in order to support upgrades from 12.04 to 14.04, upgrades from 12.04 to 13.04 ought to work
<pitti_uds> it needs to work anyway
<jtaylor> vibhav: that already applies to the bugtracker
<cjwatson> it's a lot easier if you don't have to put all the upgrade support back in at the end
<pitti_uds> as the 12.04 -> 14.04 upgrade needs to work, we need all the postinst quirks etc.
<yofel> ok, good point
<jasnow> brand new user - had a cd of 12.04, but thought 13.04 was the target
<sebsebseb> hi
<vibhav> cm-t_phone: If there is a LTS version for every seeded package, the idea sounds great
<ara> but they might skip putting a new HWE in .3
<pitti_uds> cjwatson: I think we should test/fix 12.04 -> daily and and 12.10 -> daily every day
<micahg> I was envisioning daily ISOs + automatic testing of both the "stable" rolling release and the "unstable" rolling release
<cjwatson> pitti_uds: agreed
<barry_> well, both yesterday->today and last monthly->today
<cjwatson> vibhav: that's massive overkill - take for example man-db, really doesn't need a separate LTS version
<janof> the least amount of release versions surely is desirable. utilization of resources.
<vibhav> cjwatson: Well yes, I was wrong here
<cjwatson> And I would say that's the common case
<barry> right, because one day, today's snapshot will *be* the monthly :)
<janof> so two versions of the RR, daily and monthly ?
<selena2013> greetings from Miami
<vibhav> cjwatson: Excluding packages which dont need to have LTS versions
<sebsebseb> selena2013: greetings from England
<cm-t_phone> vibhav: yes, but to be honnest i try to see that from the point of a big company, because they can not spend on migrating all their custom tools and apps on monthly(but we are more in the LTS talk than SRU)
<cjwatson> vibhav: Which is most packages
<vibhav> Indeed
<thomi> cjwatson: you've destroyed my world :(
<micahg> I think that with adding the second britney migration would allow people to receive updates in a more delayed fashion which might alleviate the need for monthlies since there will be increased stability and quality in the rolling release
<skellat> From this it really sounds like monthly roll-ups would be a nightmare
<janof> is LTS still a term we will use with a RR?
<ogra_> https://lists.ubuntu.com/archives/ubuntu-devel/2013-March/036798.html ....
<pitti_uds> janof: it's two different things
<pitti_uds> janof: future LTSes will still be what they are used to be, nobody was debating those
<janof> right, but im saying if we move to RR, the LTS term will be sunsetted and only reflect past releases, is that correct?
<pitti_uds> janof: ah, naming hasn't been discussedyet
<cjwatson> That's not true
<cjwatson> None of the rolling-release proposals alter the support terms of LTS releases, past or (AFAIK) future
<pitti_uds> cjwatson: I think he means calling them "LTS" doesn't make too much sense any more, as we woudn't have other kinds of releases
<janof> right, it defeats the entire purpose
<cjwatson> *shrug* Might also be too confusing to change
<cjwatson> Least of our problems, IMO :)
<janof> fair enough
<janof> daily builds = new beta / alpha versions
<pitti_uds> gema_: we have several scenarios right now, like "default install", "all of main", and the huge "everything that has a .desktop file"
<selena2013> so a regular user will choose between LTS and rolling release in the future
<pitti_uds> gema_: these give quite some good coverage
<vibhav> stgraber: IMO, SRU's for new versions of packages would be helpful if some interface in the old version was depreceated
<yofel> janof: for rolling it would have to be at *least* beta quality
<janof> selena2013, thats sorta my point, thats the same problem we have now
<janof> that choice hurts ubuntu
<sebsebseb> selena2013: yep I think that's the idea,  rolling release and LTS supported for years
<vibhav> stgraber: i.e, only update those packages which have been depreceated
<pitti_uds> stgraber: we also check for orphan or changed conffiles
<janof> the point of moving to an RR, im not not mistaken, is to provide updates faster, and to save resources by not having to support LTS and other versions for years
<pitti_uds> plars: do you know if we run the post-install ISO tests on the auto-upgrade tests as well? it seems we should
<janof> LTS, the term and the physical being, wouldnt make sense with a RR
<thomi> autopilot is already run before packages are relased...
<mmrazik> thomi: but there would be value to run it e.g. when X is released (and there is no change to unity)
<plars> pitti_uds: iirc it's a slightly different set of tests
<thomi> and the tests specify the unity config to use, so I'm not sure AP is going to help you much here
<pitti_uds> thomi: but upgrades might change some of its assumptions, so running again after e. g. an LTS->LTS upgrade makes sense
<mmrazik> but I'm not sure if LXC /X is going to be an answer
<selena2013> i dont have a problem with that , i would recommend newcomers LTS . But if you want the latest and greatest you can choose RR
<plars> pitti_uds: most of the upgrade ones are around making sure that we got the kernel we expected after the upgrade, etc
<mmrazik> we had troubles to run the tests in a VM (but maybe things changed)
<sebsebseb> selena2013: yep that's the idea, RR instead of the six month releases
<pitti_uds> plars: right, I see that we need some addiitonal ones; but we could also run the post-install iso tests?
<thomi> mmrazik: sure, but you get that if you run AP as part of the X release tests.
<plars> pitti_uds: I don't think there's anything that would keep us from expanding those
<yofel> question: how are mesa upgrades currently tested? I remember too many cases where a new mesa version broke some rendering in a driver and caused issues in KDE. Can that be somehow catched at all?
<mmrazik> thomi: right
<thomi> mmrazik: I just meant that using autopilot to test the *upgrade* of unity (as it stands today) won't get you much extra
<dobey> balloons: wouldn't the automated daily images still exist?
<mmrazik> thomi: oh. agree with that.
<pitti_uds> to all extends
<dobey> the monthly would be the current daily
<balloons> dobey, yes, I believe so
<cjwatson> More or less
<sebsebseb> the dialsy would become the monthly
<cjwatson> The last proposal I saw did require a configuration tweak to dailies just before each monthly
<cjwatson> Which is cumbersome but hard to avoid
<gema_> cjwatson: sorry I muted your quick typing!
<ogra_> hehe
<cjwatson> Yeah, sorry, I could have sworn I'd muted
<ogra_> sounded like drum fire
<dobey> right. to avoid updating until next month
<ogra_> why am i hearing german ads now ?
<cjwatson> This is one of the many difficult issues with monthlies
<cjwatson> I definitely wouldn't assume monthlies will happen, there's still lots of debate
<dobey> right, i don't want to derail the discussion; but i'd just not do monthlies. maybe have a monthly milestone but not a special image/config for it
<jasnow> Remember to help the devs to reproduce an issue when they get a bug by saving images/etc
<cjwatson> Saving the image URL is generally enough
<cjwatson> We can extract package versions from that
<micahg> being able to match package versions to RC bugs seems important
<cjwatson> dobey: There are many good things about having some kind of monthly rhythm, e.g. dev milestones, marketing, etc.; and I can see the point of images; I just don't buy the upgrade thing
<cjwatson> But yeah, another discussion
<dobey> cjwatson: right
<dobey> cjwatson: which is why i say milestones without images is something i could get behind :)
<vibhav> RRs should be rock solid, IMO
<roadmr> well it depends on what the promise is
<micahg> I would expect quality for the end users to be about equal to the regular releases we produce now
<selena2013> thanks to all developers for the hard work .
<roadmr> if you promise RRs will be stable and usable, that's what I expect
<micahg> s/about/at least/
<roadmr> if you tell me they're to be treated as the current, daily development images where things *may* break, then I'd expect that
<jasnow> draw a picture
<ara> roadmr, ++
<dobey> do-release-upgrade every 2 years instead of every 6 months, basically
<dobey> janof: ^^
<cjwatson> We haven't drawn a picture yet because there are still about a dozen different opinions :-)
<chiluk_> how are we going to provide hardware enablement kernels back to LTS in this new scheme? Similar to the quantal-lts-backports kernel..
<cjwatson> chiluk_: There was a session end of yesterday about that
<chiluk_> nuts... I was on a plane.
<micahg> most server users are probably on the LTS now
<wendar> most ... yeah
<ogra_> chiluk_, there should be a video of that session
<wendar> server is a different world than desktop
<chiluk_> yes a lot of them are..
<dobey> servers not running LTS already are either personal home server users, or crazy :)
<pitti_uds> I can't imagine many production servers who'd want to be rolling
<chiluk_> but a lot of them are running quantal backports kernels as well.
<cjwatson> chiluk_: http://summit.ubuntu.com/uds-1303/meeting/21598/foundations-1303-hwe-stack/
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-1303/community-1/ - http://ubottu.com/uds-logs/%23ubuntu-uds-community-1.log
<micahg> those not on the LTS should be able to handle any bumps that regular end users would be able to handle
<barry> dobey: even home servers use lts :)
<ara> for business desktops will be the same
<ara> lts to lts
<dobey> barry: i do yes. but some people apparently don't
<pitti_uds> thanks
<ara> thanks!
<dshimer> The last 4 minutes sound like: As a nobody end user, daily (1 desktop, 1 laptop) I have two choices. Scary - developer build take my chances (I'm willing but nervous) or Sad - I only get new stuff every two years.
<thomi> o/
<vibhav> o/
<jtaylor> whats the name of the next lts going to be? raring?
<dobey> dshimer: that's how it is now
<balloons> dshimer, my expectation is rolling = non-lts stable
<cjwatson> jtaylor: We'll see
<balloons> not developer edition scary
<balloons> thanks everyone
<jtaylor> cjwatson: it must be raring or "larger" for daily ppas which use ~raring suffix
<cjwatson> jtaylor: We clearly can't decrement
<gema_> balloons: scary salmon?
<dobey> jtaylor: it probably won't be 'rickroll'
<jtaylor> lucky raring is smaller than most other "r" words :)
<cjwatson> jtaylor: But that suffix is horribly misguided for obvious reasons
<balloons> gema_, indeed!
<gema_> I am glad I don't have to name them x)
<sebsebseb> dshimer: a bit like contract phones to an extent, 24 months contract is quite standard, then you may buy a new phone after
<cjwatson> jtaylor: It needs to be changed to ~ubuntuYY.MM before we reach U
<jtaylor> cjwatson: yes but thats a launchpad issue so far I know
<cjwatson> jtaylor: Yes
<cjwatson> Anyway, LP series have a fixed name; renaming would be madness
<dobey> i don't think it really matters if it's ~rickroll or ~ubuntuYY.MM
<cjwatson> Hopefully nobody will require us to do that :)
<dobey> well, until after z
<cjwatson> dobey: It matters once we ... yes
<cjwatson> Which is why I've been trying to fix this for a while before it becomes a crisis :)
<dobey> :)
<cjwatson> We fixed backports a year or two ago
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Track: Client | Ubuntu Friendly usability and feedback improvements | Url: http://summit.ubuntu.com/uds-1303/meeting/21628/client-13033-ubuntu-friendly-improvements/
<dobey> i imagine it's not really that hard to fix the recipe builder code though.
<dobey> anyway, i guess we need to stop discussing that here now :)
<cjwatson> Shouldn't be, just a matter of finding people to maintain and deploy it given lack of LP manpower at the moment
<dobey> right
<cjwatson> There's been an RT open for some kind of upgrade there for months
<cjwatson> But as you say
<dobey> ciao :)
<yofel> jtaylor: I did file a bug about launchpad not using ~ubuntu..., it's low though
<roadmr> cprofitt: hello
<balloons> cprofitt, zyga-uds,roadmr hangout is up
<roadmr> balloons: thanks
<balloons> I'll start it in a few
<ara> who is the track lead in charge for this one?
<ara> can I get a hangout link, please?
<roadmr> cprofitt: are you around?
<balloons> ara, sent
<balloons> anyone else who wants in the hangout, speak up :-)
<balloons> starting in a moment
<balloons> we should be live now :-)
<jedimike_> ara: hi! could I get an invite to the hangout?
<jasnow> Is this the public web site for Friendly? https://friendly.ubuntu.com/
<balloons> jasnow, that's correct
<jasnow> thanks
<roadmr> cprofitt: \o/
<jasnow> like "UPS Tracking" link ;o)
<balloons> ara, try turning off your video to lower your bandwidth needs
<jasnow> Can you report the submit status without the user's identify?
<bobthebobber> invite please
<roadmr> jasnow: status as in, it was accepted/processed, or rejected due to failing tests? is this what you mean?
<balloons> anyone else who wants in the hangout, speak up :-)
<balloons> bobthebobber, inviting
<jasnow> yes
<rrnwexec> one thing to consider is the difference between "works without any tweaks" and "works if you apply some patches, additional drivers, confi changes"
<rrnwexec> *config
<rrnwexec> Ubuntu Certified handles this by saying "Certified (with Notes)"
<cprofitt> rrnwexec: yep
<cprofitt> we can do that as well on Friendly
<rrnwexec> QUESTION: what about sending incomplete results? if I only run 3 tests (out of 10), shouldn't i be able to submit what i have done?
<cprofitt> rrnwexec: I ping them on your question in a second
<roadmr> deliberately crashing checkbox!
<rrnwexec> there is still a theme out there that says "ubuntu works on everything." Improving SEO of Ubuntu Friendly would help, but we also need a strong(er) awareness campaign.
<cprofitt> rrnwexec: you can help us with the SEO
<cprofitt> :)
<rrnwexec> cprofitt: yes, i can blog about it, post to lists, etc. that may help.
<ara> roadmr, doesn't checkbox already support it?
<balloons> ara, roadmr I believe I've resumed tests before
<jasnow> "black hole problem"
<rrnwexec> QUESTION: Is Ubuntu Friendly submission an Ubuntu Accomplishment "trophy"?
<roadmr> ara: resuming tests? yes, but the feature is geared towards resuming after a crash
<roadmr> ara: cprofitt was talking about "oh crap, I need to go now, I want to pause the test and resume later" - we don't accomodate that use case
<roadmr> ara: the only option as he mentioned is deliberately crashing checkbox %)
<ara> jedimike_, searching in Google for ubuntu Acer Aspire 3610 brings the staging site first :-\
<roadmr> \o/
<jedimike_> ara: oh dear... well at least we know the pages are SEO ready...
<cprofitt> we need to both get more results on the UF site ... and increase SEO
<ara> jedimike_, maybe it was only deployed to staging? (seo capabilities)
<swaveck> greetings to zyga ;)
<jasnow> work with LoCo Advocates
<roadmr> rrnwexec: for your question, so it doesn't scroll up and disappear (re: accomplishments). Answer is "No" :(
<jasnow> check before buying on Craigslist
<balloons> first things first should be to fix the submission process I'd think
<rrnwexec> when the site is ready, and the submission process is better, we could spin up a Global "Test Your Hardware" Day.
<rrnwexec> similar to a Jam, but with less jam ;)
<bobthebobber> why dont we incorporate ubuntu friendly into the installer?
<SergioMeneses> rrnwexec, +1
<ssbob_> +1 bobthebobber
<bobthebobber> ubuntu friendly, now friendly +++
<roadmr> bobthebobber: poking the hardware in ways that can make it fails or crash at install time... fun
<bobthebobber> roadmr: ah yeah, good point, but maybe after the install, and before first boot?
<roadmr> bobthebobber: an interesting goal would be making this runnable from the live cd. so boot the "try ubuntu" thing, select "test your system"
<ssbob_> or a slide show page talking about it, as a todo item after first boot
<roadmr> bobthebobber: right now it doesn't work very well mainly because it needs write access to stuff; for instance, if you booted from USB stick it will be unable to test usb ports :/ (ironic because it's 100% certain that they work in that scenario)
<SergioMeneses> I think the slide would be the best
<roadmr> ssbob_, SergioMeneses : that'd be awesome exposure, I'd probably wait until the testing/submitting experience is better
<roadmr> otherwise we'll become the most hated group in Ubuntu :(
<ssbob_> and or make it a feature in the software center (as part of the inventory step)
<ssbob_> something you can toggle on and off depending on paranoia levels
<balloons> http://www.canonical.com/contributors/faq
<balloons> You DO retain copyright
<SergioMeneses> roadmr, you're right but is a great idea :)
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-1303/community-1/ - http://ubottu.com/uds-logs/%23ubuntu-uds-community-1.log
<cprofitt> thanks everyone
<SergioMeneses> see you later!
<philipballew> Looks like this is gonna be an interesting session
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Track: Community | Consider General Contingencies For Xubuntu | Url: http://summit.ubuntu.com/uds-1303/meeting/21666/community-xubuntu-contingencies/
<tumbleweed> pity that it overlapps with the other rolling session
<micahg> yeah
<skellat> It was this or overlap with Jono Q&A
<tumbleweed> pff jono :P
<jono> skellat, hey
<jono> are you on G+?
<skellat> yes
<jono> skellat, reload the summit page and you should a link to join
<jono> valorie, can you join the hangout?
<jono> Riddell, did you want to join, I sent an invitew
<valorie> how do I join it?
<knome> hello people. are we doing the hangout?
<baizon> yes
<jono> valorie, join https://plus.google.com/hangouts/_/e5b5813205d5c1063626f2001b8e4e51d3fd95ad?authuser=0&hl=en
<ElderDryas> yes jono
<jono> knome, want to join?
<ElderDryas> names and nicks?
<knome> jono, not really.
<jono> knome, np
<knome> jono, i don't want to join G+.
<jono> knome, np
<valorie> there we go
<knome> well, it is a problem to be exact.
<knome> but this is not the time or place to discuss it.
<jono> knome, ok
<knome> who's the one in the middle?
<valorie> shall I put our list of worries on the pad?
<knome> o/
<valorie> or share the google doc
<Mirv> valorie: I think pad'd be better
<tumbleweed> skellat: actually, the monthly discussion got postponed
<Unit193> knome: skellat.
<knome> yeah, i figured that out ;)
<micahg> invite please?
<knome> yay micahg
<micahg> we can't do library transitions in a stable release, there might be an option of using a derived distro to allow for targeted additions while benefiting from the base LTS platform
<knome> jono, can you invite micahg to the session?
<rickspencer3-uds> hi all
<rickspencer3-uds> sorry I am late
<jono> knome, sure
<jono> micahg, https://plus.google.com/hangouts/_/e5b5813205d5c1063626f2001b8e4e51d3fd95ad?authuser=0&hl=en
<micahg> working on it
<rickspencer3-uds> but doing a derived release would have the unfortunate consequence that flavors would have to do all the support for their own archives
<Mirv> jono: change picture to the speaker as well
<knome> rickspencer3-uds, we're not getting much support to keep the xfce stuff up-to-date now either
<knome> Mirv, o/
<yofel> are updates synced from the main archive for derived distros?
<Mirv> knome: \o
<rickspencer3-uds> I can speak to that
<rickspencer3-uds> jono: I'm happy to speak to that if you guys want
<knome> yes, that's good.
<rickspencer3-uds> I'm happy to type or join as you wish
<jono> rickspencer3-uds, https://plus.google.com/hangouts/_/e5b5813205d5c1063626f2001b8e4e51d3fd95ad?authuser=0&hl=en
<knome> the communication was lacking.
<knome> and too late.
<jono> knome, cut him some slack, people make mistakes
<jono> knome, the point is, lets have the discussion
<jono> pointing fingers doesnt help
<knome> i'm not pointing fingers
<knome> i'm saying it would have been more fair to do this transition 6 months later or so
<jono> knome, what transition?
<knome> sorry, the proposal to do the transition
<knome> atm i think we're in a hurry
<Mirv> this is just a subtopic, but there are ~5 ~free software distros for mobile/tablet - Android (+Replicant), Firefox OS, Mer/Sailfish, Ubuntu, Tizen, of which only one is currently released on devices and owns the whole market. Ubuntu and Firefox OS are the closest next ones, Tizen will surely come to alive.
<jono> knome, but this is the point, it is just a proposal - nothing will get implemented unless the time is right
<Mirv> I'd love to see Kubuntu having the product quality Plasma Active release etc
<knome> and it's possible that more bad decisions are going to be made, because we need to make them quick
<micahg> knome: it's not decided when the transition will happen, that's part of what's being discussed ATM
<knome> micahg, yes, in understand that, but see my last comment ^
<jono> knome, the decision will only be made if it is right for the project - but it is important that we have the discussion
<knome> jono, the canonical project or the community project?
<Mirv> (just talking about the culture shift)
<knome> (with no pointing fingers, would just be good if that was communicated clearly)
<jono> knome, they should be the same
<knome> jono, i couldn't agree more.
<jono> I am talking about the shared project, Canonical one part of it
<knome> ok
<jono> lets focus on the proposal and evaluate it's merit
<tumbleweed> a derived distro lets you do new releases of your desktop, on the LTS Ubuntu base
<yofel> again, are updates synced from the main archive for derived distros? If that's a case, I otherwise agree with all points micahg made
<yofel> rickspencer3: make that ~7-9, not all users like to upgrade at release day
<knome> or can
<yofel> but I agree that it doesn't have to be 18 months
<knome> agreed with that
<knome> but isn't the support period virtually a decision for every flavor separately?
<knome> except of course new updates being added
 * balloons pops in
<micahg> knome: no, if Canonical isn't providing security support for the base OS, the flavor support is basically worthless
<tumbleweed> ^ that
<knome> micahg, yes, that's the only drawback.
<knome> right.
<knome> see yofel's comment before on 7-9 months
<GridCube> but if the "archive" is going to a complete different place than all the rest of the developers of desktops...
<knome> is it at all possible that the support time would be any longer than 6mth?
<knome> to support the transition.
<balloons> who would use a 6month supported released?
<tumbleweed> rickspencer3: it's one thing to be striving for that, it's another to say "we're there"
<GridCube> people who would also use a rolling release?
<Mirv> like the kernel is considering "unstable-3.9" kind of thing in parallel
<balloons> if your basing something off a stable supported distro, dropping it after 6-8 months seems a bit off
<micahg> I think most regular users are upgrading shortly after the new release comes out
<Mirv> so to provide both releases and another path for people who want the betas
<micahg> once they're sure that it won't break their system
<knome> micahg, yeah, i'd say that timespan is about 1mth
<GridCube> but you dont
<GridCube> you get it every 6 months, or so, or updates
<balloons> sure.. but i think that not having to upgrade would better serve that type of user, don't you think?
<rickspencer3> hey tumbleweed ... so I worry that if we wait until "we are there" we'll never really commit to being there
<knome> balloons, not update for 2 years? that's a bit harsh.
<balloons> knome, no I mean as opposed to constant 6 month upgrades, just be on rolling and never upgrade really
<micahg> balloons: depends, most people are on regular (interim) releases to get the latest without the risk of a breaking system
<balloons> just stay small constant updates
<balloons> if you want stability, your on the lts.. and it gets point releases to stay up to date
<yofel> balloons: the questions on library transitions etc. haven't been answered there.
<GridCube> i use lts on a machine and update the other, i like to have a stable system and i dont apply updates as they come
<yofel> 2-year only release might make sense for unity
<balloons> just trying to figure out what a really short lifecycle distro buys us
<yofel> it doesn't for KDE
<GridCube> but i could, easily
<knome> nor xfce, i think
<yofel> on the other hand, just supporting a kubuntu release until the next one is out would work
<knome> micahg, feel free to disagree.
<tumbleweed> rickspencer3: we can set ourselves a target of a release cycle to get there, rather than needing to be there today
<balloons> basically, I hate to see us put effort into things and then drop them so quickly
<matzipan_> yofel: 2 year release would probably not be good at the rate of changes in unity right now....
<yofel> if we loose releases, we loose the beta-time integration Q/A time that we currently have to catch all the releases
<yofel> matzipan_: true, but that's again the question on how much changes and possible breakage/regressions a user likes
<matzipan_> well, judging by the way 13.04 went... for me updating from 12.10 to 13.04 in mid february only did good
<yofel> in kubuntu we had too many cases where a late X/Mesa upload in the cycle broke KDE/Kwin on some drivers
<matzipan_> but i'm only talking about vanilla ubuntu
<rickspencer3> hi tumbleweed
<yofel> session: nothing new really
<yofel> matzipan_: sure, but it would be nice to find a compromise that works for everyone
<yofel> I do believe that canonical has the manpower and infrastructure to manage a rolling release. The flavours don't really
<knome> yeah.
<yofel> thanks guys for the session!
<knome> thanks
<matzipan_> meh there should be a middleway for making a snapshot that flavours could possibly use
<balloons> the flavors plan is really interesting.. so in summary (sorry I missed the first part), you don't see a way to do it?
<skellat> yofel: It is on record and Mr. Spencer had an opportunity to participate.  Too much is draft stages right now but what needed to be accomplished was, I think.
<micahg> yofel: I think we can integrate most of the concepts from the rolling release into a new proposal which keeps regular(interim) releases which I'll pen to ubuntu-devel, kinda the best of both world
<micahg> s
<balloons> I've always liked the LTS model for flavors honestly.. i think you can put a lot of value add that way, putting your stuff on top of the lts base
<yofel> micahg: right, thanks for you and rickspencer3 for working that out
<knome> for xubuntu, the "interim" releases have been pretty much the same as LTS
<micahg> rickspencer3: thanks for joining, it was nice to hear your thoughts directly
<rickspencer3> no worried micahg
<micahg> knome: no, with the LTS, Xubuntu was cautious in moving forward with the latest Xfce
<yofel> balloons: kubuntu though primarily focused on the "interim" releases. The LTS is good to have, but not treated really any different from the other releases
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Track: Community | Revamping ubuntu.com/community | Url: http://summit.ubuntu.com/uds-1303/meeting/21676/community-1303-revamping-ubuntu-community-pages/
<knome> micahg, well... yes. but i was referring the the quality
<balloons> yofel, yes, that is true.. and a valid way to do it certainly. you simply support/supported LTS like a normal release.. it wasn't special
<micahg> knome: well, maybe from our work point of view, but I see the core OS as having more quality which improves Xubuntu's quality
<knome> micahg, sure
<balloons> wouldn't you rather support a single stable base you can update over a longer period tho? rather than roll with the new stable's every 6 months?
<yofel> balloons: we do try to keep the LTS updated more than the other release, but that's about it. As for KDE, their release support time is so short, that we really don't need 18month of kubuntu release support
<shadeslayer> ^
<knome> i think a 6 month cadence helps with planning and setting the goals with a smaller team
<shadeslayer> KDE's support cycle is only for 6 months
<micahg> balloons: the problem is if your base is always moving, it's hard to roll it out (think System76)
<yofel> balloons: in fact, as far as upstream goes, kubuntu 12.10 is already unsupported
<balloons> I guess what I'm saying/asking, what's stopping you from staying on 6 month cycles.. but pushing to the LTS base?
<shadeslayer> so it actually helps us to have a 6 month support according to KDE upstream
<balloons> meaning, kubuntu 4.10 on 12.04?
<shadeslayer> s/according to/in accordance with/
<yofel> balloons: at least KDE upstream doesn't like "old" libraries :/
<shadeslayer> ^
<micahg> balloons: we'd lose the ability to work in the archive itself and have to devote resources that could be spent stabilizing the devel release on backporting to the LTS
<tumbleweed> balloons: also, that requires a PPA / dervied distro, and would currently disqualify an Ubuntu flavour
<yofel> balloons: so we would have to take care of many library transitions ourselves possibly
<balloons> yofel, sure, but you could push what you need as part of it.. it would be a big deal to do it
<yofel> it is a BIG deal on the Q/A side
<yofel> we would essentially re-create the beta-freeze time on the LTS every time
<balloons> yofel, hehe.. I know.. it would be big.. the question is, is it bigger/harder than what you do know?
<balloons> *now
<micahg> yofel: as long as the libraries live happily together, a full transition wouldn't be necessary
<Unit193> balloons: Basically, I like to be able to use a computer without fixing it every morning/day, but also able to use new things (like the opus support in VLC)
<yofel> it's not bigger than the regular release, but there everyone works on getting the same things stable
<micahg> Unit193: didn't we get opus support in backports for vlc?
<yofel> so we would have to do more ourselves
<yofel> micahg: ok, that much is true
<balloons> I'm really wondering if it wouldn't be possible
<dholbach> you're out of time - next session starts :)
<Unit193> micahg: I think not, as libopus1 would have to go as well, I the bug report you commented in.
<yofel> heh, sorry dholbach
<Unit193> micahg: I could easily be wrong!
<balloons> I'd like to see some good thoughts around that.. I feel like you could participate in the rolling release and then push it as a point release update to the LTS
<balloons> and keep stability.. QA would be easier in many ways.. but who knows
<balloons> I think it would be possible anyway.. possible.. which is better than completely impossible
<micahg> yofel: anyways, I'm hoping with rickspencer3's support that we can move away from this idea of forking and move towards a shorter regular release that's seamlessly upgradeable to the next release
<yofel> it would be *possible*, but not something we would really like to do
<yofel> micahg++
<ayr_ton> "too many windows"
<ayr_ton> dholbach: \o/
<balloons> yofel, micahg, et la.. thanks for discussing with me
<balloons> I appreciate your insights
<yofel> sure :)
<balloons> to the next session
<dholbach> https://wiki.ubuntu.com/CommunityWebsite
<dholbach> Mockup 2011: http://ubuntuone.com/1vNud7sJ1rRUj5givnTX5q
<dholbach> Jono's announce: http://www.jonobacon.org/2012/12/09/improving-community-getting-involved-documentation/
<tiagoscd|uds_> hey guys :)
<dholbach> https://wiki.ubuntu.com/CommunityWebsite
<dholbach> hey tiagoscd - what to join?
<tiagoscd|uds_> dholbach: sorry, again at work :/
<dholbach> tiagoscd: do we have a link to the canonistack instance?
<dholbach> tiagoscd: nÃ£o hÃ¡ problema!
<mhall119|uds> paste here or in the pad
<philipballew> https://wiki.ubuntu.com/CommunityWebsite
<dholbach> mhall119|uds, want to join in as well?
<tiagoscd|uds_> dholbach: I don't have the link
<dholbach> tiagoscd: ok
<tiagoscd|uds_> I'll try to found it
<tiagoscd> dholbach: it's correct? http://chinstrap.canonical.com
<mhall119|uds> rrnwexec: that's the canonistack I was working on
<mhall119|uds> rrnwexec: http://91.189.93.108/
<mhall119|uds> the plan with this instance was to load it with content, then have IS just copy it all into production
<mhall119|uds> this is a stand-alone site from ubuntu.com
<mhall119|uds> we can manage it fully ourselves
<mhall119|uds> no
<mhall119|uds> technically I'm not working today
<mhall119|uds> if anybody wants access to the WP instance on canonistack, just email me
<kalenjohnson> streeeeetch
<mhall119|uds> QUESTION: Is there a mailing list, irc channel, some other way of keeping up with the work going on?
<kalenjohnson> What needs to be helped with? just content? the website overall?
<dholbach> http://ubuntuone.com/1vNud7sJ1rRUj5givnTX5q
<tiagoscd|uds_> hey guys, I need to go, but I like to say that I'm available to help on page revamping
<tiagoscd|uds_> see you
<dholbach> tiagoscd: thanks a lot!
<mhall119|uds> I can get an example of the design team's personas
<tiagoscd> dholbach: you're welcome. gute nacht :D
<dholbach> tiagoscd, can't remember what "good night" was in  Portuguese :-/
<tiagoscd> dholbach: it's "boa noite"
<tiagoscd> :)
<mhall119> It shouldn't ask, but it should provide paths to get them to the data they likely want
<dholbach> kalenjohnson, both :)
<mhall119> I can provide example personas from the design team
<mhall119> but we'll need to create some community-specific ones
<mhall119> dholbach: those are the personas we need :)
<dholbach> mhall119, hum hum :)
<kalenjohnson> contributing needs to be exciting!
<niemeyer> kalenjohnson: +1
<niemeyer> Knowing what was going behind the scene, I have to say I can't see much to sweat about regarding mir. It's a tricky project, and some people were trying to figure things out.. the decision to take it more seriously was made *now*, and that's why an announcement was made and why the plan is being opened up.
<dholbach> niemeyer, which discussion are you in? is this about ubuntu.com/community?
<niemeyer> LOL
<niemeyer> dholbach: Sorry
<niemeyer> This was about community
<niemeyer> dholbach: Just the wrong community session, sorry
 * dholbach hugs niemeyer
<mhall119> dholbach: we should probably start making work items too
<dholbach> thought so :)
<mhall119> +1 for flat
 * niemeyer hugs dholbach back
<mhall119> lets not block on the design team though, they're going to be very busy
<mhall119> rrnwexec: to a large extent the personas are going to determine what content we need
<mhall119> rrnwexec: ^^
<TadeasParik> there are the local version of the community pages too, our Czech community has these pages done... are there any plans to translate them also into other languages?
 * ayr_ton thinking
<TadeasParik> I mean share this concept with the other LoCo teams...
<mhall119> TadeasParik: Wordpress doesn't really make translation easy
<kalenjohnson> It seems like the focus should be on new user content first, as that seems to be why most users are coming. Once they see if the community wiki is helpful, they will be regular, possibly contribute more...
<kalenjohnson> mhall119, I haven't worked with translations, but I know it can handle it. How easy it is, I don't know...
<mhall119> kalenjohnson: I'm inclined to direct people to loco teams and loco team sites for that
<mhall119> they'll be able to manage it better than we could in one place
<TadeasParik> mhall119, you can create a totally new concept and use another system... not only wordpress... I meant to share this idea with other LoCos...
<mhall119> every other part of ubuntu.com is English
<mhall119> I'm not sure how somebody would find the community site except for going through an english-only page
<kalenjohnson> I would think translations would come from the English pages
<ayr_ton> dholbach: lets create a trello board for review the content
* udsbotu changed the topic of #ubuntu-uds-community-1 to: Currently no events are active in this room - http://summit.ubuntu.com/uds-1303/community-1/ - http://ubottu.com/uds-logs/%23ubuntu-uds-community-1.log
<ayr_ton> o/
