-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Russian translation update #207
Comments
Side note: Can we have multiple milestones for the same issue? We have to synchronize versions... |
Not that I'm aware of - github only allows one milestone :/ Looks like we'll need multiple issues for things like this which is a bit of a PITA. |
(off-topic)
|
Fixed in 1.10.15-stable. |
(off-topic) After stable reaches parity with labs, we can then do the strict labs -> stable thing. I'm not sure using labels for milestones will work out well. We'd just end up with loads of crufty labels, and the milestones view would get confusing too. Ultimately I think we'll end up doing work against a labs milestone, and then once it's tested in labs we update the issue to use a stable milestone. So issue stays open to remind us that there's something that needs porting to stable. This is probably best discussed in the developer discord chat or a separate issue ticket. |
It's possible he also sent PR to old repo? I've not had any notifications (and am contrib on that repo) so possibly not. Anyway, the patebin seems to contain the full locale file.
The text was updated successfully, but these errors were encountered: