IRC logs for #baserock for Sunday, 2015-05-10

*** zoli__ has joined #baserock02:14
*** zoli__ has quit IRC02:19
*** edcragg has quit IRC02:40
*** inara` has quit IRC02:43
*** inara has joined #baserock02:45
*** pacon has joined #baserock06:10
*** zoli__ has joined #baserock06:21
*** pacon has quit IRC07:30
*** zoli__ has quit IRC08:13
*** pacon has joined #baserock09:15
*** edcragg has joined #baserock09:43
pedroalvarezLooks like it wasn't a good idea to upgrade morph in mason after the release10:36
*** zoli__ has joined #baserock11:14
*** zoli__ has quit IRC11:20
*** pacon has quit IRC12:27
*** rdale has joined #baserock17:56
*** zoli__ has joined #baserock18:41
*** edcragg has quit IRC20:25
persiapedroalvarez: Hrm?  If it wasn't a good idea to upgrade the morph in Mason, does that mean it wasn't really safe to upgrade morph for release?22:13
*** zoli__ has quit IRC22:15
ratmice__yeah i wasn't sure the implications either, e.g. is the thought that you should upgrade mason immediately prior to release, fix any potential issues then release?23:07
pedroalvarezpersia: nothing to worry about, I believe. But seems like there are some problems with the mason script with new versions of Morph23:08
persiaAh, so it is just a case of Mason bitrotting, rather than morph being bad.  Thanks for releiving my worry :)23:09
pedroalvarezIt doesn't wait for the build before start deploying..23:10
pedroalvarezNot sure what is going on, maybe a bisect will help23:10
pedroalvarezratmice__: some of us have local instances of mason to test changes on Morph. We don't want to use the public ones to "play"  though.23:12
persiaNot playing with production is a good idea, but perhaps we need a better staging area?23:13
pedroalvarezAlso, they are really useful to populate cache servers with development branch artifacts  :)23:14
persiai.e. some way to try Mason against something not yet landed, so see the effects of a change, and so avoid issues.23:14
*** zoli__ has joined #baserock23:16
ratmice__pedroalvarez: didn't intend to imply playing, or even random development, but a process in which if updating mason works, the release can go ahead unchaged, or if it fails it can be postponed or morph/mason fixed before the release goes live23:16
pedroalvarezA special Mason that check for Morph changes, and if there are any, upgrade its version and kick a build23:17
pedroalvarezI guess we will have some discussion about it this week23:19
pedroalvarezratmice__: that makes sense23:21
*** zoli__ has quit IRC23:21

Generated by 2.15.3 by Marius Gedminas - find it at!