#metabrainz

chirlu: did you commit that change?

bitmap: you about?

hm, so the latest data dump is in the new schema version?

that one is

thanks, I'll give it a try

k

chirlu, bitmap, Gentlecat: ping.

pong

I want to commit the search path fix and update the tag.

do I commit it to master? or a branch?

pong

Just merge the pull request I opened a minute ago.

(To production.)

ohh, perfect. thanks!

merged.

can you please also update the tag?

It may be too late to update the tag. We’ll need a new one, probably.

too late?

Too many people may already have downloaded it.

we have not made it public yet.

Yes, it was in the public repo.

but simon didn't say GO. :)

then make a git checkout v-2016-05-23-schema-change-v2 tag?

Something like that, yes. But only bitmap will be able to sign it properly.

oh.

crap.

ohhhh bitmap!

when. will. this. schema. change. die?

When does he land? :)

does MB really need signed tags? :)

what do you mean by sign?

he already landed in JFK, not sure when his connecting flight is.

Gentlecat: PGP

Cryptographically signed.

do we have some special key for those?

fwiw: I'd also like "new releases from your area more than *events* (though, https://i.imgur.com/c7NJRa2.gif)

ugh jfk

:(

wb bitmap.

\o/ bitmap

The keymaster!

bitmap: did they let you back in?

we found one small problem with the schema change branch. chirlu fixed it.

but we need to set a new tag to reflect the change

Gentlecat: yeah, they finally decided I was a legit citizen

what do I have to to do?

ruaok: I have a bit of feedback for the postmortem blog post. ping me when you have time to hear it

CatQuest: right now, the regular onsite font changes depending which operating system you use and which fonts you have installed :)

I hope that didn't take long 👍

oh, push a new tag. ok

cd313835c0

is the commit.

alastairp: whatchagot?

the key for doing this is in syswiki btw

lets hear em.

ah, good to knwo

but you'll have to wrestle with gpg for $long_duration

bitmap: ah, good to know

ruaok: may 24, there were 2 problems? shmmax values which had to be reset, and the postgres extension that wasn't set up properly?

not sure if you want to make those 2 things separate? it kind of sounds like there's only 1

[17:49] <LordSputnik> gcilou: chirlu: kepstin: I'm not even sure having other projects on the MB homepage makes sense. Linking to just MeB to allow people to discover that appeals to me more

+1

ok, tag updated in the blog post.

any reason not to hit publish on that?

chirlu?

Missing thank-you section. :)

what else?

Yes, some "part of the MetaBrainz family" line in header/footer/homepage is fine. explicit links to other brainz i wouldn't like as much

im working on another layout now

In the release post, nothing else I think.

kepstin: it's basically the same on every machine i have.. I think it's basically verdana

yeah, it's probably common to see verdana on most machines

who needs thanking? I've got Bitmap, Gentlecat, Zas, Chirlu so far.

i like verdana

Tickets were resolved by bitmap, Gentlecat, me, reosarevok and gcilou.

but on my linux boxes, depending on config, I'll get bitstream vera sans (or dejavu as a substitute) isntead

lol majorlurker and myself did soem hottesting ?

but mostly it was you guys doing awesome.

on a mac without ms office installed, you might get helvetica.

ruaok: ruaok too, I guess. ;-)

this mac has never seen an ms office. but i think i manually verdana'd it. i liek verdana

and tahoma too actually

arial is sooo old

(inbefore comic sans joke)

tahoma was kind of a neat font. It was the default system font on windows 2000, which was my favourite windows :)

the problem with is is that it doesn't have a bold or italic version.

ya. :(

Verdana is too squashed. It's been sat on

gcilou: you oppinion

your*

:)

gcilou: you'll want to think about how the layout will adapt to smaller screens or even cell phones.

> We would like to thank Bitmap, Gentlecat, Zas, Chirlu, Reosarevok, Gcilou for contributing directly to the release and we'd also like to thank all of the people who helped test, debug or otherwise offer support in this quite difficult release. Thank you!

yay nay?

\o/

s/Chirlu/chirlu/ ;-) But I can do it myself after publishing.

tho it's weird to see those who's nicks are lowercase be upper case

ya

Project musicbrainz-server_master build #411: SUCCESS in 19 min: https://ci.metabrainz.org/job/musicbrainz-serve...

working on a mockup like dis https://usercontent.irccloud-cdn.com/file/HhDnv...

I'd say that is "people intent" :D

gcilou: too wide :D als owhat is that in the upper rightmost corner?

(several corners ot the right. i know)

:D

I just screenshotted my screen, it's a label that says store for the web tool

akkurat :D

anyway my + is going for list not map

why not? lol, no it's not part of the design

there can be an "events in your area" subpage of the homepage (that you get to by clicking "more..." which has a map, and which can explain loosly how to get events Near you ™)

Gentlecat: Upper or lower case? :)

etc

keep it upper :)

camel case

could somebody on pg 9.5 give me an example of some entries from the deleted_entity table in the pg_dump format?

hi luks!

I'm wondering if I can fake it and make the column text, or I really need upgrade to 9.5

hi! :)

\o/

more like CamelCase

I’d guess you can text it.

alastairp: the shmmax thing turned out not to be a problem, really.

ruaok: right. so is that what #postgresql helped you with?

chirlu: I've seen '{fooo}':jsonb in the docs, which wouldn't work

there were lots of little problems, and I didn't list all of them.

also right now this thing has like 3 columns. thats.. very busy

er, ::jsonb

(I wasn't following, I don't know if they also helped with the crashy extension)

the extension tip is what they helped with.

yeah, that's what I kind of understood

ugh i need go make dinner

so,then I think it is fine as is, no?

yeah, I guess

chirlu: any comments on the what happened blog post?

and about the replication change, I wonder if it's worth explicitly linking to what went wrong

Yes, I think the sequence of events is not quite right in the same region that alastairp means. :)

the "there was a bug in some code we use" sounds very hand-wavy