launchpad help|
Size: 2644
Comment: 1910 members in the bt team at the time of editing
|
← Revision 25 as of 2010-11-11 19:37:26 ⇥
Size: 1879
Comment: s/edge//
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| = Continuous "edge" beta testing = | = Continuous beta testing = |
| Line 13: | Line 13: |
| Launchpad's ```edge``` environment generally runs the latest daily code from the Launchpad developers against the production database (real live data). | Launchpad deploys new features in a limited fashion by only showing them to members of the beta testers team. For members of the team, no special actions are needed - the new features are immediately available. |
| Line 15: | Line 15: |
| 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.) | == Test environments == |
| Line 17: | Line 17: |
| '''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 [[http://bazaar-vcs.org|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. |
There is are two test environments, '''staging.launchpad.net''' and '''qastaging.launchpad.net''' which contain a copy of the Launchpad data and newer code. The '''staging''' server additionally has any database changes which we are testing out on in. The databases for these test environments are reset approximately weekly. ```staging``` or ```qastaging``` are useful if you want to experiment with a feature or to try to reproduce a bug without messing up real data. |
Launchpad Help > Get involved > 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 2,000 beta testers and we encourage enthusiastic users to join that team to get the very latest functionality in Launchpad.
Continuous beta testing
Launchpad deploys new features in a limited fashion by only showing them to members of the beta testers team. For members of the team, no special actions are needed - the new features are immediately available.
Test environments
There is are two test environments, staging.launchpad.net and qastaging.launchpad.net which contain a copy of the Launchpad data and newer code. The staging server additionally has any database changes which we are testing out on in. The databases for these test environments are reset approximately weekly. staging or qastaging are useful if you want to experiment with a feature or to try to reproduce a bug without messing up real data.
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!
