Very difficult to create a recipe targeted to a new archive
Bug #670440 reported by
Jonathan Lange
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Tim Penhey |
Bug Description
There's no way to create a PPA (or a new team for a PPA) when creating a recipe. This is a fairly common case, because most projects do not have a daily build, and presumably many projects would want their daily build in a new PPA.
Here's what you have to do now:
1. Open a new tab and go to https:/
2. Create a new team
3. Create a PPA for that team.
4. Once done, switch back to the recipe tab and reload to get the new PPA in the choice box.
If the new team and the new PPA could be created inline, probably using AJAX and morphing dialogs, then the recipe creation experience would be vastly improved
Related branches
lp:~thumper/launchpad/recipe-new-ppa
- Henning Eggers (community): Approve (ui)
- Graham Binns (community): Approve (code)
-
Diff: 742 lines (+425/-51)11 files modifiedlib/canonical/launchpad/testing/pages.py (+18/-8)
lib/lp/app/browser/launchpadform.py (+20/-0)
lib/lp/app/templates/base-layout-macros.pt (+3/-0)
lib/lp/code/browser/sourcepackagerecipe.py (+86/-10)
lib/lp/code/browser/tests/test_sourcepackagerecipe.py (+128/-0)
lib/lp/code/javascript/sourcepackagerecipe.new.js (+56/-0)
lib/lp/code/model/sourcepackagerecipe.py (+4/-1)
lib/lp/code/templates/sourcepackagerecipe-new.pt (+85/-2)
lib/lp/registry/browser/productseries.py (+12/-23)
lib/lp/soyuz/model/archive.py (+1/-1)
lib/lp/testing/__init__.py (+12/-6)
Changed in launchpad-code: | |
status: | Triaged → In Progress |
assignee: | nobody → Tim Penhey (thumper) |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
Changed in launchpad: | |
milestone: | none → 11.01 |
To post a comment you must log in.
While I do think that this is important, I think that this is asking a bit too much to have in the new recipe form, especially given that we don't have any morphing ajax dialogs.
I agree that having morphing dialogs would vastly improve the experience, but I'm not happy blocking the general release of this feature on that.