Apache Allura / Chat is hosted on FreeNode IRC channel #allura
Yeah, I was thinking the exact same thing
brondsem: I joined the IPMC so I can vote on Allura releases - probably gonna check it all tomorrow and then cast a vote :)
it won't be a sebb-like review, but I'll do my best ;)
+1 you can always edit it later :)
My main concern is the Stable Release info, since it's not official yet
But, we can always change it if needed
Ok, it's submitted. Hopefully it gets reviewed and approved quickly.
But I doubt it. There are apparently 1800 submissions in the backlog
Don't suppose anyone here has new article approval status on Wikipedia, eh? :-p
you can't just make new pages directly on wikipedia any more?
shrug I just clicked the submit link on the draft.
So I didn't need to dot aht
Well, anyway, I don't think I meet the requirements to move the article, since my account is new
Anyone with an existing account with edits want to go ahead and move it?
i should be able to
i'm thinking we can drop the (software) suffix?
Hrm. Yeah, fair enough
i'm getting stuck since the Allura page was already present
reading the help..
hopefully it'll be deleted soon, then I can move your draft
Yippie, build fixed!
if not, we shoudl be able to do that
brondsem, ctsai-sf: FYI, I'm about to hit the upgrade button for ScummVM
the data from the previous upgrade won't interfere?
it'll be removed
ok, here goes, then :-)
we've had a number of projects in the past that rolled back and re-upgraded
Hrm, so that's what was happening at 1pm that I was thinking I'd want to make sure to take my lunch break earlier for... but then I couldn't remember what it was and got caught up in other stuff...
ctsai-sf: i wouldn't wait for it to finish before eating :)
Oh, well, brondsem's around in case there's an emergency rollback we need to.
Though I doubt that'll be necessary.
Indeed, I'm going to grab a bite now.
i've sent an email to email@example.com about those failures. they're all git timeouts
configuring our build now to run only on ubuntu2/4 since they seem to be fine
brondsem: re max markdown size, i don't remember seeing it in the diff, will check and remove if necessary
actually i guess we could just set it to a huge number in the config
will change in configtree
default in development.ini would be good to increase too I think
i wonder if we want our SF-internal jenkins instance to report in here, since the apache job can take hours sometimes until it is run (lots of other jobs)
i don't want too many notifications though :)
wjp: upgrade is still chugging along
not sure what that means on the scale of it though :)
patches are imported; feature requests have not yet
that's about 80% through the bugs I think
assuming it does it chronologically
I count 8912 artifacts, of which 1615 patches, and this is bug #5699 / 6599, so that means a total tracker progress of 83%
which would mean another ~35 minutes if everything is linear
wjp: i'm heading out shortly, but I'm sure ctsai and I can help out with any questions you might have tomorrow
I've just tweaked tracker permissions a bit, but so far things look ok