Test

Note that the `readme.txt` of the stable tag is the one that is considered t
he defining one for the plugin, so
if the `/tru* "Tags" is a comm=== Plugin Name ===
Contributors: (this should be a list of wordpress.org userid's)
Donate link: http:a separated list of tags that apply to the plugin
* "Requires at least" is the lowest vernk/readme.txt` file says that the stabl
e tag is `4.3`, then it is `/tags/4.3/readme.txt` that'll be used
for displaying information about the plugin. In this situation, the only thing
considered from the trunk `readme.txt`
is the stable tag pointer. Thus, if you develop in trunk, you can update the tr
unk `readme.txt` to reflect changes in
your in-development version, without having that information incorrectly disclos
ed about the current stable version
that lacks those changes -- as long as the trunk's `readme.txt` points to the co
rrect stable tag.ed up to: 3.4
Stable tag: 4.3
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Here is a short description of the plugin. This should be no more than 150 char
acters. No markup here.
== Description ==
This is the long description. No limit, and you can use Markdown (as well as in
the following sections).
For backwards compatibility, if this section is missing, the full length of the
short description will be used, and
Markdown parsed.
A few notes about the sections above:
* "Contributors" is a comma separated list of wordpress.org usernames
* "Tags" is a comm=== Plugin Name ===
Contributors: (this should be a list of wordpress.org userid's)
Donate link: http:a separated list of tags that apply to the plugin
* "Requires at least" is the lowest version that the plugin will work on
* "Tested up to" is the highest version that you've *successfully used to test
the plugin*. Note that it might work on
higher versions... this is just the highest one you've verified.
* Stable tag should indicate the Subversion "tag" of the latest stable version
, or "trunk," if you use `/trunk/` for
stable.
Note that the `readme.txt` of the stable tag is the one that is considered t
he defining one for the plugin, so
if the `/trunk/readme.txt` file says that the stable tag is `4.3`, then it is `/
tags/4.3/readme.txt` that'll be used
for displaying information about the plugin. In this situation, the only thing
considered from the trunk `readme.txt`
is the stable tag === Plugin Name ===
Contributors: (this should be a list of wordpress.org userid's)
Donate link: http:pointer. Thus, if you develop in trunk, you can update the tr
unk `readme.txt` to reflect changes in
your in-development version, without having that information incorrectly disclos
ed about the current stable version
that lacks those changes -- as long as the trunk's `readme.txt` points to the co

If no stable tag is provided. == Installation == This section describes how to install the plugin and get it working. `/assets/screenshot-1. o r install the plugin through the WordPress plugins screen directly.txt` is the stable tag=== Plugin Name === Contributors: (this should be a list of wordpress. your instructions match the desired user flow for activating a nd installing your plugin. in order to eliminate any doubt.3/readme. 2.as long as the trunk's `readme.rrect stable tag.txt` file says that the stable tag is `4.(png|jpg|jpeg|gif). you can update the t runk `readme. .0 = * A change since the previous version. In this situation.txt` points to the co rrect stable tag. For example. Include any steps that might be needed for explanator y purposes) == Frequently Asked Questions == = A question that someone might have = An answer to that question. This screen shot description corresponds to screenshot-1. = What about foo bar? = Answer to foo bar dilemma.txt (tags or trunk). jpeg. e. so if the `/trunk/readme. Upload the plugin files to the `/wp-content/plugins/plugin-name` directory.txt` of the stable tag is the one that is considered t he defining one for the plugin.txt` that'll be used for displaying information about the plugin.3`.png` would win ove r `/tags/4. Screenshots in the /assets directory take precedence. gif). Use the Settings->Plugin Name screen to configure the plugin 1. without having that information incorrectly disclos ed about the current stable version that lacks those changes -.png` (or jpg.org userid's) Donate link: http: pointer. Thus. 1. Activate the plugin through the 'Plugins' screen in WordPress 1. but you sh ould specify "trunk" if that's where you put the stable version. then it is `/ tags/4. Note that the screenshot is taken from the /assets directory or the directory that contains the stable readme. it is assumed that trunk is stable. This is the second screen shot == Changelog == = 1. if you develop in trunk.3/screenshot-1. (Make Note that the `readme.txt` to reflect changes in your in-development version.g. the only thing considered from the trunk `readme. 1. == Screenshots == 1.

== Upgrade Notice == = 1. = 0.5 = * List versions from most recent at top to oldest at bottom.0 = Upgrade notices describe the reason a user should upgrade. No more than 300 cha racters. .* Another change.