for beta, in LB we just deploy the commit so doesn't make any difference i think.
2021-04-06 09616, 2021
alastairp
mmm, maybe we're mis-understanding
2021-04-06 09623, 2021
alastairp
I mean to make a beta release of BU 2.0
2021-04-06 09646, 2021
_lucifer
ah ok!
2021-04-06 09653, 2021
alastairp
so that we can set a tag in requirements.txt of LB for a pr or to make a test deploy
2021-04-06 09629, 2021
_lucifer
sure let's do a beta release
2021-04-06 09633, 2021
alastairp
great
2021-04-06 09655, 2021
alastairp
I need to look at your comment on #61, and I also added some feedback to #58
2021-04-06 09603, 2021
_lucifer
yes, i agree with the feedback on 58.
2021-04-06 09636, 2021
_lucifer
there are multiple other changes some we already discussed earlier today that we should do in 2.0.
2021-04-06 09653, 2021
sumedh joined the channel
2021-04-06 09628, 2021
CardinalWolseley joined the channel
2021-04-06 09655, 2021
alastairp
yeah
2021-04-06 09600, 2021
_lucifer
plus now that we are breaking compatibility let's go through the entire BU code base once to see if there are some more backward incompatible change we like
2021-04-06 09607, 2021
alastairp
and the ones that I mentioned on the PR that removed the namespace versions
2021-04-06 09613, 2021
alastairp
yeah, good idea
2021-04-06 09624, 2021
alastairp
maybe iliekcomputers can get on board with this plan too
2021-04-06 09642, 2021
_lucifer
yup good idea
2021-04-06 09607, 2021
_lucifer
for the separate branch name, v1.18 sounds good?
2021-04-06 09616, 2021
_lucifer
or maybe python2 is more apt?
2021-04-06 09640, 2021
alastairp
let's use the version number
2021-04-06 09647, 2021
alastairp
yes, v1.18
2021-04-06 09647, 2021
_lucifer
š
2021-04-06 09620, 2021
_lucifer
alastairp, can you take a look at BU permissions? I am getting 403 while pushing to it.
2021-04-06 09631, 2021
_lucifer
*BU github permissions
2021-04-06 09631, 2021
alastairp
I invited coreteam to be admin on BU. You should have full access now
not urgent. but we should hash out how this should work, based on some of the feedback we've already gotten about how to deal with reported.
2021-04-06 09641, 2021
ruaok
sadly, it isn't actionable and has too many open questions, but thanks. :)
2021-04-06 09611, 2021
alastairp
yeah, but it's already 1000x better than if it just had the title and "implement this please" as the body
2021-04-06 09643, 2021
ruaok
given our limited community moderation ability, I think we should examine ways in which we can enage our community to help while not violating our privacy policy.
2021-04-06 09612, 2021
alastairp
I opened a bunch of tickets today and tried to add in as much detail as possible, because I find that often we think of great ideas when talking among ourselves but by the time we get to implementing it I've forgotten everything we discussed
2021-04-06 09626, 2021
ruaok nods
2021-04-06 09633, 2021
alastairp
yeah, agreed. so reporting is good, but addressing the reports can be more difficult
2021-04-06 09643, 2021
ruaok
over lunch a pile of things I wished to see about this feature became clear, so I wanted to jot them down.
2021-04-06 09608, 2021
ruaok
and hopefully avoid the drama around the metrics feature, lol.
2021-04-06 09617, 2021
alastairp
:( yeah
2021-04-06 09603, 2021
alastairp
btw, current priority list for me is 1) consul startup improvements over all projects, 2) metrics
2021-04-06 09651, 2021
ruaok
3) real features, regardless of which project ?
2021-04-06 09606, 2021
alastairp
1) consul startup, 1) metrics, 1) real features
2021-04-06 09625, 2021
alastairp
speaking of adding detail to tickets, _lucifer: I'm adding some stuff to LB-849. again, it's good to have the ticket but better to have some details about the discussion that we had
