Nice to know the command patches are being looked at. How long does it usually take for a patch to make it into Ubiquity release? Mine's been sitting there for 3 weeks:
http://labs.toolness.com/trac/ticket/320 I was hoping that since this was submitted weeks before Ubiquity 0.1.2 there might have been a chance of it making it in the release. - Mayuresh On Sun, Oct 26, 2008 at 5:20 PM, Abimanyu Raja <[EMAIL PROTECTED]>wrote: > Today, Blair and I spent some time closing the old tickets. And I noticed > that there are a lot of command-related tickets that are still open. Of > course, commands might not be as interesting to work on but from the user's > perspective, Ubiquity is only as good as its commands. So, this is just a > call to everyone to help clear up some of the patches and start working on > making our commands better at the same time. > It would be cool if we could aim to always be 85% complete on the Command > Updates milestone (but of course, that means completed tickets should be > removed from the milestone after a while...). Maybe, if we fall below that > %, it'll send a message like the one that is generated when the buildbot > fails. > > - Abi > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ubiquity-firefox" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ubiquity-firefox?hl=en -~----------~----~----~----~------~----~------~--~---
