docs: update changelog and development release steps

CHANGELOG.md

@@ -4,6 +4,16 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com) and follows semantic Versioning.
 
+## [Unreleased]
+
+Thank you to the collaborators on this release:
+
+- [@eeddaann](https://github.com/eeddaann)
+
+### Added
+
+- added support for Grafana annotations
+
 ## [3.3.3] - 2023-07-21
 
 ### Changed

DEVELOPMENT.md

@@ -70,9 +70,8 @@ On MacOs you can use the preinstalled "screen sharing" application as a VNC view
 After step 3 Github Actions should take over and create a new release.
 Steps 4 and 5 are for publishing the release to Grafana repository.
 
-1. Update the Changelog and the package.json
-2. Tag the commit with a Semver tag, e.g. v2.2.3-rc.1
-3. Push the changes including the tag
-4. Get the md5 hash of the release from the Github Action or from the release page (text file)
-5. Within the Grafana Cloud account a request for a plugin update can be started:
+1. Make sure a section in the Changelog exists with `## [Unreleased]`
+2. Push the changes and merge to the default branch
+3. Get the md5 hash of the release from the Github Action or from the release page (text file)
+4. Within the Grafana Cloud account a request for a plugin update can be started:
    <https://grafana.com/orgs/frser/plugins>