Flameshot: Plan for another release (0.6.1?)

Created on 4 Feb 2019  路  10Comments  路  Source: flameshot-org/flameshot

Similar to #314 , I'm suggesting tagging another minor release again. It's already half a year since last release and that there are several important bugs fixed since v0.6.0.

Of course with the experience of the last release, this time the release should be performed more carefully. We should build binary packages for different distributions first before actually tagging in order to prevent potential bugs caused by packaging (to be more concrete, the D-bus related bug in Ubuntu 18.04 package for v0.6.0).

Most helpful comment

I have a few things in mind before creating a 0.6.1:

  • Finishing the numbered bullet tool: almost done.
  • Update copyright year in source files: this one is a single replace command but I'm waiting for the new tool to be finished to not cause merge conflicts.
  • Check and tag issues and check if I can fix more low hanging fruit bugs.
  • Add the close flameshot after capture option
  • Add a save path from the gui config menu (its effect would have less priority than the path defined from cli)

I'm working on a personal project and contributing to Godot engine for a free software contests but I want to start working on these tasks soon.

All 10 comments

I think it's better to wait for snap and flatpak packages.

Is there any progress for snap and /or flatpak packages?

@hosiet
snap build successfully, but it's dirty and need @lupoDharkael to publish them to snap store.
flatpak is hard to build in travis-ci docker environment.

I don't think either of them could be a blocker. I know that CI is great, but we make releases less than 2 times every year and it's totally fine if we build them manually.

@hosiet https://github.com/flameshotapp/packages flatpak build successfully, wait someone to publish them.

I have a few things in mind before creating a 0.6.1:

  • Finishing the numbered bullet tool: almost done.
  • Update copyright year in source files: this one is a single replace command but I'm waiting for the new tool to be finished to not cause merge conflicts.
  • Check and tag issues and check if I can fix more low hanging fruit bugs.
  • Add the close flameshot after capture option
  • Add a save path from the gui config menu (its effect would have less priority than the path defined from cli)

I'm working on a personal project and contributing to Godot engine for a free software contests but I want to start working on these tasks soon.

Add the close flameshot after capture option that it could be possible to make multi-captures? If it is, should it be possible to re-edit each capture after (to insert numbered bullets for example)

Any news on the release?

@lupoDharkael

This project and app are particularly popular on Linux. With the transition to Wayland I think your app will only gather a greater following. Perhaps, having a call out for additional maintainers is in order.

Working on a new release.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

szszoke picture szszoke  路  4Comments

thiswillbeyourgithub picture thiswillbeyourgithub  路  3Comments

xstable picture xstable  路  3Comments

omkarnathsingh picture omkarnathsingh  路  4Comments

makz27 picture makz27  路  4Comments