Mozdev.org

Not quite what I was hoping for, but bug 319770 has now official status wontfix: The message context menu won't get a "Forward As Attachment" menu item in Thundebird core. Though that means a longer life for my extension, I would have rather seen the right click context menu made available for all users.

Ah, well... Maybe they will get that someday when work is started on bug 236833.

Fortunately there's still hope for the dual menu button making its way to the core, because there seems to be some activity on bug 17796. Maybe it will see the light in Thunderbird 3, which will be released somewhere next year.

Yes! After one and a half month and a little bugging on #addons the Forward extension got reviewed, passed it and has now been made public. Hurray! Happy 4th of july!

You can view my public add-on now at: http://addons.mozilla.org/thunderbird/addon/7026

Review Information:
Reviewer: Archaeopteryx
Comments: Thank you for developing and submitting this useful extension. I got a memory alert, but this happened probably because the mail compose window in Tb2 leaks in general. Please check this with 3.0a2pre-Nightlies, there this shouldn't happen.

I'll check out the memory alert, when I find out how... Thank you Archaeopteryx for reviewing my extension

The next step is taken. I've nominated my add-on on AMO to become public.
I think it has been sandboxed/experimental long enough. Now let's see how long it will take to get to the top of the queue and what the editors think... I won't hold my breath though.

By adding my blog to my project's "What's new", I suddenly have a nice way to keep the list small and also have a history of changes. Only problem is that I didn't start out with the blog, so the oldest changes don't show up.

Hence this blog entry. I'll dive into the project pages to recreate the history...

The History of the Forward Extension, part I:

• April 15 - added forward to AMO
• March 28 - released forward 0.3 to mozdev, re-released old versions with corrected updateURL
• March 4 - released forward 0.2 to mozdev, based on feedback on 0.1
• March 2 - released forward 0.1 to mozdev and called for testers/reviewers on project_owners@mozdev.org

I'm still trying to find out how to best run this project website. Uptil now I didn't blog and didn't subscribe to blogs, just read them when I stumbled upon one.

Not sure about other people. Maybe nobody reads this, maybe some people do. It doesn't really matter. This extension is very small, website is very small, userbase is very small, but I do it for the fun. Let's hope I keep thinking blogging is fun and remember to add a blog entry whenever I change something. It offers an easy way to track changes that way...

Some days ago I unleashed the Forward extension to AMO. Those first few days are quite exciting. Will other people find my extension? Download it? Like it? Give feedback about it?

I spent much time behind the computer looking at the Statistics Dashboard.
One thing that kept bugging me, was that I noticed on the graph Add-on Version it listed version 0.1 next to version 0.3. What the heck? I didn't release version 0.1 to AMO. Did someone hack the version info? Are the stats wrong? What happened?

Than it struck me: the very first version I released to mozdev originally didn't have an updateURL in its install.rdf. I later on re-released that version, because I didn't want people to be left out on updates. But when an extension doesn't have an updateURL it goed checking with AMO.

Ah, well. Mystery solved. Let's hope the users who still have 0.1 upgrade to the latest and greatest version, otherwise they are left out of all the nice new features and bug fixes...