flameshot-org/flameshot

Flameshot nightly build version higher than stable in repo

Open

#2,602 opened on May 13, 2022

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C++ (29,897 stars) (1,916 forks)batch import
EnhancementGood first issue

Description

Feature Description

Hi, much appreciate the Flameshot app.

Could you bump the nightly build's version (to be higher than stable repo)?

Use case problem:

I use Fedora 36 (Gnome 42 + Wayland) and install the Falmeshot by command dnf install flameshot. But in the released Flameshot v11 version is a bug, that is solved in the nightly build. The fix is not released yet (I expect it would be in v12). Cause this bug, I install the nightly build version marked as 11.0.rc1. And that cause the problem when I wanna install the upgrade of another packages through dnf upgrade command. The package manager always wants upgrade the flameshot app to stable Flameshot v11.

I'd like suggest to rename the nightly builds to higher version than is already released as stable. I mean, now is stable v11.0, that expected nightly builds would have v12.0.rc1 or v12.0.beta1.

Contributor guide

Tech stack
cpp
Domain
release
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic knowledge of GitHubfamiliarity with semantic versioning
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the version number definition in the repository, likely in CMakeLists.txt or a dedicated version file. Review the current nightly build versioning scheme and propose a change to set it higher than the latest stable release (e.g., 12.0.rc1). Check the issue comments for any prior discussion on this topic. Coordinate with maintainers via the issue to agree on the new version format.