Confirm
3,816
edits
Changes
→Calendar Community Questions and Answers
1. What are the differences between nightly and release update?
* blahNone really, except for the difference in channel and business logic surrounding non-linear updates. Perhaps you can clarify this question a little?
2. What is Patcher2 needed for? Does it generate a special type of MAR file for release update?
* Patcher2 is the "patcher script" mentioned above. It is a script that takes all the locales for a release and creates partials and completes and snippets for all of these builds and then puts that information onto the AUS staging server so that each locale will be properly updated. I.e. This way an Italian build won't be served an update to an English build.
3. Where are the update files for releases stored?
* Completes (MARs) are stored on the FTP site with the build executables since they are built by the build system. Partials are stored on the AUS staging server.
4. Do we have to change some config in Sunbird for release updates?
* You can diff the fx configs between a nightly and a release and see the difference. There are some differences in the mozconfig file that are done at build time to change items like the release channel. You can diff files between:
** /mozilla/tools/tinderbox-configs/firefox/os
** /MOZILLA_1_8_BRANCH_release/tinderbox-configs/firefox/os
You can see similar differences for Sunbird by replacing sunbird with firefox. (TODO: Bonsai query for this diff on Sunbird)
5. Will the community AUS2 server be in place or have at least an address to configure Sunbird 0.7 in time (September/beginning of October) for the next release update (0.7 -> 0.9)?
* Yes, it should be. The "server" is actually a server with a set of Virtual Machines on it. Our community machine for Sunbird is one of these Virtual Machines. There is a set of things that need to be done: SSL certificates, some holes punched in firewalls etc. Preed and I will take this up with IT here and work on getting these issues addressed before 0.7.
6. Public address? How do we access it? Who will maintain it? Do we have community access (-> ause?) Do we have support from #build or mozilla.org if there is an issue? For example who does security updates for the server?
* Yes, the public address will be accessible. Access to our VM will be given out to a few people in the Sunbird community. Ause will of course be one. We need to decide who else really needs SSH access to it. We have support from the mozilla build team for build-related issues. For overall server issues, we will need to file an IT bug with the Mozilla IT team (For instance, if the entire server crashes, has an issue with a firewall etc). As far as security updates and patches to the VM are concerned, that is our (sunbird community) responsibility. However, it is recommended that we stay as close to the standard build reference platform so that if we need to pull the build team in to work on an issue, they are dealing with a known quantity.
7. Nightly updates (after changing the URL in Sunbird) 9. : Special configuration required on the AUS server to support nightly updates? How do we need to configure the tinderbox to upload the update information to the new server? Possibility to hook it up to <http://update-watch.localgho.st/nightly/production/latest/>? ===Update 0.5 release * Once we have configured the community server and the patcher to watch this FTP site to generate snippets to 0.7 release=== 10. We need post to use the official AUS server for our staging area on our VM, then thisshould be pretty simple. Who will take care of this? How do we create and test Since Patcher watches the update packages for all platforms x 22 locales? What tools do FTP location itself, as far as I understand, we shouldn't need etc.? ..to change anything on the tinderbox.
8. Update 0.5 release to 0.7 -> release: We need to use the official AUS server for this. Who will take care of this? How do we create and test the update packages for all platforms x 22 locales? What tools do we need etc.? ...* In order to upgrade users from 0.5 to 0.9 7 (since the AUS server changes between these two versions) we will need to have help from Mozilla for this. Here is how it will work:** On the old AUS server we will post the MAR and partial so that users will upgrade directly to 0.7*** We will need help from preed and rhelmer for the build/server side of this, and if something goes wrong, we'll probably need to get help from sspitzer to give us a hand diagnosing issues on the client side. ** After the upgrade to 0.7, the users will be on the new AUS server and they will be using that server from then on.** Ideally after this update, the users will remain on the same channel that they were on in 0.5, which for these folks will be the releasechannel.
9. Update 0.7 -> 0.9 release: Are the tools for package creation and testing public available so that we can do the release ourself? ...* Yes...sort of. Preed is going to look into getting us some configs and access to the patcher scripts that we'll need. Most everything else is available or can be made available. He really needs some help to make the updates and the update process extendable to the myriad of Mozilla community projects, and if someone from the calendar community can step up to help with that work (Ause?) that would be a huge help.* I (ctalbert) am still working on a wiki page to detail our build process so that we can easily create a build for this next release. I plan to work with Ause on this in more detail in the coming weeks. If we find that we lack access to any necessary tool or script, we'll raise that issue with the build team and get the problem addressed.
