> It appears to me the only sensible way to proceed is downstream-first: > First of all, 1.6 won't make it into Ubuntu for another 9 months, thus > upstream doesn't make a difference right > now. I probably shouldn't even > have gone that route, after i missed 1.5 cut-off.
Actually, as you can see from recent ubuntu updates to xkeyboard-config, I have begun routinely backporting patches from upstream's tree on bugs that originated here on launchpad, and plan to continue doing so at least until feature freeze, and possibly up until before beta-freeze. I like doing this because I can then drop the patches when 1.6 is released with no worries. I also value upstream's review on the patches since they obviously know the code much better than I ever will. > The patch isn't really that big: probably about 95% of it is .po file. I don't know if it matters that much, but if it makes a crucial difference, .po file can be taken out for now: i could provide separate patches, and thus make .po separable. Yes, in fact that would indeed help. The bigger the patch, the harder it is to review and the more risk that something will break, which consumes extra time for me. If you can minimalize the size of the patch, I would be open to including it in ubuntu before it's taken upstream. Bryce -- Patches for Crimean Tatar (Crimean Turkish) keyboard layouts https://bugs.launchpad.net/bugs/323041 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
