#metabrainz

since the problem with a database that is managed by the users device itself, it makes sense there must a condition on which the migration would trigger

Ahh got it here every user has a copy so every time it has to get triggered

Yup

migrations take place at every app start

Thanks a lot.. will update it

So if I have 5-6 migrations than all those classes with appropriate conditionals right..

yes

Damn.. ok thanks 🙏

By the way could u also review my PR whenever u have time thanks

you can also enclose a variable inside the migration object itself btw

and do if else in kotlin

would result in same thing

just make sure the object is const

Ohk alright I’ll do that thanks

bitmap: the endpoint looks great, thanks!

<13Max (Maxr1998)> pranav: Room migrations usually expect a static from and to schema. So, if you change anything, you increase the version number. Thus, you don't have checks inside your migrations. That's pretty annoying during development but definitely the way to go for production. It also makes sense to export the schemas into the repo (as a JSON file), then you easily notice if something changes.

👍

Ahh thanks a ton Max that makes a lot of sense.. coz this method would be too tedious for multiple migrations..

lucifer: looks like eur might be supported by stripe now. Let see if I can get that setup later.

Would be happy to discuss things and receive Feedback n suggestions!

Spammed all the channels ig ;) sorry for this

Hi outsidecontext (IRC) , I have posted my proposal for GSoC on the Discourse. Your feedback would be valuable.

hi yellowhatpro: here are some comments to your second draft https://www.irccloud.com/pastebin/smv2fuvT/yell...

yellowhatpro: please consider posting on community forums instead, see https://wiki.musicbrainz.org/Development/Summer...

yellowhatpro: yes the archiver can have different running modes to select different inputs.

null_hawk[m]: Thanks a lot. I will review and give feedback. But currently I'm drowning in work related stuff and tomorrow I'll be traveling the whole day. I'll see that I can answer afterwards.

outsidecontext: Sure 😊

Hello! I am currently working on implementing i18n on BookBrainz as my summer of code project and needed some help..

I researched on whats the best way to maintain continuous translations in a big codebase and found two approaches

1) build two locales folder - one for the devs to work on and push new translation keys and another for the website and translators to acess

2) get a seperate translation branch for the devs and translators to work on whihch will be pushed into the main code periodically(the approach MB currently uses)

I wanted to know why MB is using the approach 2 and why is it better. Also reasoning on why approach 1 isn't suitable would be appreciated :)

[musicbrainz-server] 14reosarevok merged pull request #3220 (03master…flow-231): Update Flow to 0.231.0 https://github.com/metabrainz/musicbrainz-serve...