Plan / Package subscription feature for Builder

[predominant]

Describe the Enhancement:

Allow users to opt in for notifications / alerts about activity on a plan.

Describe the Need:

This is universally useful to all users on any builder instance. Users that want to be notified of new builds available, new promoted packages, or special notifications regarding the package can be reached via this system.

General user benefits:

• Get notified about selected events for selected plans:
• Just promotion notifications on core/glibc
• All new builds for myapp/backend
• Receive special announcements regarding subscribed packages

Administrator / plan author benefits:

• Reach users for breaking changes
• This is a big need in core-plans at the moment
• A way to send notifications (optionally emails, based on user preference?) when breaking changes are coming through the pipeline

Notification Levels

I can see this being useful, but also noisy. Package notification is going to have to be a tiered thing. Much like the way Github allows increasingly noisy notifications to be sent to users based on their preferences for a repo.

Increasing, such as:

• Breaking changes
• Only Promotions to stable
• All promotions (any channel)
• All builds

Current Alternative

No current alternative

Can We Help You Implement This?:

I'm relatively busy on other community bits. And am not as confident as I need to be with my Rust level of skill as yet to contribute to this, personally.

Aha! Link: https://chef.aha.io/features/APPDL-11

[Defilan]

This is a FANTASTIC idea and very much needed. We should not expect casual users of Habitat to be reading each minute detail of every PR that comes through. Great idea @predominant !!!

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[eeyun]

Stalebot, more like... jerkbot, amirite... ?

Er... Obviously we have a lot of issues in this area. Leaving a comment as we're starting into discovery on this.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[sajjaphani]

This isn't stale

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale[bot]]

This issue has been automatically closed after being stale for 400 days. We still value your input and contribution. Please re-open the issue if desired and leave a comment with details.