General-dev

[N-R-K]

This is just a dummy thread for discussing small/mundane development related things which don't warrant their own issue/discussion.

[N-R-K]

There's been a decent amount of bug fixes and improvements since last release. I'm thinking of cutting a new release this week or so. I plan on merging the following PRs before that, any other bugfix/PRs that are worth merging before release?

ping: @guijan

---

• scrotGrabMousePointer: error out on failure #317
• deprecate --note #326

[guijan]

If anything, the amount of changes done to the code means we've gone 2 steps forward 1 step back in many places. Maybe someone will find the new bugs (if any) while they're fresh if we wait around for a while. I'd moderate releases to once or twice a year regardless of how much activity there was in the timeframe.

But I don't think any of the PRs at the moment are particularly urgent.

[N-R-K]

the amount of changes done to the code means we've gone 2 steps forward 1 step back in many places.

Don't disagree here.

Maybe someone will find the new bugs (if any) while they're fresh if we wait around for a while.

But I think you might be overestimating how many people actually run software from master, in my experience most people stick to their distro's package. (E.g in the most recent bug report that isn't from a scrot developer #320 it's using v1.5 - presumably, because that's what his distro has).

Cutting a release will allow distros to pick it up in their unstable branches (e.g debian sid, gentoo's unstable keyword etc).

[guijan]

Maybe we should switch to semver when the first deprecation turns into removal?

[N-R-K]

Was thinking the same, though it's a bit more difficult to semver a end user application. For example, the addition of --compress can also be considered a breaking change (as it alters the behaviour of previous commands relying on --quality).

[N-R-K]

@eribertomota We should be ready for a 1.10 release. There's a draft changelog committed in the master branch.

[eribertomota]

I will take care of this now. Sorry, I only saw your private email message now.