#musicbrainz-devel

what kind of curry? <- more important question

oh yeah

nice

naan'd it up?

no naan :( just rice

cooking for 1 means I take shortcuts and just eat for 2

yeah

but this has been marinading all night, smells delicious

feh. the update script didn't convert the lists. :(

aCiD2: should it be doing that now?

I won't have converted edits either because that's disabled

unless you turned it on

I didn't

and lists... do we have the public list tables?

public.collection or whatever

edits turned on

which upgrade script converts collections?

and should I be running rebuildcoverarturls?

hi ruaok

ruaok: I'm not sure, I'm looking now

and no, you don't need to run that

ngs-rawdata.pl should

have you got public.collection_info in rawdata?

the stubs didn't get converted either.

I think that script failed.

count

(1 row)

looks like that script is malfunctioning

quietly if so.

what's the output after that?

woah. we're ditching a bunch of collection data by converting only two tables. :(

BEGIN

COMMIT

that's after the collections line?

wait no.

Fri Oct 8 16:05:39 PDT 2010 : Merging releases

Fri Oct 8 16:31:45 PDT 2010 : Create tracklist index

in other words, it goes on to another script.

i thought so

actually, collections are the list bit anyway

lists can contain only releases, right?

oh meh, the code to extract jira tickets and display them on my dashboard thingy was broken and was omitting a bunch of bugs.

fuck. because then we're tossing the artist discography and the watched artist feature.

yes, that hasn't been written yet

are there tickets for that?

aye

ok, good.

right-o. lets go look at tickets.

ok!

I'll go wrangle the data conversion in a while.

ok, how do you guys want to tackle this?

Best way might be for you to pull the list of all open issues for RC1

sort by issue, and click the first then "next" through them

if it looks good to you, keep it

if you're unsure, paste it here?

maybe filter that to be non-bugs too

scanning down the list, I can't readily identify anything that should not be done.

they are all pretty important I'd say

yeah.

lets focus on re-shuffling things so we arrive at an even workload.

right now its at 7 weeks warp and 3 weeks you

aCiD2, warp: what things do you see that we can pass to aCiD2 ?

hello

sorry, was distracted by a phone call.

back now.

http://jira.musicbrainz.org/browse/MBS-248 is one

I just noticed I have a whole bunch of unestimated tickets, which weren't showing up before because of my shoddy PHP work.

http://jira.musicbrainz.org/browse/MBS-681 I might be able to do that

http://jira.musicbrainz.org/browse/MBS-84 that is already fixed I think?

http://jira.musicbrainz.org/browse/MBS-54 is for me

would both of you like to take some time to ensure your tickets are estimated properly.

?

http://jira.musicbrainz.org/browse/MBS-392 too

I'm happy with my estimates

http://jira.musicbrainz.org/browse/MBS-403 may be for me?

http://jira.musicbrainz.org/browse/MBS-415 that too

take whichever you want :)

Please just open them and make sure I'm ok to take them

oh, duplicate check is good, that would be a fair amount of work (for me anyway).

84 does not seem done.

I mean we have the "add various artists release" link in the menu

add release always seemed like a fairly redundant link

it's just the menu item, that's 5 minutes and doesn't need to go through code review.

we've by now already spent more time talking about it compared to the amount of work left on it.

lol

aCiD2: edit conditions, yes, for you.

6/4 weeks now.

one more week to go. :)

5.2 / 4.3

Remember these are warps estimates though

the way I see it , warp gets the RE, aCiD2 gets everything else. :)

When you're done giving me way too much shit to do, I'm going to re-evaluate it

;)

perfect.

just keep track of which ones you need to estimate

and as I said, I discovered a whole bunch of unestimated tickets.

but that will probably upset the balance more, as sometimes I tend to work faster than warp

thats fine.

ok, we'll do another pass once you estimate those

ok, we're near 5 weeks for both of you.

ok.

ruaok: I generally agree, but i don't want warp to burn out because he's too focused

I'

that happens to me sometimes

ll be here.

(if I spend weeks on just one area)

I trust warp to tell me if something is amiss. :)

:)

aCiD2: extending the release editor to add artists/labels inline is probably something you will get done much faster than me. do you have that ticket yet?

nope

that sounds difficult though, but I might be able to hack it out faster

ruaok: re-estimated mine, think you'll find the balance quite upset :)

aCiD2: http://jira.musicbrainz.org/browse/MBS-244

woah

are there any non-RE tasks left for warp?

i don't think so

and I have a few now too

How about we hack on these for 4 weeks or so, and see where we stand then?

is that even still valid?

not really.

can I close it?

yes

it's part of other tickets.

k

ok. so, if I post to the blog saying that RC1 comes mid-to-late november without setting a date, we should be ok, right?

then we wait 4 weeks, re-eval and set a fixed date.

how does that sound?

hopefully good!

I'm not sure

Then we might be able to ship for christmas

my screen is still filled with unestimated tickets

OH!

I'll sit tight then.

is there an easy way to see that in jira? :)

unestimated tickets? yes.

if I can remember how...

I currently have 53 tickets, of which 22 have estimates.

project = MBS AND remainingEstimate IS NULL AND resolution = unresolved AND assignee = currentUser() AND fixVersion = "NGS - RC1"

aCiD2: start looking at more tickets to steal