#musicbrainz-devel

reosarevok: can you reproduce that?

ocharles: I think it's caused by asking bitmap's script to make a lot of works in a row, + then trying to do other stuff myself

But yes, I can reproduce it in that I have gotten it several times in the last two days, I just got tired enough to ask today :)

(I can't reproduce it in that I can't just make it happen when I want to)

In this case, as you can see in the URL I guess, I got this simply while loading a work page

(while the script run in other tab)

*ran

ocharles, see http://blog.musicbrainz.org/?p=1223&cpage=1...

(you might want to answer / check)

ocharles / warp: http://tickets.musicbrainz.org/browse/MBS-4130

Rare enough to not hotfix probably

But still, please try to fix it soon - can cause annoying data corruption

ocharles: Please merge this in for me. https://github.com/navap/musicbrainz-server/com...

hi navap!

Hey

I saw a lot of hilights today, but no jira emails. Very mysterious.

I got jira emails today.

I guess nothing was assigned to you 'cause we were disagreeing about whether you should be assigned or not :P

I meant, my name kept getting thrown about but I wasn't assigned anything

Well for the record, I'm fine with getting stuff assigned to me.

see, that works for me too.

I usually go prowling through some of the components for tickets I can do and assign them to me. If there's stuff that you guys think I can take on then that makes my job easier

but the jira manifesto that ocharles wrote prohibits it.

ollie was worried there'd be too much and you'd end up not being able to do it all, like he couldn't

I saw ocharles made a comment about due dates, which also made sense

navap: thats what I'm thinking.

but he was the default assignee so ended up with practically everything, whereas we're picking out specific things, so it doesn't seem the same to me :/

Yeah

well, at the office I noted two tickets that you should work on,

I'll assign them to you tomorrow.

and I'll finish finances for 2011 tomorrow, so then you can write the annual report too.

Excellent :)

I've already drafted up a bit of it

the donation of servers got us in the black for 2011. but only by a few bucks.

it was tight.

And assigned a ticket to warp to get the top contributors

but we're already received a 20k donation this year. :)

*we've

What was the value of the server donation?

$48,242

Wow

ya, they handed over a pile of stuff. none of it was slouchy. :)

and tomorrow I'm picking up a 32 port remote login box.

so we can log into the console on any of our servers. from anywhere.

that'll make djce and my life a lot easier. :)

Sounds like it

ianmcorvidae: Hopefully you got an email with this, https://github.com/metabrainz/musicbrainz-serve...

interesting, we just barely tipped our new, higher ws global ratelimit a few hours ago: http://stats.musicbrainz.org/mrtg/drraw/drraw.c...

that's the py73 spike of course

I see from the blog there was a release yesterday. Can't see a tag for it in git though (unless I'm going blind!)

Is there one?

djce: has something changed about the rate limiter in the last couple of days?

I believe both ends (musicbrainz-server and the rate limiter have changed)

nikki: thanks for reporting http://tickets.musicbrainz.org/browse/MBS-4132 - it has bothered for a few days, but I was too lazy to report it

oh, weird

ocharles: perhaps you can find the error for http://tickets.musicbrainz.org/browse/MBS-4133 :P

this rings a bell from seeing a stacktrace about add recording

I'll enable stacktraces on beta too

nikki: also, can you put beta ise's (that seem to be new) in the 3mo bucket?

ok

cause we should certainly be getting them fixed asap

anyone else having strange results while sorting with javascript on http://musicbrainz.org/statistics/countries ?

yea, the commas break it

I know mbs-4132 isn't a beta one though, 'cause reosarevok got something similar

ocharles: ok. so I can report this issue

murdos: yea, please

nikki: ocharles is correct. Did that answer help?

yes

ocharles: can you point me to the wiki page explaining release process (with test/beta/live)?

For example there was a bug for about 24h recently which explains this gap: http://stats.musicbrainz.org/mrtg/drraw/drraw.c...

but the fact that this graph has stopped is deliberate: http://stats.musicbrainz.org/mrtg/drraw/drraw.c...

murdos: http://wiki.musicbrainz.org/Release_Process

since it duplicated this one http://stats.musicbrainz.org/mrtg/drraw/drraw.c...

ocharles: there's something I don't understand. beta should be next live version, isn't it?

this is where there's some confusion :)

I see from the blog there was a release yesterday. Can't see a tag for it in git though (unless I'm going blind!)

adhawkins: no tag yet

Is there one?

Ah ok.

adhawkins: ruaok always lags behind on tags...

I'll keep an eye on my cron job then :)

we currently have the model that "beta contains branches that are in user testing"

but some people think "everything that will go into the next release" makes more sense

beta?

si

Is that a tag name or something?

it's beta.musicbrainz.org

and it's a branch

(this is to murdos)

Ah ok. Wires crossed there :)

for me "branches that are in user testing" is test

murdos: but no one tests them, because they are not against the live database

I think people like nikki, me are using test

if we want to change it as "bleeding edge version of master" (ie, what the next release will be) it simplifies things a lot

but I'm bothered by the fact that beta doesn't reflect the next live version, because that way you can always discover issues on musicbrainz.org that were not appearing on beta.musicbrainz.org

when I asked for beta, I expected it to be stuff in master that hasn't been released yet

because of merge issues, ...

I think we therefore need to change this workflow :)

as everyone but me and warp aren't confused, and we're the least important people as far as "makes sense" goes

murdos: well beta should always have the same issues as master, unless they get fixed

So would people be happy if beta was just the master branch, but updated basically on every push?

I'd be fine with it, since that's what I expected it to be :P

(in practice it's a tiny bit more fiddly than that, because not everything can go out at once)

+1 for me too

expected schema changes and data fix scripts, everything that has been code reviewed goes in master (and beta), and everything that is in master is pushed in production on each server release.

yea, the only thing that is problematic is stuff that goes onto beta and people say "woah, this isn't ready at all"

it's very hard to un-merge a branch (though it can certainly be done)

the other option is to just not release until that work is done, and delay the release

if we find something that bad, maybe we *do* need to delay the release

I'm all for delaying release, in order to have polished release, rather than half-baked release

well, what we'd do atm is just not release that feature at all

and delay that feature to the next release

this will cause us to delay the entire release until that feature is done

(which is what will happen for CAA if I've correctly followed discussion)

and I think I'd prefer delayed releases which do include the things we marked as being included over being like "we're releasing this...oh no we're not!" (like the whole "fix version: next monday... next next monday... next next next monday..." stuff we've been doing for months :P)

fine with me :)

(of course, if something is a total disaster and it would take weeks to fix, then something like that might be ok to revert)

but it's a special case which should take a specific discussion

so not having that part of the general release process isn't a huge problem

heh

nikki, murdos: so, we have a bunch of stuff "in beta testing" atm

what shall I do with them? merge to master, clear beta, and put master back there?

probably merge them to master, but I would like to see a list of these things before

Well they have all passed code review :)

I know, this is just to know what I need to test on beta ;-) until very recently beta was not really usable, so I've not used it much

sure

I'm hoping to get beta blogged this month

I'd like to mashup a list of 'these features are in beta testing' into it, add preferences to 'always prefer beta.musicbrainz.org', and the email problems need to be fixed