github/greenshot
1
0
Fork 0
mirror of https://github.com/greenshot/greenshot synced 2025-08-23 22:56:19 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update 2025-05-20-working-towards-greenshot-1-3.markdown

Browse source
This commit is contained in:
jklingen 2025-05-21 18:58:25 +02:00 • committed by GitHub
commit 4e8cf83d40
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
_posts/2025-05-20-working-towards-greenshot-1-3.markdown
View file

@ -10,13 +10,13 @@ tags:
Long time no see... in our [last blog post](/2024/02/11/current-status-greenshot/) we explained why the project activity had slowed down so much, and that we're working on getting development up and running again. That was quite some time ago 🙈 Now we have some news to share:
### Code Signing Up and Running
#### Code Signing Up and Running
Finally, we are able to create signed releases again 🎉 it took quite some time and effort, and we have learned that code signing for Windows is much more complicated than it was just a few years ago. This step is crucial in our mission, and the basis for the next steps to come.
For starters, we have recently released a signed installer of the current unstable version (1.3.281), you can find it on our [version history](/version-history/) page. If the missing signing was the only reason for you not to switch to one of the unstable versions, you can now go ahead and grab it. Please note that this is still an *unstable* release, which means it hasn't been thoroughly tested and might include unexpected behavior.
For starters, we have recently released a signed installer of a recent unstable version (1.3.281), you can find it on our [version history](/version-history/) page. If the missing signing was the only reason for you not to switch to one of the unstable versions, you can now go ahead and grab it. Please note that this is still an *unstable* release, which means it hasn't been thoroughly tested and might include unexpected behavior. Also note that (automated) continuous builds are _not_ signed.
### Next Steps
#### Next Steps
Our top priority is to publish a final (stable) version of Greenshot 1.3 as soon as possible, for future versions we are aiming for smaller releases and shorter release cycles. For the 1.3 release, this means:
* we will have a look at incoming merge requests, especially bug fixes