Community
Participate
Working Groups
esp if the actions are to become API. We shouldn't introduce new API based on older UI concepts.
removing milestone. Not a lot of bang for the buck here as most p2 actions are used in dialogs/buttons and therefore not contributed to anything that needs a command. We aren't exposing any further API in 3.5 and the main entry points to the UI (install new software, update) are commands. This may become more important if we choose to expose more detailed UI operations as API, in which case one way to protect the implementation would be to expose only command id's.
bulk update: UI bugs not yet assigned a milestone are returned to the inbox.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
There appears to be no pressing need to make changes in this regard.
