Idea: Have a RFC's and pre-release feedback section in monthly update

[hmistry]

In the monthly bundler updates, it might be a good idea to mention in outstanding RFC's that are in need of feedback with a due date (can always be extended, never pulled in). This another marketing channel to tap to get the word out there periodically and remind users about it. Hopefully it will reduce reactions like we saw on Twitter recently as there would have been ~10 monthly notifications since the RFC (assuming we sent an update every month).

Similarly, for beta and pre-release versions where you're looking for users to test it and provide feedback.

cc: @indirect @rubymorillo

[indirect]

I really like this idea, thanks!

[rubymorillo]

@hmistry this is a great idea! We'll definitely add this in.

[hmistry]

Also it'd be good to quantify things a little like: "we are looking for total of 100 users testing on large projects with Gemfiles of 100+ gems" or "we got 5 user feedback last month, and we'd like another 20 more before release".

Something like that creates more incentive if I'm a potential candidate to help out as I know I'm not wasting my time or presume that many others are helping out when they're not.

This is more work but I thought if there was a feedback form for users to submit to get following info then we're not guessing (I don't think we're collecting any analytics or crash reports):

I tested bundler v2.0.beta1 with 78 gems on ruby v2.4.1 on macOS and used the following commands:
- install -> worked # this can be a simple checkbox thing
- deploy ->failed # give link to submit issue on Github
- add -> n/a
...

Other feedback: ...

[rubymorillo]

Revisiting this again. So far, I've mentioned the RFC once in a monthly update, but not with the level of detail above. @indirect @colby-swandale what do y'all think?