[00:15] <robru> back... everybody ok?
[00:53] <robru> bregma, ok, build is done. went for the publish and the changelog mostly looks good. there is a blank line that shouldn't have been deleted but I can't possibly force a rebuild over such a minor whitespace issue. just need a core dev to ack the packaging then we can publish for real
[00:57] <bfiller> robru: silo-002 tested and ready to be released
[00:57] <robru> bfiller, published, please merge & clean once it hits release
[00:58] <bfiller> robru: will do
[01:27]  * rsalveti waves
[02:39] <robru> alright gents! I'm EOD and I gotta run some errands, but I'll probably be around later; feel free to ping me if you need anything
[04:47] <kgunn> robru: someone merged for me it seems...thank you!
[06:48] <bzoltan> robru: I was pinging you yesterday
[06:49] <robru> bzoltan, yeah sorry for not replying, i did get your message and disable the recipe though
[06:49] <bzoltan> robru: Thanks. Please sync with me whenever you do anything related to the SDK.
[06:50] <bzoltan> robru: I do not know how to merge and clean the silo
[06:50] <robru> bzoltan, well, it's just the staging PPA though, right? isn't the whole point of that that it's a dumping ground to test things?
[06:50] <robru> bzoltan, oh ok, i can do it. it's just a button on the spreadsheet, but if you haven't been trained then you might not have permissions yet
[06:51] <bzoltan> robru: the point is to keep the versions correct and not to conflict with the work others do :)
[06:55] <bzoltan> robru: I need to fully understand the present system and the process of landing things on our trunk. I am not happy that landing stuff on very own trunk takes 2-3 days...
[06:55] <robru> bzoltan, well the big difference with citrain is that stuff isn't supposed to land in trunk until after it's landed in distro. this makes it easier to guarantee that what's in trunk actually reflects what's in the distro.
[06:56] <robru> bzoltan, but really it shouldn't take 2-3 days. merge & clean could have easily happened same day as it was released to distro; i guess either it was overlooked, or you didn't ping the right people at the right time
[06:56] <bzoltan> robru: It causes 30+ pending MRs and a horror of conflicts... the trunk is ours and the direction should be just the opposite
[06:56] <robru> bzoltan, i think there's supposed to be a training session for this on monday. are you in that one?
[06:56] <bzoltan> robru: I do not know
[06:57] <robru> bzoltan, well, that's beyond my control... this decision was made much above me. we are creating this system where "trunk" == "distro". trunk isn't really yours anymore, I guess.
[06:57] <bzoltan> robru: I firmly believe that the direction of integration should be Modul -> Product and not Product -> Modul
[06:58] <robru> bzoltan, take it up with didrocks I guess. not my call
[06:58] <bzoltan> robru: then we might create an other project or an other branch and keep the "distro" trunk only for releasing
[07:00] <bzoltan> robru: I am not sure if I have the energy and time to fight :) for it ... I think we can resolve this issue without conflicts. We need an internal integration point. So far it was the trunk ... now we do not have one. I guess I need to make one.
[07:00] <robru> bzoltan, well that seems reasonable to me... i dunno what to say dude. I am upstream for friends-app, and I always have half a dozen small feature branches that occasionally get released to distro first, then merged to trunk. it's a pretty slick workflow that's been working well for me for a couple weeks.
[07:02] <robru> the silos are particularly amazing for testing. I used to have such a hassle compiling arm packages for my device... I remember installing compilers on my mako and just building packages there... it was such a nightmare... but no more! Now I can just dump MPs into a silo, and then soon after I can enable a PPA on my phone and install built packages and test them easily. it's brilliant.
[07:03] <bzoltan> robru:  I guess it is not fair  to compare an app with the whole UI Toolkit :)
[07:04] <bzoltan> robru: in the SDK we have like 4 PPAs ... Silos are just yet an other PPA for me. Not a great discovery ... I do staged testing for ages
[07:04] <robru> bzoltan, i don't really see the difference... in both cases you need to test on different platforms, in both cases there's a combination of manual and automatic tests to do... having a PPA that just magically has all your MPs built in is great
[07:05] <bzoltan> robru:  how the Silo contains all the MRs?
[07:05] <robru> bzoltan, but the 'great discovery' is that now there's a tool that does the builds for you... you don't have to manually build packages or manually upload to PPA anymore.
[07:05] <bzoltan> Each MR has own PPA?
[07:05] <bzoltan> robru:  we never need to build manually ... .deb files are in the MR
[07:05] <robru> bzoltan, no, when you have a stack of MRs you want to merge, you list them all on the spreadsheet, and then the citrain will grab all those MRs and build them all into one PPA for you
[07:06] <bzoltan> robru: and we never manually upload to PPAs
[07:06] <robru> bzoltan, i don't know what you're talking about... citrain introduced auto PPA builds for MRs. I never heard of anybody doing this with any other tools prior.
[07:09] <robru> bzoltan, so anyway, it's totaly out of my hands... take it up with didrocks if you want to (try to) opt out of citrain... but I personally wouldn't, it's the slickest release process I've ever seen. we just had a couple hiccups because it's so new, but there's just tons of potential here. it's only gonna get better.
[07:17]  * robru --> sleepytime ;-)
[08:04] <bzoltan> robru: I definitely do not want to opt out the UITK from the CI process! I love CI train! For real, no kidding. I just do not like the idea that we can not land our merge requests to the trunk of our projects without a massive manual procedure what takes at the best case 2-3 hours manual work.