launchpad help|
Size: 1904
Comment:
|
Size: 2908
Comment: header and footer
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ~-[[FrontPage|Launchpad Help]] > [[GetInvolved]] > Beta testing -~ ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| = Introduction = |
|
| Line 3: | Line 9: |
| You can get access to the beta program by joining the [https://launchpad.net/~launchpad-beta-testers launchpad-beta-testers] team. There are close to 1,000 beta testers and we encourage enthusiastic users to join that team to get the very latest functionality in Launchpad. Find out [:JoiningLaunchpadBetaTesters how to join Launchpad beta testers]. | You can get access to the beta program by joining the [[JoiningLaunchpadBetaTesters| Launchpad beta testers]] team. There are close to 1,000 beta testers and we encourage enthusiastic users to join that team to get the very latest functionality in Launchpad. |
| Line 7: | Line 13: |
| Launchpad's edge environment generally runs the latest daily code from the Launchpad developers against the production database (real live data). | Launchpad's ```edge``` environment generally runs the latest daily code from the Launchpad developers against the production database (real live data). |
| Line 9: | Line 15: |
| Prefixing standard Launchpad address with ```edge.``` gets you to the edge environment. | Inserting "```edge.```" into any Launchpad URL gets you to the edge environment. So, by and large, the URLs are interchangeable. (Except, of course, when the url points at a new feature in edge.) |
| Line 11: | Line 17: |
| '''For example:''' ```bugs.edge.launchpad.net``` | '''For example:''' ```bugs.edge.launchpad.net```, or ```http://bugs.edge.launchpad.net/bugs/1``` |
| Line 13: | Line 19: |
| If you visit an edge URL but you're not a beta tester Launchpad will automatically redirect you to the standard Launchpad servers. | If you're a beta tester and you visit the normal launchpad.net production environment, you'll be redirected to the edge servers, unless you've specifically chosen to temporarily turn off that redirection off for a period of time, using the link on the front page at ```https://launchpad.net/```. |
| Line 15: | Line 21: |
| If you're a beta testers and you visit the normal launchpad.net production environment, you'll be redirected to the edge servers, unless you've specifically chosen to temporarily turn off that redirection off for a period of time, using the link at ```https://launchpad.net/```. | The edge servers are production servers in the sense that any modifications or updates made to your data in Launchpad through edge.launchpad.net affects the same production database that everybody else is using on plain launchpad.net. Using the [[http://bazaar-vcs.org|Bazaar]] version control system, the updates to the edge application servers are all automated and happen daily. |
| Line 17: | Line 23: |
| So, by and large, the URLs are interchangeable. | There is another test environment, '''staging.launchpad.net''', which operates under very different rules: the data on it is flushed out and replaced with a copy of the production database every few days. ```staging``` is useful if you want to experiment with a feature or to try to reproduce a bug without messing up real data. |
| Line 19: | Line 25: |
| The edge servers are production servers in the sense that any modifications or updates made to your data in Launchpad through edge.launchpad.net affects the same production database that everybody else is using on plain launchpad.net. Thanks to Bazaar, the updates to the edge application servers are all automated and happen daily. | '''dogfood.launchpad.net''' also has its own database, and you also should not put data into it that you want to keep. The code and content may changed without warning. As of March 2008 it's particularly used for testing Launchpad build infrastructure, and it has its own build slaves. |
| Line 24: | Line 30: |
= Become a beta tester! = Visit the [[http://launchpad.net/~launchpad-beta-testers/+members|Launchpad beta testers team page]] to apply to join! ~-[[GetInvovled| < Get Involved]]-~ |
Launchpad Help > GetInvolved > Beta testing
Introduction
The Launchpad team runs a continuous beta program, as well as special beta test campaigns.
You can get access to the beta program by joining the Launchpad beta testers team. There are close to 1,000 beta testers and we encourage enthusiastic users to join that team to get the very latest functionality in Launchpad.
Continuous "edge" beta testing
Launchpad's edge environment generally runs the latest daily code from the Launchpad developers against the production database (real live data).
Inserting "edge." into any Launchpad URL gets you to the edge environment. So, by and large, the URLs are interchangeable. (Except, of course, when the url points at a new feature in edge.)
For example: bugs.edge.launchpad.net, or http://bugs.edge.launchpad.net/bugs/1
If you're a beta tester and you visit the normal launchpad.net production environment, you'll be redirected to the edge servers, unless you've specifically chosen to temporarily turn off that redirection off for a period of time, using the link on the front page at https://launchpad.net/.
The edge servers are production servers in the sense that any modifications or updates made to your data in Launchpad through edge.launchpad.net affects the same production database that everybody else is using on plain launchpad.net. Using the Bazaar version control system, the updates to the edge application servers are all automated and happen daily.
There is another test environment, staging.launchpad.net, which operates under very different rules: the data on it is flushed out and replaced with a copy of the production database every few days. staging is useful if you want to experiment with a feature or to try to reproduce a bug without messing up real data.
dogfood.launchpad.net also has its own database, and you also should not put data into it that you want to keep. The code and content may changed without warning. As of March 2008 it's particularly used for testing Launchpad build infrastructure, and it has its own build slaves.
Special beta campaigns
We also run regular special beta campaigns where we ask our beta testers to try a specific feature that is in beta, and give us feedback, before we make that feature available to the wider user base. We aim to have one feature in special beta testing in each of our monthly release cycles.
Become a beta tester!
Visit the Launchpad beta testers team page to apply to join!
