Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Artifact ID: | a1638b7901b8c7271d230d7293f9561f73e07f2d |
---|---|
Page Name: | Publishing a new release |
Date: | 2019-03-16 15:19:12 |
Original User: | tinus |
Mimetype: | text/x-markdown |
Parent: | 228f47ac8fc5a7f285f6f8c3badee4c665d4739b (diff) |
Next | 34ab186bba26af8a6db9ac8b263ca559ec5f623e |
Content
Releasing and publishing a new version
When creating a new release, a number of steps need to be followed:
Release
- 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.
- Check the version info, and update it if necessary.
- Save the entire code project
- Run the build.cmd batch script, and test the new DLLs (preferably both 32- and 64-bits)
- Run the 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
- 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.
- Close any tickets that have been fixed in this release, referencing the version number.
Publication
- Visit the Notepad++ Plugin Repository, and change this plugin's definition to match the new version.
- Post a message to the Notepad++ Plugin Development Forum. Make a new post, with the plugin name and version as subject. You can copy the information from the release notes, and don’t forget to include a download link to that specific version (e.g. http://fossil.2of4.net/npp_preview/zip/PreviewHTML.zip?uuid=v1.0.0.0-64).
Sources
- Top 10 Hints for Writing a Notepad++ Plugin, and Getting It Listed (Dave Brotherstone, 2012-08-20)