# Releasing and publishing a new version

When creating a new release, a number of steps need to be followed:

## Release

1. If there are code changes, commit those first, as a regular commit. If this commit fixes any tickets, add a reference to those tickets' uuids in brackets.
2. Check the version info, and update it if necessary.
3. Save the entire code project
4. Run the [build.cmd](./finfo?name=build.cmd) batch script, and test the new DLLs (preferably both 32- and 64-bits)
5. Run the [publish.cmd](./finfo?name=publish.cmd) batch script.
  * It will build both 32- and 64-bits versions of the DLL.
  * It will ask to update the release notes [ReleaseNotes.txt](./finfo?name=ReleaseNotes.txt)
  * It will commit the updated DLLs (and release notes) to the respective release brances.
    Ideally, the commit message should only consist of the version number.
6. Close any tickets that have been fixed in this release, referencing the version number.

## Publication

1. Post a message to the [Notepad++ Plugin Development Make a new topic, with the plugin name and version as subject. You can copy the information from the release notes, and don’t forget to include download links to that specific version (e.g.
2. Fork the repository, update the PreviewHTML’s `version`, `repository` and `id` fields in both json files, and make a pull request.
3. Visit the [Notepad++ Plugin and change [this plugin's to match the new version.

### Sources

* [Top 10 Hints for Writing a Notepad++ Plugin, and Getting It (Dave Brotherstone, 2012-08-20)