I first thought: here we go again. But checking through the messages I saw that deadlines were stated clearly. I´m missing the deadline one more time, my fault. But, that said, I´d vote for changes in the l10n process. I can´t understand why we need to file a bug, and another bug, and more bugs, for being able to do what others - every team who commited their stuff before l10n lock - did without going through that hell.
I first thought: here we go again. But checking through the messages I saw that deadlines were stated clearly. I´m missing the deadline one more time, my fault. But, that said, I´d vote for changes in the l10n process. I can´t understand why we need to file a bug, and another bug, and more bugs, for being able to do what others - every team who commited their stuff before l10n lock - did without going through that hell.
Marek Stępień wrote: > Axel Hecht napisał: >> Oops, bad me. Got the wrong week. I somehow had in my head that we'd >> close the Sunday after the summit, must have been memorizing that wrong.
> So, to make that clear: you are still accepting patches for 2.0.0.1, > aren't you?
Yes, I will go through the review queue tomorrow. Right now, I'm more or less on my feet 24+, not a good idea to do approval work tonight.
> > So, to make that clear: you are still accepting patches for 2.0.0.1, > > aren't you?
> Yes, I will go through the review queue tomorrow. Right now, I'm more or > less on my feet 24+, not a good idea to do approval work tonight.
Since we are going through this for the first time, I am not sure what that means for the Kurdish locale. There are some open bugs, some of them filed by Axel himself, but it seems he is taking care of it. Is further action from our side necessary?
Erdal Ronahi wrote: >> > So, to make that clear: you are still accepting patches for 2.0.0.1, >> > aren't you?
>> Yes, I will go through the review queue tomorrow. Right now, I'm more or >> less on my feet 24+, not a good idea to do approval work tonight.
> Since we are going through this for the first time, I am not sure what > that means for the Kurdish locale. There are some open bugs, some of > them filed by Axel himself, but it seems he is taking care of it. Is > further action from our side necessary?
The biggest blocker right now is getting ka and ku built. Then we can look at the results and the builds and so forth.
Stuff you could do is to file a bug to get a bugzilla component set up for Kurdish :-), that'd be a good thing. You should provide information about the native-language name for kurdish as well as default QA and assignee.
I'll poke jay about getting the build stuff approved. Or make clear that I would prefer to not approve that patch myself, though I technically could.
