From 2bb37499c177846226b012aa34566e82fcd5d8a0 Mon Sep 17 00:00:00 2001
From: frank goossens <futtta@gmail.com>
Date: Sat, 13 Mar 2021 11:02:16 +0100
Subject: [PATCH] final beta of 2.8.2?

---
 autoptimize.php |  4 ++--
 contributing.md | 20 ++++++++++++++++++++
 2 files changed, 22 insertions(+), 2 deletions(-)
 create mode 100644 contributing.md

diff --git a/autoptimize.php b/autoptimize.php
index 8ae30da6..4a92d69e 100644
--- a/autoptimize.php
+++ b/autoptimize.php
@@ -3,7 +3,7 @@
  * Plugin Name: Autoptimize
  * Plugin URI: https://autoptimize.com/
  * Description: Makes your site faster by optimizing CSS, JS, Images, Google fonts and more.
- * Version: 2.8.2-beta-3
+ * Version: 2.8.2-beta-4
  * Author: Frank Goossens (futtta)
  * Author URI: https://autoptimize.com/
  * Text Domain: autoptimize
@@ -21,7 +21,7 @@
     exit;
 }
 
-define( 'AUTOPTIMIZE_PLUGIN_VERSION', '2.8.2-beta-3' );
+define( 'AUTOPTIMIZE_PLUGIN_VERSION', '2.8.2-beta-4' );
 
 // plugin_dir_path() returns the trailing slash!
 define( 'AUTOPTIMIZE_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
diff --git a/contributing.md b/contributing.md
new file mode 100644
index 00000000..9e3fd7bb
--- /dev/null
+++ b/contributing.md
@@ -0,0 +1,20 @@
+Issues
+==
+If you are a plugin user who has problems configuring Autoptimize (your site breaking in some way when activating AO) **the place to get help is [the Autoptimize support forum at wordpress.org](https://wordpress.org/support/plugin/autoptimize/)**.
+
+If you are a developer and you think you discovered a bug in the code or if you have ideas for improvements, create an issue here on Github with a clear technical description.
+
+If you are both developer & plugin user the choice is yours (it really depends on what type of support you need) ;-)
+
+Pull requests
+==
+PR's are enthousiastically welcomed!
+
+For optimal efficiency please take the following things into account:
+1. use the **beta** branch as master is frozen to be at the same level as the current version on wordpress.org.
+2. test your changes not only functionally, but also using the **unit tests** available (running `composer test` after having done `composer install` and running `bin/install-wp-tests.sh`)
+3. (new) code is supposed to follow the WordPress code guidelines, test using **phpcs** (install with `composer install` and then run `vendor/squizlabs/bin/phpcs` against your changed/ added file
+
+When in doubt or in need of guidance/ help create an issue describing what you would like to change and we'll figure it out! :-)
+
+Frank