- Fixed: 305588 – Cannot open multiple attachements at once
- Fixed: 318547 – No list of attachments when saving email as text file
- Fixed: 508250 – Provide “Forward as” options as dropdown button menu entries (dualbutton / menu-button for forwarding inline vs. attachment)
- Fixed: 595104 – Support plural forms in messenger.properties where possible
- Fixed: 679908 – probing.png is missing
- Fixed: 734550 – test_mailGlue_distribution.js: Services.prefs.getPref() does not exist
- Fixed: 807699 – Sanitize dialog (“Clear Recent History”) cleanup: unused strings
- Fixed: 812923 – Dragging a huge number of messages onto a folder freezes TB even BEFORE dropping
- Fixed: 830177 – Typographic fix in Account Provisioner labels
- Fixed: 853531 – Use a nicer icon for the new “New Mail” notification.
- Fixed: 858010 – Display error in TB 22 using personas
- Fixed: 859120 – Unprefix the last -moz-linear-gradient in mail/themes
- Fixed: 863617 – Fix leftovers from switch to Services.jsm and mailServices.js
- Fixed: 864838 – Replace nsIBlocklistService with Services.jsm (port bug 856144)
- Fixed: 866223 – Compose windows are no longer recycled
- Fixed: 868848 – Build failure: [xul.dll: fatal error LNK1120: 1 unresolved externals] [DXVA2Manager.obj: error LNK2001: unresolved external symbol _MR_BUFFER_SERVICE]
- Fixed: 869609 – mail: Virtualenv failing on multi-arch Debian-based distros
- Fixed: 869890 – thunderbird should declare itself dpiAware on windows via the .exe manifest
- Fixed: 872041 – Mailing List does not work when entered in address box
- Fixed: 872478 – [trunk] Make package is failing because of missing files in package-manifest
- Fixed: 876054 – Stop using getPreventDefault() in convbrowser.xml
MailNews Core-specific: (24)
- Fixed: 248808 – Search/filter/mailview: “date”, “is after” includes messages on date
- Fixed: 513709 – configure.in: Remove some useless vars, mozilla-* ones are enough
- Fixed: 594646 – If order of http-equiv and content in <meta> is reversed(<meta content=”…;charset=…” http-equiv=”Content-Type”>), charset in <meta> is applied to mail data coverted to utf-8. Thus, non-ascii characters are shown in garbled
- Fixed: 640371 – Local Inbox folder allowed to grow past 4GB by mail download
- Fixed: 694196 – crash [@ MsgGetHeadersFromKeys(nsIMsgDatabase*, nsTArray<unsigned int, nsTArrayDefaultAllocator> const&, nsIMutableArray*) ]
- Fixed: 735433 – Create and use TEST_DIRS variable, in MailNews Core
- Fixed: 839279 – Code cleanup in /editor/: Use new String methods like startsWith, endsWith, contains and use querySelector instead of NodeList calls
- Fixed: 852869 – Remove some redundant Makefile.in files in comm-central
- Fixed: 856577 – crash in nsMovemailService::GetNewMail
- Fixed: 858238 – localMsgs.properties should use string based identifiers rather than numbers
- Fixed: 859125 – Clean up confvars.sh and configure.in
- Fixed: 863672 – Port configure.in changes to comm-aurora
- Fixed: 864192 – Move EXPORTS to moz.build in comm-central
- Fixed: 864417 – broken observer calls in editor.js due to bug 795158
- Fixed: 868393 – Require alphabetical order when assigning to order-independent moz.build variables
- Fixed: 869359 – Move XPCSHELL_TESTS to moz.build as XPCSHELL_TESTS_MANIFESTS in comm-central
- Fixed: 869425 – Move MODULE to moz.build in comm-central
- Fixed: 869445 – Configure without mozconfigs broken
- Fixed: 869449 – Kill off DIR_INSTALL
- Fixed: 870282 – Searching by “Priority” is missing an “Isn’t” operator
- Fixed: 870307 – Remove some redundant nsVoidArray includes and member variable
- Fixed: 873177 – Fix typo that regresses getCellProperties result
- Fixed: 873754 – Tweak Last-Modified date for new feed subscribe
- Fixed: 874101 – Add entries to .hgignore
Thunderbird Meeting Details :
Remember to use headphones and mute yourself when not talking
Feel free to ask questions in the meeting either by speaking up or by asking them in #maildev on IRC.
Other ways to get in touch with us can be found on our communications pageMeeting Changes
- taking notes on Etherpad at https://thunderbird.etherpad.mozilla.org/status-meeting-minute-taking
- We have a calendar at https://firstname.lastname@example.org/Thunderbird%20Schedules to have meetings coming up.
mconley, irving, rolandtanglao, JosiahOne (audio only), wsmwk, clokep (incoming audio only), aceman (audio only), mkmelinAction items from last meetings
Action items from last meetings
- (CLOSED) Standard8: Look into having the notes blogged
- They are blogged: https://blog.mozilla.org/meeting-notes/archives/tag/thunderbird
- Added to http://planet.mozilla.org/thunderbird/ a few weeks back
- (???) Standard8: Document flags to tb-planning
- (???) Standard8: Follow up with metric numbers being public
- This should be happening soon, work has been done, waiting for final approvals
- (CLOSED) http.jsm update?
- clokep needs to file a bug to get it included (see below)
- atuljangra will be moving the FileLink backend to chat/ as part of GSoC, this will de-duplicate http.jsm
- (2013-04-02) Investigating possibilities for dropping second ESR release channel whilst maintaining mainstream the same as the ESR releases.
- (2013-04-02) Standard8: arrange for swag to be sent to WADA and Aryx who are our awesome FotT.
- Community as a whole: Decide “who is supposed to plan our dances?”
- rkent: Send a proposal to tb-planning
- I’ve got two GSoC students assigned to me
- Jon Demelo will be working on a connector for Ensemble – likely a CardDAV one.
- Fallen will be working on making devtools work with Thunderbird.
- I have a contributor (Sakshi Bansal) investigating some object comparison algorithms for me, because I feel like the one we’ve high-jacked and extended from Underscore.js isn’t ideal. I have him looking at what Sync is doing.
- Cleared a bunch of reviews last weekend, will clear more this week
- Our tree is in bad shape, Mozmill-test wise. :/ (seems to be coming from m-c)
- I’ve got two GSoC students assigned to me
- This got more (less?) complicated, Instantbird has a GSoC student (Atul Jangra) to integrate FileLink.
- Potentially could move FileLink under chat/ as it would then be shared code.
- Decided in meeting that we WILL be doing this, it is simpler than moving http.jsm to toolkit.
- Will be mentoring a student (Quentin Headen) to add Yahoo! Messenger support to the chat/ backend.
- I am trying to test the McAfee update on Windows 8 using Thunderbird 17.0.6 (fixed in McAfee 12.1.338released today although they are throttled like firefox so uninstall and re-install to force an update if you don’t want to wait!)
to force an upgrade to 12.1.33
- Will make volunteers SUMOMO admins (vincent, wayne, matt) so they can have the fun of SuMoMo SPAM
- have been cleaning up the [good first bug] bug list, and it seems to have gotten some traction. we should add that to more easy bugs. (Yes, true, I also am mentoring some GFBs – aceman)
- wsmwk (late addition)
- bugday for Thunderbird+calendar June 12
- Q: what is the current procedure in reviewing bugs in /mailnews (account manager) like bug 389139? In the past I got IanN and somebody from TB to review it (like mconley). But what to do today if nobody has the time or rights to do it? Is Neil’s review enough for check-in? A: Yes
- Q: What is opinion on removing debug code added by contributors that already left? I mean e.g. code in #ifdef DEBUG_bienvenu . My idea would be to keep the debugging code (where it seems useful) just change the name of the define. Call it after the functionality it is testing, e.g. DEBUG_ImapProtocol. A: Better leave it as is…
- Ping Standard8 about his action items
While Thunderbird is having a test week, we’ve released the version that goes with it 2.4b1.
We are interested in catching regressions with regards to : Alarms, CalDAV Servers and Email Invitations.
The beta is on AMO now, I think the most user friendly link is https://addons.mozilla.org/en-US/thunderbird/addon/lightning/versions/?page=1#version-2.4b1.
We’ve just released Thunderbird 22b and lightning a corresponding version of lightning. Our next major release is due in a few weeks with version 24. In order to catch anything that might have gone wrong since the release of version 17.This week we need our users to spend a few hours testing the
applications, so that anything that might have gone wrong in improvements and fixes since the last big release of version 17 can be caught. There are two ways to test, a formal way and a less formal way.
Let me start with the formal way - as it’s the best way for us to know
the level of quality we’ve achieved with the products.
- download thunderbird at http://www.mozilla.org/en-US/thunderbird/all-beta.html and Lightning at https://addons.mozilla.org/en-US/thunderbird/addon/lightning/#beta-channel
- go to https://moztrap.mozilla.org/runtests/environment/293/ and start following the tests - try to also do test that have not been done yet
- file bugs for anything not working at https://bugzilla.mozilla.org , and in the advance field make the bug blocking bug 870347
The informal way of testing is just to switch your daily usage of Thunderbird to the beta version above and make sure that : you send crash reports and you file bugs in bugzilla as described above.
During the testing week we will be available for chat on #tb-qa (on irc.mozilla.org) to help you the best we can - please be patient as we might
be there but not answer so quickly.
Ludovic for the quality team.
- The character counter should now be correct when tweeting links.
- Twitter now uses the v1.1 API, this will allow Twitter to continue working past June 11th, 2013 (when the v1.0 API is disabled).
- Invalid/self-signed/out-of-date SSL certificates can now be easily overridden for IRC accounts.
- Logs are now organized by the date they were created, and smartly folded to easily find recent chats.
As we stated during the Instantbird 1.3 release, this version now requires Mac OS X 10.6 (Snow Leopard). Instantbird 1.4 is based off Mozilla 20 and libpurple 2.10.7, the newest versions available.
You might be asking “What’s next?” for Instantbird; we will be participating in Google Summer of Code 2013 (again through Mozilla). Through this and our other volunteers, we’ll continue improving Instantbird to make it a chat program you love to use. Hopefully we can integrate some cool new features from this year’s Google Summer of Code and finish integrating the Account Import Wizard from Google Summer of Code 2012! As always, if you see any issues, please file bugs!
In grad school, I remember a conversation across the campus green with an visiting psychologist from Harvard. I don’t remember much about the conversation except that he introduced me to Isaiah Berlin’s notion of the Hedgehog and the Fox, and correctly pegged me as a Fox. I think I was a bit offended at the simplification, but time has proven him right. I’m certainly no hedgehog.
I got into a silly argument on twitter last night, about whether my looking to hire someone who I labeled (as job descriptions make us do) a “Coding Designer” was not just foolish (I’d seen the Unicorn references in my tweetstream already) but apparently a bad idea, because, so the ultra-simplified argument goes, you somehow can’t be both. And so I’ll use the energy to rant a bit about what seem to be prevailing attitudes around titleism and narrow definitions of “professionalism”.
We all need to define ourselves to others. It helps us be understood, and hopefully valued. Labels can be useful for that. We also, even more, like to label others. It helps us simplify our approach to them. If I can find a label for you, then I can rely on a prioris about how people with that label tend to think and behave, and I don’t need to actually get to know you too much. The more people we interact with, the more important these shortcuts are. Some roles are particularly subject to that (Recruiters, VCs, politicians, etc. — people who routinely talk to dozens if not hundreds of people a day). And the best at these roles are those who use a different labeling system than their peers. Recruiters who see the latent ambition or genius in a shy candidate; VCs who see the determination behind a stutter, or, conversely, the lack of self-confidence behind the bravado, etc.
Labels are useful and practical in the short term. And I don’t know how one could run a large HR department without them. But we should be careful to not take them too seriously, as in the long term, they can hurt. They hurt because people, especially interesting, worth-getting-to-know people, are much more subtle, complicated, confusing and hard to categorize creatures. Whether you take the label too seriously when thinking about others (e.g., refuse to see the valid opinion about a design expressed by a non-Designer) or about yourself (and limit your impact on the world because “oh, that’s not something that a mere ____ like me could say/do”), you’re not getting the most out of anyone involved.
As I write this, I realize that I feel quite strongly about this topic. Part of it is probably because I grew up in an educational system, which at least then believed way too much in labeling people and determining their fate based on that label. Much waste ensued. Part of it is probably because I can’t for the life of me figure out what my label should be, and if I can’t, then that must be bad. I’ve had a range of professional labels, from scientist to engineer, architect, team lead, vice president, CTO, CEO, blah blah blah. I’ve been called a designer, strategist, entrepreneur, boss, blah blah blah. None of those words will, I hope, be in my epitaph. And so I get cranky on twitter at night, because if there are people who strive to be both excellent at design and at coding, then by golly we should encourage them.
Titles are a poor approximation of a professional ideal, and a profession is a poor approximation of a human’s breadth, contributions, and talents. Embrace your inner fox, and if you happen to have both design and coding skills, can see a problem, conjure up a solution, prototype it, welcome challenges to your idea from peers, data, and users, apply.
On the 20th and 21st of May the Library of Congress holds a workshop on the topic of preserving software.
Otto de Voogd and Robert Kaiser will be representing Mozilla, putting forward our viewpoint as custodians of a codebase with a significant heritage and importance.
Many questions and thoughts arise. Here's an overview of ours; we look forward to feedback.
- Should archivists keep source codes or executables or both?
Executables and source code are both valuable. Executables are valuable because the source code is sometimes not available, or perhaps the build tools are not, and setting up a build environment for older code can be a difficult and complex thing.
Source is valuable to determine how a program works. It also makes it possible to reuse code and algorithms, especially, but not only, in the case of open source software.
- Preserving documentation.
Preserving documentation that goes with software, seems logical.
Would this need to go as far as preserving discussion threads and entries in bug trackers?
- Preserving environments/platforms.
It seems obvious that without preserving an environment in which the software can run, it is going to be impossible to experience the software.
Preserving such an environment should therefor be part of the software preservation effort.
To avoid the physical constraints imposed by preserving old hardware (which would be a preservation effort in its own right), a solution would be to build virtual machines and emulators.
As hardware capacity constantly grows, running virtual versions of older hardware should generally be feasible.
To fully recreate an environment we'd also need to preserve the operating systems and other software tools that the preserved software needs to run.
Those being software themselves would logical already be included in any software preservation effort.
Preserving documentation concerning environments, would also be required.
To build virtual machines and emulators it would be helpful for hardware makers to make technical specifications available. One could envision this to become a legal requirement at least for older hardware.
Can we imagine a world where web based emulators would allow an online digital library to serve users worldwide? Users who would be able to run old software in emulators running in their browsers...
- Is everything worth preserving, if not how does one go about selecting what is worth preserving?
Does one need to preserve every version of software, just the last version or all major releases? What about preserving software that has not spread widely. Would there be some threshold, or some other criteria?
- How does one index software and search the library?
There will be a need to gather meta data about software and the preservation of documentation as we already mentioned. This meta data and documentation could serve to populate an index enabling for instance the search for particular features.
- Can software preservation help in making code reusable?
If there are good ways to actually find relevant and useful code, this could lead to more reuse not only of actual code, but also of algorithms and concepts.
It may also become a valuable source for students who wish to learn about actual implementations of software solutions.
At the very least a minimum of meta data, such publication dates, copyright owners and licenses should be available to determine how certain code can be reused.
In particular for open source software we believe that software libraries should strive make it available without restrictions.
- Preserving data formats.
The software preservation effort should also include an effort to preserve data formats. Including technical descriptions of those formats and the tools to read, write and edit those formats.
- Can software preservation help in the discovery of prior art?
We believe it can, and as such preserving old code could be a great tool in preventing the repatenting of existing software concepts.
Of course we believe that software patents shouldn't exist in the first place, as software is already covered by copyrights, but at the very least prior art is a good avenue to prevent some of the worst abuse of software patents.
- How do copyrights affect software libraries?
A lot of software is licensed to be used on a particular piece of hardware or only available via subscription. How does this affect software libraries? Should there be exceptions like there are for traditional libraries?
In the life cycle of software, the commercially exploitable time is limited, likely anything older than 10 years no longer has any commercial value.
Maybe copyrights on software should be significantly reduced to something like 10 years, which is more than enough to cover the commercially exploitable timeframe of the software life cycle.
Such a limit would greatly enhance the work of software libraries, increasing availability and ease of access as well as removing a lot of the red tape involving requests for permission to keep copies.
- What about software as a service?
And what about software as a service, where neither the source code nor the executables are ever published? How can something like Gmail be preserved, when neither the service's code nor the environment is available to the public?
- Preserving "illegal" or cracked copies?
What if a copy of a piece of software comes from an illegal source? A cracked version with modifications maybe? They have value in themselves as they are a cultural expression.
What if such an illegal copy is the only copy still available? Would it make sense to preserve that too?
Hello Folks. If you have been using Lightning 2.3b1 with a localized version of Thunderbird, you probably had troubles with undefined entities. This happened due to a glitch with the Mozilla localization dashboard, the wrong changeset was used.
I have just uploaded Lightning 2.3b2, which should fix the issue. As always, you can download beta versions from the addons.mozilla.org site in the “Developer Channel” box. If you have previously installed a beta, you should get the update via automatic updates.
While we at Mozilla know you can do a lot of good things in JS these days - after all, we're even launching our own phone OS building fully on HTML+JS, and we have been using more and more JS code to power key functionality in our browsers and other products over the years - it's great to see that complex things like editing maps can be done fully in JS and available for all platforms now, while previously it took proprietary and availability-limited technologies like Flash or Java to do the same thing.
Great work, OpenStreetMap guys!
(And yes, as a contributor to OpenStreetMap and even OSMF member, I am biased, but free and open map data on the web fits Mozilla philosophy pretty well anyhow...)