Community
Participate
Working Groups
When I work on a task for many days, I usually attach the context to the repository on the end of each day I work on it. This is my case, but there would be other reasons for other people to do is. My idea is to make it mark the older contexts as "obsolete", since the latest one is what matters.
This should come for free once bug 152065 is done, but leaving open so that we ensure the attach UI allows marking obsoletion.
Please don't make contexts attached by other users obsolette. at least not by default.
There can be a checkbox in the attach context dialog saying something like: "Make other contexts obsolete?", whose state is persistent (so I won't have to select it every time). Or then, make obsolete only the contexts from the same user who is attaching it (makes more sense)?
I don't quite see the use case for this and wonder if adding this to the UI would result in more complication then help. Attached contexts are a snapshot of the state of the progress on the task at the time that the context was attached. As such I'm not sure they're ever 'obsolete', they're just not current. We just made some changes to make retrieving the most recent context easier (e.g. bug 179601), so is there still a need for this?
It is more a cosmetic matter, i.e., when you open the web ui and see that amount of attached contexts. Having all of them marked obsolete unless the latest, makes the page to display them on a strikethrough font and my eyes automatically ignore them. And yes, it is very low priority ;)
I don't think that we should do this automatically, but instead allow it to be controlled by the user as with a patch. Just as a patch can optionally deprecate another, so could a context. So I'll mark this as a duplicate of bug 152065 which is to provide marking patches obsolote. *** This bug has been marked as a duplicate of bug 152065 ***
