One of the important features we want to support in intrepid is out-of-the-box 3g support.

Now that Network Manager 0.7 has entered the archive, I’d like to to ask you to test your 3g hardware with it and report your findings to the 3G Hardware page on the wiki. We want to hear about all results – good and bad ones. Just remember to open a bug in launchpad and link it to your result on that wiki page.

How to test

If you are running intrepid, you just need to apt-get upgrade to get the current network-manager 0.7. Alternatively, you can also use the Network Manager PPA which usually has even more recent snapshots in it.

If you are using hardy, the PPA is currently the only source to track network manager 0.7 progress in ubuntu.

Edit: Finally, the latest daily intrepid livecd’s come with NetworkManager 0.7. Please test them as well.

Known issues

1. We have dropped all driver tweaks for now. This means you most likely see regressions with orinoco and madwifi/ath drivers.
2. /etc/network/interfaces is currently not recognized. Better remove all entries (except the “iface lo” one) from it to avoid confusing behaviour. The long term idea is to provide legacy backend for network-manager that parses your /etc/network/interfaces as good as possible. If thats not enough for some you probably will have to uninstall network-manager. In case our legacy backend will not reach a stable enough state for intrepid, we might go back to the dumb “blacklisting” approach we used in hardy.
3. network manager applet has no UI to disconnect a particular interface. So do not get confused if you suddenly are connected to wired and wireless at the same time.
4. VPN plugins are not yet available. I added an initial package for the openvpn plugin to the Network Manager PPA (intrepid only) for now. Once I have good feedback I will do the same for the other vpn variants and eventually upload those packages to the real archive.

How to report bugs

To file a bug, please follow the instructions below and file a bug using this link.

In general, Network Manager 0.7 bugs should have the word “0.7” in their bug summary, so I can easily filter them out.

If you encoutner connectivity issues with Network Manager 0.7 and your wifi/wired setup, please attach your complete syslog taken after you reproduced your issue.

If you are having 3g issues, please attach the complete output of lshal as well.

Please remember to search the current network-manager bugs to avoid filing duplicates. However, if in doubt, open a new bug rather than adding information to potential duplicates. Just name the bug you think you might see a dupe off in your new bug; we will sort them out properly.

A few days ago, the ubuntu mozilla-extension-dev team published their first monthly report for Jul 08.

Thanks for all contributors that helped us to get where we are.

If you are interested in helping out on extensions, read the extensions team wiki page and start to lurk on #ubuntu-mozillateam on irc.freenode.net, our team will be surely be happy to help you and answer your questions.

Hi again,

