Sounds like a good idea, I will give it a shot. Nice to know that
command-releases are decoupled from the core.

On Sun, Oct 26, 2008 at 11:37 PM, Blair McBride <[EMAIL PROTECTED]> wrote:

>
> The 2-3 weeks leading up to 0.1.2 was more concentrated in fixing
> things that were broken, so as not to push back the release date even
> further (it slipped by quite a bit!).
>
> But the great thing about 0.1.2 is that the standard command feeds can
> be updated without needing to update all of Ubiquity - they update
> just like normal commands now.
>
> Regarding how long it should usually take a patch to get into
> Ubiquity... hopefully not as long as 3 weeks! Hopefully things will
> move a bit quicker now that 0.1.2 is out, and there's a lot less noise
> to sort through on Trac.
>
> Oh, and Fernando's suggestion sounds very desirable.
>
> - Blair
>
>
>
> On Mon, Oct 27, 2008 at 11:28 AM, Fernando Takai
> <[EMAIL PROTECTED]> wrote:
> > mskadu,
> >
> > Your patch is pretty good, but would be better if we had an modifier to
> > choose countries - maybe you could do an ebay-country-search-noun and add
> > the default for the country?
> >
> > Cheers!
> >
> > On Sun, Oct 26, 2008 at 8:15 PM, <[EMAIL PROTECTED]> wrote:
> >>
> >> 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
> >>
> >>
> >
> >
> >
> > --
> > Fernando "Takai"
> > http://flickr.com/photos/supeertakai
> > http://fernandotakai.wordpress.com
> > http://fernandotakai.jaiku.com
> >
> > >
> >
>
> >
>


-- 
Mayuresh

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to