releases explained

Author: JohnRDOrazio

README.md

@@ -171,3 +171,30 @@ The clock can be styled accordingly in one's own stylesheet. Some sample styling
   .clockdate { color: DarkRed; margin-bottom: 10px; font-size: 18px; display: block;}
   .clocktime { border: 2px inset White; background: Black; padding: 5px; font-size: 14px; font-family: "Courier"; color: LightGreen; margin: 2px; display: block; }
 ```
+
+# Releases
+
+Newer releases don't necessarily mean better, it really depends on what you are expecting to get out of this plugin. So here is a quick overview of the releases so you can decide for yourself which version might best suit your needs.
+
+## v2.0.2
+
+This captures the state of the first version of the plugin, which allows for dynamically adding one's own locale translations.
+The output format of the date and the time are fixed and do not support short weekdays or short months.
+Can take a custom timestamp; if the timestamp is server generated it may have to be multiplied by 1000 to account for milliseconds.
+This version of the plugin doesn't do anything to account for timezone offsets, which means that the clock's time may not reflect the server's timezone time.
+Direct link: [v2.0.2](https://github.com/Lwangaman/jQuery-Clock-Plugin/releases/tag/v2.0.2)
+
+## v2.0.9b
+
+Version 2.0.9 fixes the problems which arise from the timezone offsets. In order to faithfully reflect the server's timestamp in UTC time, the plugin corrects the client timezone offset so that it the clock's time will reflect UTC time. However if the server has set a timezone offset from UTC time, this will need to be accounted for server-side before passing the timestamp to the plugin.
+Seeing that this process only needs to take place when a server-generated timestamp is being passed in, this version of the plugin detects if the timestamp is server-generated by checking whether it takes into account milliseconds or not. This means we no longer multiply the server-generated timestamp by 1000 before passing it to the plugin, the plugin will use that information to determine that the timestamp was server-generated and will thus account for client timezone offsets.
+The tag was renamed 2.0.9b because I forgot to update the minified version the first time; 2.0.9b has an updated minified javascript file.
+Direct link: [v2.0.9b](https://github.com/Lwangaman/jQuery-Clock-Plugin/releases/tag/v2.0.9b)
+
+## v2.1.0b
+
+Version 2.1.0 adds the short version of weekdays and months to the supported locales. Note that the currently supported locales do not guarantee linguistic correctness, the stored values for shortened months and weekdays are guesswork and are not based on any kind of standard usage.
+This version also introduces PHP style date and time formatting. This gives the end user more flexibility in choosing how the date and time should appear on the clock. This also means that some option parameters that existed in previous versions have been deprecated, such as the "format" parameter which let the user choose between 12 and 24 hour format, the "seconds" parameter which let the user choose whether to display seconds or not; at the same time more option paramters are added such as "dateFormat" and "timeFormat" which recognize a number of PHP style format characters.
+Again the tag was renamed 2.1.0b because the javascript was not initially minified.
+Direct link: [v2.1.0b](https://github.com/Lwangaman/jQuery-Clock-Plugin/releases/tag/v2.1.0b)
+