first I would like to thank all that helped out testing the ffox 2.0.0.15
security updates a few weeks ago. We now have new batch of firefox
security updates going out soon. Please help testing them and give us
feedback through the mozilla qa tracker (http://mozilla.qa.ubuntu.com).

As usual, we need testers for all supported ubuntu releases. Those are:

+ dapper – firefox 1.5 + feisty – firefox 2 + gutsy – firefox 2 + hardy – firefox 3

To participate, visit the mozilla qa site (http://mozilla.qa.ubuntu.com)
and click on the package version you want to test and submit results for
the test-cases listed there.

The built packages are available from my PPA and you can find
instructions and the sources.list entries required on top of the
mozilla QA tracker page.

If you don’t have a native install of the above ubuntu releases, using a
VM or chroot is perfectly fine as well. Instructions on how to setup
VirtualBox can be found at: https://help.ubuntu.com/community/VirtualBox.

As usual we expect it to be quite difficult to find testers for dapper,
feisty and gutsy. So if you have a few spare cycles and want to make a
difference, jump in, setup a VM and help out!

As always, in case you have questions or run into issues, feel free to
ask on #ubuntu-mozillateam or #ubuntu-testing on irc.freenode.net.

Thanks in advance for your help and happy testing!

– Alexander (asac)

NetworkManager 0.7 is back. So far I received good feedback on this snapshot, so I thought it was time to get more testers involved.

To get the packages, add the network-manager team PPA to your sources.list and upgrade your system:

https://launchpad.net/~network-manager/+archive

Enjoy and remember to let me know what works and what doesnt!

Update: If you end up having two wpa_supplicant processes running (after resume) just sudo killall wpa_supplicant and all should be back to normal.

mozilla is preparing an update for their firefox 2.0 product and the Ubuntu MozillaTeam [0] needs you to test the ubuntu candidate builds [1].

The testing is done by running a test plan [3] and submitting the results to the mozilla QA site [1]; in addition, just use the builds and look for regressions while doing your daily work.

If you need help, just join #ubuntu-testing or #ubuntu-mozillateam on irc.freenode.net and ask your questions.

Thanks a lot!

– Alexander

Note: We are looking for new testers on all supported ubuntu releases. That’s currently dapper, feisty, gutsy and hardy. In particular we have a lack of dapper and feisty testers and your contribution on testing those releases would be highly appreciated. So, if you want to help, but don’t have such a system installed (anymore), consider to setup a chroot or a VM (try virtualbox [2]).

[0] – https://wiki.ubuntu.com/MozillaTeam/
[1] – http://mozilla.qa.ubuntu.com
[2] – virtual box instructions are https://help.ubuntu.com/community/VirtualBox and https://wiki.ubuntu.com/Testing/VirtualBox
[3] – Testplan: https://wiki.ubuntu.com/MozillaTeam/QA

UPDATE: – I found out, that this mail went out to much more than just those who previously have contributed to the ubuntu QA tracker. I am sorry and apologize for hitting the wrong button. To compensate you for this minor annoyance, I offer free hugs in #ubuntu-mozillateam (just today) to everyone who received this mail by accident and shows up

Hi,

I feel thrilled to re-announce that we have a Ubuntu MozillaTeam meeting in #ubuntu-meeting on irc.freenode.net today!

The meeting starts at 1800 UTC and we have a proposed Agenda. If you have anything mozilla related you would like to discuss during the meeting, go ahead and add your agenda item to that list.

cu in a few.

In case you didn’t notice: firefox 3 was just released to the world and to hardy-updates.

Champagne!

Some might have read the breathtaking news; if not, here the delicious announcement: http://developer.mozilla.org/devnews/index.php/2008/06/11/coming-tuesday-june-17th-firefox-3/. Rock on Mozilla!

@ubuntu: help and test our packages in hardy-proposed now … if all goes well we might be a able to get those bits to hardy-updates on the same day.

Otherwise, prepare for party!

you can get and test this milestone now by running

1. intrepid
2. hardy-proposed
3. or the ubuntu mozillateam hardy ppa

If you run into regressions, please open a new bug and drop a short note about your bug in the firefox 3 rc2 upgrade bug.

Many thanks for testing

Here some good news for all of you waiting for the firefox 3 RC1 upgrade in hardy …

“Today, we finished the verification process and copied firefox 3 RC1 from hardy-proposed to hardy-updates!”

Thanks to everyone involved in this update. Also, many thanks to all the (brave) users that supported us by testing these packages while they waited in hardy-proposed!

In the unlikely case that you get to know about a regression, please file a bug against firefox-3.0 or the xulrunner-1.9 package and let the ubuntu mozillateam know directly.

Thanks for your support (and patience). Enjoy!

Almost all bits required for the firefox 3/xulrunner 1.9 rc1 transition are now available for pre-testing in the mozillateam ppa.

If you end up without your preferred translation you might also want to grab your langpacks from the ubuntu langpack ppa.

Next steps are: (hopefully tomorrow) push all bits to hardy-proposed; do thorough QA for about a week and finally release everything to hardy-updates.

Have fun!

Hi,

as you might know we have a feature freeze exception to update firefox 3 extensions even though we are close to the release.

However, as we get closer to the release, even extension updates become risky; so please submit your extension packages to the ubuntu mozillateam by the end of this week (Sat 5 Apr).

Please remember to add your extension to https://wiki.ubuntu.com/MozillaTeam/Firefox3Extensions and use the https://wiki.ubuntu.com/MozillaTeam/Firefox3Extensions/Packaging to get an idea about extension packaging best-practices in hardy.

The firefox-extension project in launchpad already has a bunch of bzr branches that you can use as a starting point on how to do this in practice. Remember to file a firefox-extensions bug asking for review and/or sponsorship. Remember to follow up if we ask for improvements or clarifications.

If you need support packaging your extension, ask for help in #ubuntu-mozillateam on freenode. Remember to be patient in case we don’t answer right away as we might be busy or away from keyboard.

Happy packaging!

its time for a next round of firefox security release testing .

Any feedback gathered from real installs, chroots or VMs is helpful and highly appreciated.

Note: We still need more dapper testers. So if you don’t have a dapper install at hand, but want to help improving the quality of our LTS release considerably, its time to setup a chroot or VM and start help out on dapper QA.

If you have questions about beta testing applications in general or this specific firefox release, feel free to get in touch with me (asac in #ubuntu-mozillateam) or henrik (heno in #ubuntu-testing).

References:

1. The tracker page – coordinates QA:
   => http://mozilla.qa.ubuntu.com/
2. Documentation on how to setup a VM using virtual box:
   => https://wiki.ubuntu.com/Testing/VirtualBox

Thanks and Happy Testing!

Last minute reminder: we have a firefox 3 extension packaging session in #ubuntu-classroom at 1600 UTC today (about 1 hour from now).

This session is great for starters as well as for skilled packagers that want to help getting more extensions into ubuntu.

I have prepared some content that you don’t read in advance (of course you can ). Instead I will cite them during the session. So, here the content:

• https://wiki.ubuntu.com/MozillaTeam/Firefox3Extensions/Packaging – some extension packaging details
• https://wiki.ubuntu.com/MozillaTeam/Firefox3Extensions/ – page to keep important information about proposed extensions

Note: The packaging page above requires a mozilla-devscript package version that isn’t in the archive yet. You can get it from my PPA for now: https://edge.launchpad.net/~asac/+archive

See you all in a few minutes!