want a way to lock/embargo/privatize releases and downloads

Bug #422902 reported by Martin Pool
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Unassigned

Bug Description

It would sometimes be useful to make a release and its download files not publicly accessible, somewhat similarly to the embargo feature on announcements. A couple of cases:

1- We want to announce and generally recommend the release when binaries for all platforms have been built. Various people build the binaries and upload them over several days. It may cause user confusion if the current release doesn't have a full set of binaries yet.

2- If we discover a release is seriously buggy, we might want to disable access to it. At the moment the only option is to delete all the files. It would be nice to block access (possibly with a 'yes, really' link), showing a project-provided message.

In either case:

- project team members should still have access
- there should be a prominent decoration (as for private objects) that the release is not visible

Possibly this is just that releases should have a privacy bit, though the case of withdrawn releases seems different.

Martin Pool (mbp)
summary: - want a way to lock/embargo releases and downloads
+ want a way to lock/embargo/privatize releases and downloads
Curtis Hovey (sinzui)
Changed in launchpad-registry:
status: New → Triaged
importance: Undecided → Low
tags: added: feature
Curtis Hovey (sinzui)
tags: added: private-projects
Curtis Hovey (sinzui)
tags: removed: feature
tags: added: feature
Curtis Hovey (sinzui)
Changed in launchpad:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.