Comment 4 for bug 3882

> Are there other use cases that you can think of for
> why you'd want time-based or temporary package subscriptions?

I don't know, but that use case is broad. consider a person beeing in a large team (i.e. MOTU, core developer). maybe you can see something like a team status, but that includes too much information in general. these people should be interested to get a package built on all architectures, and be able to track the status until the package hits the archive on all architectures, plus a period where they are notified about new bug reports in those packages.

> It might be best to gather those in this bug report.

I'll keep the status on "need info", however I don't know what you would like to know about more ...