#musicbrainz-devel

so what's the story with the release editor?

is there a spec for the new version?

or it's more of a gradual one-off incremental improvement kinda thing?

ianmcorvidae: no rushing!

warp: ping

ocharles: ping

reosarevok: ow

Any idea of why this does nothing? http://musicbrainz.org/edit/14551763 -> http://musicbrainz.org/release/c6f7132c-2393-48...

(whole issue due to http://tickets.musicbrainz.org/browse/MBS-2467 )

reosarevok: weird

Meh, true

It's not the same artist

ah, that caps problem looks quite easy to fix

So that's the problem

But the caps thing should be fixed, yes please

:)

everywhere I look today there are bugs :(

:)

there were bugs on the roads today... or maybe that was just my buggy driving

I wish the release editor's searches weren't completely broken for me

I've yet to see the add disc thing work properly

(or at least not consistently)

nikki: have you tried changing the artist name to ascii for a moment, searching and editing it back?

(ugly, I know, but…)

there are aliases :/

And they don't work either?

*sadface*

not as far as I can tell

reosarevok: ack

warp: it was just to ask about http://tickets.musicbrainz.org/browse/MBS-2467 and its ease of fixing, but ollie said it was kinda easy already

(hope he's right)

tsk, enter it consistently! :P

yea, user problem :P

Tell Guess Case not to touch it then!

hm, we may need a checkbox for that then.

luks: is your "Set medium titles when merging releases" patch published somewhere?

bitmap, luks: could you make some Picard plugin to take feat. out of both the title and artist fields?

nikki, reosarevok : I'm working on relate to works atm

If it creates a new work, I assume that work should automatically be linked to the recording, right?

yes

yep

are we always assuming just "performance" with no attributes is correct?

Hmmm… well, it is always correct, after all, isn't it? "cover" is extra info, but it would still be a performance anyway

(having an option you can check if it is a cover might be useful, but I'm not sure)

the interface is looking a bit messy at the moment without more options :)

for now I'll leave it out

if we're creating a new work, I would expect it to not be a cover (normally you'd link a cover to the existing work)

medleys are a bit more tricky, but I guess covering most works you need to add is a good start

Is test.mb.org expected to be suffering problems at present?

pecastro: I merged your makefile changes into master.

warp: Hi. Tkx.

cjk32: I'm not mucking with it currently, and as far as I can see ocharles isn't either.

cjk32: so it shouldn't be suffering problems.

warp: I have mucked with it

haha, ok

ocharles: css is broken.

I changed branches

back

ok :)

ocharles: always a bit odd to see no-one logged in with "who" in one moment, and then see people logged in with a login time of three weeks ago on the next run a few seconds later.

lol

reosarevok: there's already one for track titles at least: http://users.musicbrainz.org/~luks/picard-plugins/

bitmap: I know, what I want is that extended to artists

oh, okay

(we'd need that before being able to change the current feat. style to anything involving artist credits :) )

css is fixed now, but trying a "New Artist" edit fails.

reosarevok: does that mean we can expect an RFC from you on this topic soonish? :)

warp: it means *you* can expect a +1 from me in your RFC on this topic ;p

reosarevok: drat!

But I want that RFC to pass and this seems to me to be a minimum prerequisite for it

I don't expect I'll have the time or inclination for that for a while.

Aww

Well, I'll think about it

I guess http://paste.pocoo.org/show/398852/ should work, but luks will have to update it since it's his plugin ;)

bitmap: notice that it is likely that the artist field won't have parentheses surrounding the feat

reosarevok: I made the parentheses optional for the artist names

:)

nikki, reosarevok : relate to works alpha edition on test.mb.org :)

same annoying approach as before - relate to artist firts

doh, broke it

ok, it's working now!

warp: https://gist.github.com/1002367 I think HTML::FH makes *everyone* go crazy

hehe

murdos: ping

warp: https://github.com/lalinsky/musicbrainz-server/...

luks: thanks!

warp: astro seems to have a load of stuff that's not in production :(

ocharles: hrm, huh?

warp: https://gist.github.com/1002586

ocharles: so what branch is astro on then?

production, but something has been errornously merged into it

ocharles: on astro?

seems to be that way

odd, and pingu is clean?

git rev-parse production gives different shas on my box and on astro

something has merged next into production

because I can see "Merge branch 'master' into next"

* 618c2de - Merge branch 'next' of git://git.musicbrainz.org/musicbrainz-server into production (9 days ago) <Robert Kaye>

ocharles: so ruaok messed up then?

it twud appear that way!

I have to go fetch someone from the hospital, back in about half an hour.

ocharles: make sure to hit ruaok on the head with blunt objects when he joins the channel.

noted

luks: how would you want to do the merging of RAWDATA and READWRITE if not through upgrade.sh?

ocharles: I expect that djce or somebody else who will be doing it will want way more control over the process

ok, well I'll leave it open in the review for now and it can be discussed more with rob

as an example, I don't think it will be done remotely

that's a huge amount of data to transfer for no reason

remotely?

oh, you mean between astro and totoro?

I hadn't considered that

and additionally, I don't think we want complete downtime during the whole migration

MB should go into read-only mode

export but do not modify in any way the old DB, import into the NEW one, put back to read-write mode

right, but that's just a case of flipping a DBDefs switch, that's not part of the upgrade scripts atm

no

"echo 'ALTER SCHEMA musicbrainz RENAME TO musicbrainz_raw' | ./admin/psql RAWDATA" effectively puts MB down