lmk if I should look into it, I plan to include this in the blog instructions today
CatQuest
bleh. I wish we had a separate proj. for bookbrainz(style)
since we have a separate style for mb, doesnt that make sense?
reosarevok
I guess it would make sense once there's a community to use it :D
CatQuest
it'd make sense now cause it'd be easier for devs to look at open ticket list and not need to filre out "style" tickets
i mean i guess
ruaok
alastairp: let's do it tomorrow, shall we?
CatQuest
(I also feel dodgy about creating "style" tickets now)
tere are already several
reosarevok
I mean, right now style is also run by the devs :)
So they should see both, no?
CatQuest
exactly
yeh. i guess
reosarevok
Until they have a separate process for that
CatQuest
but also i feel most style tickets will be moot once site is up and out of alpha-beta
alastairp
ruaok: fine by me
CatQuest
reosarevok: i fig i'm part of this "they" in your sentence .. idk?
reosarevok
Well, I expect the BB team will want (with the input of the community, which nowadays is probably mostly you :p) to select a way to do style stuff
Whether it is "all goes to a vote" or "the dev team chooses" or something else :)
CatQuest
i have a ticket up like that already infact :D
I fear i am slowly fixing myself up to become "style-dude of bb" wich is.. a lot of work? :DDD
yvanzo
bitmap: Yes, I'm reworking Dockerfile a bit at the same time.
ruaok
alastairp: as we wait for things to happen today during the downtime, I'll try some artist histogram scripts on timescale. curious to see how long that would take.
alastairp
oh yeah, it'll be interesting to see how long these types of aggregate/stats queries will take to run
bitmap
yvanzo: maybe the Dockerfile rework can wait until after? :) or will it be ready by the time the upgrade is done?
yvanzo
bitmap: it is, will push it.
bitmap
thx
yvanzo
(just needed to test it locally to be safe)
bitmap: btw, should we draft some blog posts already?
bitmap
just didn't want to have to tell people to checkout some pr in the blog
I'm working on the upgrade instructions one already
should be ready for review soon
yvanzo
bitmap: will musicbrainz-server be tagged v-2020-05-18-postgres12 (as we use to prefix noticeable release like schema change)?
(or -pg12 or nothing)
bitmap
we could do that
-postgres12 worksforme
yvanzo
+1
will use that in musicbrainz-docker then
bitmap
yep, I"m updating references in the blog to use v-2020-05-18-postgres12
cloverfield has quit
cloverfield joined the channel
bitmap wonders if there's a "non-inline" code block in wordpress or any way to change the font
nvm I figured out how to switch to the code editor
reosarevok
Tweeted, set banner
bitmap
I started a barman backup of floyd about 20 mins ago
ishaanshah[m]
iliekcomputers: I couldn't get the spark tests done, I will do that first thing tomorrow
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | GSoC students start here: https://bit.ly/2NUaxgb | Channel is logged; see https://musicbrainz.org/doc/IRC for details | Meeting agenda (today is "schema change" day, might not be a meeting—stay tuned!): Reviews, 2 accounts 1 email (reo)
c1e0_ joined the channel
v6lur_ joined the channel
reosarevok
bitmap: are we already stopping the cron jobs etc?
bitmap
yvanzo: I have a rough draft of the upgrade instructions blog post. the docker section could probably use some help
reosarevok: yup, doing that now
reosarevok
Ok, just strikethrough what is done on the gdoc I guess :)
(why the hell did they make strikethrough so complicated - alt shift 5, wtf? :D )
