modelling 'release of X depends on Y being released' is hard/impossible

Bug #796197 reported by Fabian Thoma
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Milestones in Launchpad should have the ability to base on other milestones, even milestones from compleatly different projects, let me present a use case example:
an Application uses a library and waits for the library to get it's next stable Release out, so it adds a dependency to it's own milestone, so they actually see everything they need to do or are waiting for in one view.
The same goes for the elementary Project, we want our next release "Luna" to wait on a couple of things, so we would just add all the milestones we need to reach to release the next os version to the os milestone itself, that way we'd have a great overview over the tasks we need to still do.

Revision history for this message
Robert Collins (lifeless) wrote :

Hi, I think we'd generally encourage modelling that as a bug for the milestone; that said bugs don't (yet) have dependencies nor do they permit the dependency to be the release of another project. Clearly they should!

We've no immediate plans to work on your bug, and it wouldn't be all that easy - but if you or someone else wish to hack on it, we will help with design and review :)

Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
summary: - milestone dependencies
+ modelling 'release of X depends on Y being released' is hard/impossible
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.