Creating a release series is somewhat confusing
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Edwin Grubbs | ||
Bug Description
This is a note to record a sub-optimal user experience.
I just registered a new Launchpad product (testdoc). In order to make 'bzr branch https:/
My initial thought was "Oh, this is a new product, so there's probably not a release series yet, I'll click on the link that saying 'Register a release series'". I clicked the link, filled in the form, specifying 'trunk' as the name, and then was told that there was already a release series called 'trunk'.
So I went back to the Product Overview page where I saw a "Timeline" section, which has a single item "trunk" with "Releases: none" and "Milestones: none". I'm still not sure what a timeline is in this context, but I guessed that this is the release series.
I then clicked "Change source" (which is the closest thing to 'link to a branch'), and filled out the form, which did what I wanted.
The bug is that it's not clear that a product gets a release series as soon as it's created, nor is it clear how to change that release series.
See also bug 174468.
| David Allouche (ddaa) wrote | #1 |
| Changed in launchpad: | |
| importance: | Undecided → Medium |
| status: | Unconfirmed → Confirmed |
| description: | updated |
| affects: | launchpad-foundations → launchpad-registry |
| Changed in launchpad-registry: | |
| assignee: | nobody → Edwin Grubbs (edwin-grubbs) |
| Curtis Hovey (sinzui) wrote | #2 |
| Changed in launchpad-registry: | |
| importance: | Medium → Low |
| Edwin Grubbs (edwin-grubbs) wrote | #3 |
| Changed in launchpad-registry: | |
| status: | Triaged → Fix Released |
Agreed. When approving imports, I occasionally (rarely, but more than once) see that the user has created an unnecessary series such as "main" or "0.9" when using the trunk series would have been sufficient.
In the past, I argued that the series created when the product is created should be implicit, and that releases, imports, etc. that hang off this series should appear to the user as if they were associated to the product itself. So projects that just do everything off trunk (most small projects do) would not even need to know about series at all.
There might be a simpler way to fix the confusing though.