On 08/06/2016 22:59, Brian Grinstead wrote:
>> The code isn't used at all in Firefox, as discussed in
>> https://groups.google.com/forum/#!topic/mozilla.dev.developer-tools/XYPqQ58ndX4/discussion.
>> It’s also now possible to migrate usages to the Browser Console
>> i.e. Seamonkey is no longer usi
Hi zb.
I don't turn on ICU on Android version yet due to bug 1262102. So If
it is only on Desktop browser, it can use it.
On Thu, Jun 9, 2016 at 9:20 AM, wrote:
> Summary:
>
> Gecko's localization framework has not really changed much in the last 20
> years and is based on two data formats -
Summary:
Gecko's localization framework has not really changed much in the last 20 years
and is based on two data formats - DTD and .properties - neither have been
designed for localization purposes.
Our internationalization status is a combination of DIY helper functions, ICU
based APIs and a
The whiteboard field a text blob with no rules, only conventions on
separators (which are not used consistently.) If you misspell a tag,
there's no prompt to correct (unless the browser or os spell checker
recognizes it) and you can get inconsistencies that way.
As for "real tagging system" look,
On 6/8/16 4:03 PM, Jason Duell wrote:
Could we dig into details a little more here? I assume we could add a
database index for the whiteboard field if performance is an issue.
Do we give keywords an enum value or something (so bugzilla can
index/search them faster)? I'm not clear on what a "rea
Emma,
> it's not a indexed field or a real tag system, making it hard to parse,
search, and update.
Could we dig into details a little more here? I assume we could add a
database index for the whiteboard field if performance is an issue.
Do we give keywords an enum value or something (so bugzill
There is a ticket for a "proper" tag system,
https://bugzilla.mozilla.org/show_bug.cgi?id=1266609 which given time, I'd
like to get implemented, but with limited resources, this is what I can do
now.
On Wed, Jun 8, 2016 at 2:08 PM, Patrick McManus
wrote:
> as you note the whiteboard tags are per
Yes, 'amnesty' is probably too strong a term, and 'cleanup' is probably
better.
-- Emma
On Wed, Jun 8, 2016 at 2:19 PM, Patrick McManus
wrote:
> that's useful thanks. I think the word amnesty implied the death penalty
> for existing whiteboard tags.
>
> what it sounds like is you're just offeri
that's useful thanks. I think the word amnesty implied the death penalty
for existing whiteboard tags.
what it sounds like is you're just offering (for a limited time) to do
conversions on an opt-in basis? That's great.
-P
On Wed, Jun 8, 2016 at 3:11 PM, Emma Humphries wrote:
>
>
> > On Jun 8
> On Jun 8, 2016, at 1:43 PM, Kartikaya Gupta wrote:
>
> What happens after June 24? Is the whiteboard field going to be removed?
>
No, the whiteboard field remains, but any tags migrated will be deleted from
existing values.
If a tag is used across teams, I'll work out a resolution such a
as you note the whiteboard tags are permissionless. That's their killer
property. Keywords as you note are not, that's their critical weakness.
instead of fixing that situation in the "long term" can we please fix that
as a precondition of converting things? Mozilla doesn't need more
centralized s
What happens after June 24? Is the whiteboard field going to be removed?
On Wed, Jun 8, 2016 at 4:32 PM, Emma Humphries wrote:
> tl;dr -- nominate whiteboard tags you want converted to keywords. Do it by
> 24 June 2016.
>
> We have a love-hate relationship with the whiteboard field in bugzilla. O
tl;dr -- nominate whiteboard tags you want converted to keywords. Do it by
24 June 2016.
We have a love-hate relationship with the whiteboard field in bugzilla. On
one hand, we can add team-specific meta data to a bug. On the other hand,
it's not a indexed field or a real tag system, making it har
Who is responsible for updating our build documentation about this? It
seems the docs still don't believe we can even build for sure on VS2015
(though it's been the recommended compiler for a while now), and list a
number of SDKs that I'm not convinced you'd actually need to manually
install if
Filed bug 1278368 to remove the code and bug 1278372 to remove the component
from bugzilla.
Brian
> On Jun 8, 2016, at 7:57 AM, Benjamin Smedberg wrote:
>
> \o/
>
> Is there a bug to track this code removal?
>
> --BDS
>
> On Mon, Jun 6, 2016 at 4:04 PM, Brian Grinstead
> wrote:
> There is
\o/
Is there a bug to track this code removal?
--BDS
On Mon, Jun 6, 2016 at 4:04 PM, Brian Grinstead
wrote:
> There is an Error Console feature in toolkit that's been replaced by the
> Browser Console. We'd like to remove associated code in
> toolkit/components/console/ and the component in b
On Mon, Jun 06, 2016 at 09:35:34PM -0700, Bill McCloskey wrote:
> Hi everyone,
>
> I would like to announce a new tool I've been working on for source
> code searching called Searchfox (http://searchfox.org). If you use MXR
> or DXR, I recommend you try Searchfox. Here are some of the benefits:
c
Hello,
Next week, as announced in February [1], during our workweek in London, we are
making a pause on the 48 developments.
That means we won't build any beta version. The uplifts are also going to be be
limited (both from release management andsheriffs).
However, in case of critical or securi
Hi,
When we moved to the "inbound" model of tree management, the Tree Sheriffs
became a crucial part of our engineering infrastructure. The primary
responsibility of the Sheriffs is and will always be to aid developers to
easily, quickly, and seamlessly land their code in the proper location(s)
an
19 matches
Mail list logo
