frankban | lazyPower: how do I push updates to the redis branch to the promulgated location? (bzr+ssh://bazaar.launchpad.net/+branch/charms/trusty/redis) I am getting "readonly transport" errors | 11:58 |
---|---|---|
lazyPower | frankban: ah, it wasn't promulgated to a namespace you can do that to. it lives in ~charmers. | 11:59 |
lazyPower | anythign that lives in ~charmers still gates through us. :-/ i should have asked if you needed it promulgated in another namespace | 11:59 |
rick_h_ | lazyPower: we've got our namespace under ~juju-gui-charmers. Can we do that withuot breaking things? | 12:00 |
frankban | lazyPower: I have no problem in asking you to merge changes each time, but maybe it would be more practical to have our own promulgated location, like for the juju-gui charm | 12:01 |
lazyPower | i agree, i dont want to gate every one of your commits | 12:01 |
lazyPower | because #lazy | 12:01 |
frankban | :-) | 12:01 |
rick_h_ | lazyPower: we'd like to be able to push as we're working with arosales_ to help take some charm review/management burden off your folks so this doesn't seem to help at all. | 12:01 |
lazyPower | I can move it over there, i'm not sure about the breaking of the existing alias though | 12:01 |
lazyPower | I need to defer until i can ask marcoceppi about this, as its the first time i've ahd to move a charm. I know its possible i just forget the process | 12:02 |
rick_h_ | lazyPower: rgr | 12:02 |
lazyPower | will circle back once I've got instructions. | 12:02 |
frankban | lazyPower: np thanks | 12:02 |
=== kadams54_ is now known as kadams54 | ||
=== hazmat_ is now known as hazmat | ||
=== perrito667 is now known as perrito666 | ||
=== arosales__ is now known as arosales | ||
arosales | lazyPower, is this a case where a branch needs to be made? | 15:13 |
lazyPower | arosales: they have an org/namespace in launchpad already. I need to unpromulgate the ~charmer branch and repromulgate to point @ the juju-gui org as the recommended branch | 15:42 |
arosales | lazyPower, ok | 15:43 |
rick_h_ | lazyPower: ~juju-gui-peeps to be official | 15:49 |
rick_h_ | sorry, ~juju-gui-charmers | 15:49 |
rick_h_ | even I can't keep the damn teams straight | 15:49 |
lazyPower | mmhmm | 15:52 |
lazyPower | and its only goign to get worse from here | 15:52 |
jcastro | rick_h_: ping | 17:56 |
jcastro | rick_h_: hey so, you guys didn't deploy the new community page today? | 17:56 |
rick_h_ | jcastro: working on it | 17:57 |
jcastro | ah ok | 17:57 |
rick_h_ | jcastro: kadams is having fun building the release as we speak | 17:57 |
jcastro | rick_h_: what's the tldr, business as usual or explosions? | 17:57 |
rick_h_ | jcastro: but the release is getting together | 17:57 |
rick_h_ | jcastro: his machine out of memory? | 17:57 |
jcastro | rick_h_: but mostly, he got you everything you need right? | 17:57 |
jcastro | he being luca | 17:57 |
rick_h_ | jcastro: yes, we've got the new page and the videos page in there for release | 17:58 |
jcastro | ooh, the videos page made it too? hell yes. | 17:58 |
jcastro | rick_h_: ok, so I'll probably start round 1 of bug reporting on it tomorrow. | 17:59 |
jcastro | rick_h_: about how often do you guys deploy a new version? | 17:59 |
rick_h_ | jcastro: 2wks | 17:59 |
jcastro | just wondering what my cadence to landing things should be | 17:59 |
jcastro | oh ok, perfect | 17:59 |
rick_h_ | jcastro: is the normal target, the issue tracker has the next milestone setup | 17:59 |
jcastro | ack | 17:59 |
jcastro | rick_h_: one more thing then I'll shut up, `juju publish` still on for august ish? | 18:03 |
rick_h_ | jcastro: not sure atm. | 18:03 |
jcastro | aww man, you just cost me a bet | 18:04 |
rick_h_ | jcastro: ruh roh | 18:06 |
rick_h_ | jcastro: if it helps it's possible and I recruited lazyPower to help test it out :) | 18:06 |
rick_h_ | jcastro: but I'm not sure it'll be 100% out for all users next month | 18:06 |
rick_h_ | it'll probably be in some form of beta still for select folks | 18:07 |
jcastro | I was like "hey guys, no need to be pessimistic, you know rick is ON IT." | 18:07 |
lazyPower | o/ | 18:07 |
jcastro | hey | 18:07 |
jcastro | will the branches under /charms/ still ingest automatically even when publish rolls out? | 18:07 |
rick_h_ | jcastro: no, the goal is that publish shuts off ingestion all together. It's causing too many problems | 18:08 |
rick_h_ | jcastro: scripts that want to upload can do so via the api clients we've got | 18:08 |
rick_h_ | jcastro: but no automatic pulling from anywhere, user focused interaction or bust. | 18:08 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!