Notice: Planned Repository cleaning

[chriscct7]

Now that development of the next generation of this plugin is reaching a critical point, we're going to circle back and clean up this repo and organize it a bit.

If you're reading this, it's likely because your ticket was linked and closed with this issue as a comment.

What this means is:

If your reported issue was a bug:

• We tested the issue and either confirmed it doesn't exist OR
• Have fixed it in our next major release (6.0) OR
• Have decided not to fix it (possibly a bug in a newly deprecated feature or not something worth fixing for another reason) OR
• Have it logged for a future milestone OR

If your reported issue was an enhancement or a feature request:

• We evaluated it and included it in the next major release (6.0) or scheduled it for a future major release OR
• Have decided not to do it
• Or set it to a maybelater status

If you'd like more information on the status of a particular issue, feel free to comment on that issue.

In any case, we have gone through and done a thorough evaluation of all of the tickets closed. As a result, if you have opened many tickets in the past, you may have gotten several email notifications from GitHub this weekend. Many of you will find your requested features/enhancements in the next major release or your reported bugs have been fixed. This upcoming 6.0 release is pretty awesome :)

Please continue to open bug reports & feature requests here.

If you need to report a security issue, please email us at support@monsterinsights.com.

For lite (free version) support, please use the WordPress.org forums. For Pro (paid version) support, please use the support form located in the My Account area of monsterinsights.com (it's one of the tabs on that page after you log in).

This repo will continue to be re-organized and updated quite significantly before the 6.0 launch.

[chriscct7]

Closing as the team has completed evaluating all open issues.