AdguardTeam / AdguardTeam/AdGuardHome
The app is stable enough now that a designated 1.0 release seems warranted.
- Langage dominant
- TypeScript
- Étoiles
- 36.9k
- Forks
- 2.5k
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
### Prerequisites
- [x] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions) and found no answer
- [x] I have searched other issues and found no duplicates
- [x] I want to request a feature or enhancement and not ask a question
### The problem
I've used AdGuard Home for at least 5 years now, and it seems to work well enough for its intended purposes that I personally would consider it stable by now, or at least as stable as it seems likely to ever be.
As such, changing the version numbering for new versions from 0.(…) to whole numbers seem like a suited time for it.
### Proposed solution
Instead of numbering the next version as (at the time of writing) 0.102.72, number it as 1.0.
### Alternatives considered and additional information
Let's be honest: We can't just stick to the Dwarf Fortress-type approach that *a lot* of app devs out there do nowadays, where they come across to outsiders as being scared of considering their apps to be stable. Officially announcing a version 1.0 would go a long way to fix such impressions.
Guide de contribution
Ouvrir le guide de contribution
Évaluation
Cette issue n'a pas encore été évaluée.