[02:12] Unit193, look good to you? https://bugs.launchpad.net/ubuntu/+source/xfce4-notifyd/+bug/1668821 [02:12] Launchpad bug 1668821 in xfce4-notifyd (Ubuntu) "[FFe] xfce4-notifyd 0.3.5 for zesty" [Undecided,New] [02:23] Sure, perhaps get someone from studio to ACK. [02:28] Seemingly lubuntu as well [02:28] Eh.. [02:28] -SwissBot:#xubuntu-devel- ::xubuntu-artwork:: [shimmer-themes-debian] r18 Update packaging for Numix theme (by Sean Davis) [02:29] Who are our normal contacts for those now? [02:29] wxl, krytarik, sakrecoer: ↑ [02:31] thanks [02:31] going to wander off for a bit now [02:31] Cool, have fun. [08:07] ochosi: built gtk3 panel in vm - using default panel location I *do* see the panel flicker you talk of - but I need to be almost out of the top of the panel to trigger it - also confirm there not being able to move plugins [08:09] * flocculant normally has panel in bottom left corner - shrunk down to 1 pixel auto resize [08:26] you must have wondered how I wasn't see something so pronounced ;) [09:22] flocculant: ok, it's just one more (minor) thing i have to fix [10:12] cyphermox: I don't suppose you'll be doing a late devscripts merge? :> Some delta has been fixed upstream. [12:20] flocculant, akxwi-dave, wxl, sakrecoer, if you would like to review https://bugs.launchpad.net/ubuntu/+source/xfce4-notifyd/+bug/1668821 and potentially ack it for zesty :) [12:20] Launchpad bug 1668821 in xfce4-notifyd (Ubuntu) "[FFe] xfce4-notifyd 0.3.5 for zesty" [Undecided,New] [12:22] bluesabre: done by me [12:23] suppose I'll go ahead and sub -release [12:23] best to I guess :) [12:24] oh [12:24] Unit193 already did [12:24] sneaky :p [12:24] you only look a bit silly :) [12:24] * bluesabre is happy with his dev team [12:24] :D [12:29] * flocculant thinks he should install any gtk3 stuffs in the vm [14:47] Hi everyone, I would like to help out with Xubuntu development. I'm thinking QA testing to start. Could someone help get me setup to do so? [14:49] hello Perigee, the best place for you to start is to have a read at the QA section of the Xubuntu contributors documentation: http://docs.xubuntu.org/contributors/qa-tester.html [14:49] hi Perigee - quick first question [14:49] flocculant: Shoot [14:50] Perigee: can you test on hardware - running the dev version (which is pretty much completely stable now) or do you intend to test thing in a vm? [14:51] this late in the cycle - I'd prefer people who are brave enough to do some real world testing :) [14:51] I can do either. I have a few different laptops I can test on, and at least one desktop, maybe two [14:51] awesome [14:52] so best way to start is grab the daily and install that - we have a few official ppa's we use to [14:53] ok, what do I need to do about the ppa's? [14:53] for a bit more detail - you can look at the dev docs which slickymasterWork posted (there are actually 3 'tester' chapters - first one deals with setting up [14:53] Ok will do [14:53] http://docs.xubuntu.org/contributors/ chapters - 4 to 6 [14:54] I'm pretty much around for a few hours now - akxwi-dave is the other qa lead - so either of us will be able to help with specifics - anyone is likely to help with less specific stuff [14:55] Great, I'll read through that and get the basics setup. [14:55] okey doke [14:58] Perigee: dual booting is a useful half-way - I kind of do that - if dual booting can be used to describe having 6 options :D [15:00] flocculant: Been there myself with the hexabooting at times. :) I remember back in my Gentoo days (2004 era or so) I had a huge list... just trying to get things to work [15:01] :) [15:01] good choice of word there too :D [15:09] Unit193: what would it bring us? I'm not sure it's that big of a deal... [15:11] Unit193: tbf, before looking at the merge, we should fix that issue with the autopkgtests not passing on some architectures [15:11] (because otherwise it wouldn't transition anyway) === Zren_ is now known as Zren [16:27] knome akxwi-dave - updating of http://xubuntu.org/contribute/qa at https://xubuntu.org/?p=4279&preview=true [16:28] knome: 5 attempts to login today before I had more than my profile - really must talk to IS about that :p [16:33] hmmh [16:33] right [16:34] that's weirdish [16:34] i'll try to debug it with you later today to see if $something helps [16:34] aah ok [16:34] but it's not "much" i can do [16:35] and i believe there's not much more IS can do... [16:35] well [16:35] it worked first time before [16:35] so 'something' has changed :D [16:36] heh [16:36] maybe [16:36] anyway, coffee time, bbl [16:36] :) [16:54] flocculant: I've gone through the doc chapters, signed up for the various resources. I just got a VM running the daily ISO + PPA's. Is there a rigid testing regimen that needs to happen each day/week and be reported somewhere as success/failure? I understand the bug reporting aspect. [16:54] mmm coffee [16:59] Perigee: http://iso.qa.ubuntu.com/qatracker/milestones/369/builds alphabetical - right at the bottom [17:00] the only thing we do specifically is iso testing this cycle [17:00] sometimes we do package testing - mostly when dev wants something testing or it's lts cycle [17:01] hi genii :) [17:03] flocculant: Ok I see now. Is that what I should focus on then? Running those test procedures for the various ISO's and reporting via the tracker there? (On various hardware of course) [17:03] flocculant: Salutations [17:04] Perigee: to be honest - the greatest value for 'me' is people that run the dev version daily in use [17:04] much of the iso stuff is common - so if there's an issue - it would be *buntu not just us [17:05] particular things like lock breaking are issues we keep seeing - but that's not likely to break again this cycle [17:05] flocculant: Got it, and doing that throughout my day would be reported just with bug reports if any are found, right? [17:05] yup - though check for dupes first [17:05] flocculant: Ok then, makes sense. [17:05] Perigee: and check upstream https://bugzilla.xfce.org/ too [17:06] could be it's reported there and not on lp [17:07] I tend to find issues just doing what I do normally ... 'mmm that didn't do that last week' [17:07] Ok, I'll certainly get my main laptop running the daily [17:08] Perigee: that would be great :) [17:11] Perigee: this late in the cycle little is going to change - and oops moments are unlikely [17:11] flocculant: Ok, you should see me on the Launchpad team and elsewhere in Ubuntu-land as "crouthamela / Andrew Crouthamel". [17:12] if you stick around (which I hope) starting using the dev cycle on release+ 1 day like I do can see a few hiccups - hence the multi-boot scenario but rarely am I more than a short while outside [17:12] ok cool - nice to meet you :) [17:13] :) [17:14] but to be honest - the times that packages landing completely breaking are few now - changes in the way packages land and testing by canonical are different than they were I believe [17:14] So they're more careful now? [17:14] seems so [17:15] there have been several instances where uploading after freezes have been made much "harder" (for justified reasons), and i think this has started paying off [17:15] well - not perhaps careful, but proposed is usually disabled - you could break your system more often by using that repo if you wanted too [17:15] knome: ack [17:15] so developers aren't maybe any more careful, but the archive admins and release team are more cautious about late uploads ;) [17:16] ahh [17:16] I think in the last couple of cycles - lock has been problematic - but not unusable [17:16] more likely to see issues actually during install than anything else [19:29] flocculant, around? [19:33] slickymaster, around? [19:36] knome: yea [19:36] for a while - then bbl [19:36] oh [19:36] give me 5 mins [19:37] actually - bbl later noq, was waiting for M to return :) [19:37] hey guys [19:37] heh [19:37] hello chatter29 [19:38] allah is doing [19:38] flocculant, ok, so look at https://temp.knome.fi/xubuntu/contributor-docs/contributor/C/ [19:38] flocculant, does the QA ToC structure make sense like this? [19:39] flocculant, and: would you rather see even more subsection titles there (under testing infra etc.) or is this good enough? [19:45] :-) that looks good knome [19:46] oh obviously akxwi-dave needs to ack too [19:46] ok, i'll look into getting things sorted so that the different subsections can still have their own pages but appear as subitems like this [19:46] actually it [19:46] it what? :) [19:47] looks really good [19:47] heh, ok, good good [19:47] i'm planning to land some more stuff on documentation, likely also subsections, so need to do this in order to keep things clean [19:47] and evenin [19:47] hullo hullo! [19:51] ahh great, incremental config for contributors <3 [21:24] knome: yea - as akxwi-dave says looks good [21:31] now to beat docbook as long as it does what i want... [21:31] * flocculant hands knome the beating stick [21:31] i have my hammer out... [21:31] possibbly too much :p [21:32] nah [21:32] i might need bigger tools [21:36] cyphermox: And ah fun. Didn't see anything that'd fix the gpg2 fun. [21:38] knome: as far as subsections goes - the fewer the better imo [21:40] mhm [21:40] i've almost got what i want... [21:40] but not quite [21:41] :) [21:43] hmph. [21:43] now i'm at least getting the subsections i want printed [21:44] (and nothing more) [21:47] how important do you think it is to be able to get the subsections into separate pages? [21:47] to print? [21:48] like, http://docs.xubuntu.org/contributors/qa-testing.html [21:48] oh you mean like when dev finishes and docs starts? I'd ay quite [21:48] nope, the subsections of *qa* [21:49] i understand this will be quite a long page if they are all in one... [21:49] basically, whole qa stuff would appear on one html page [21:49] mmm - better if they do - but *I* would be more likely to print the whole of it - others maybe not [21:49] i'll look into it then [21:55] am now, knome :) [21:55] evening all [21:55] oki [21:55] so basically see the discussion with flocculant aboce [21:55] above too [21:55] already saw [21:56] and I do agree with flocculant [21:56] above too [21:56] hmm, oops [21:56] regarding avoiding large html pages [21:57] and do +1 your subsections idea, knome [21:59] hmm, so every sect1 should be a chunk... [22:00] not sure I understand what you mean, knome [22:01] to what do you refer by sect1? [22:01] you don't have to [22:01] i'm just saying it aloud for my personal reference later :P [22:01] lol [22:02] knome: not sure how the sub-sectioning is working but Dispute Resolution on strategy should be a section - not sub-section of development [22:02] unless we think dev cause all the issues :p [22:02] well that's a content issue, not a technical one [22:03] i'm mostly poking the technical stuff today [22:03] assumed as much - just making sure now rather than in 6 months :D [22:04] actually i think the issue is just that "Development" is a clumsy section title; it should be more like "contributing" or sth [22:04] because if you look at the content/context, it all is general for everything, not just code contributions [22:06] or communication - cos that's what the majority is about - then sub-section comms would need another name [22:07] bluesabre: did I say that seek in parole was a bit broken? [22:10] knome: next time I'm trying to login to x.org I'll grab utc time too - then I'll go see IS and report it - having an actual time should help [22:10] in the meantime - I'm off - night all [22:10] night flocculant [22:24] Unit193: if there's something you need though, it's a different story [22:34] because if you look at the content/context, it all is general for everything, not just code contributions [22:34] cyphermox: Better handling of buildinfo files (for when one is building Debian packages) and git-deborig looked interesting, but not enough for you to drop everything else for 'em. [22:35] oops again [22:35] i'll move the irc window elsewhere...