Opened 18 years ago
Closed 14 years ago
#4883 closed enhancement (worksforme)
Automatic feature list of the software being developed through commit logs
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | general | Version: | |
| Severity: | major | Keywords: | tracobject notification |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Currently, feature lists of large softwares are managed manually. But additions, modifications, and removals of features are dependant on commits. So I was wondering if there is any way to manage a special wiki page which contains the feature list of the software, just like the tickets ("#fixes" kinda stuff).
Features can have numbers too! Feature lists have a tree structure, so the numbering must be in order with that.
One example commit message can be
AddFeature 12.4.3 Automatic feature-list management. Fixes #5000
and one more
AddsFeature 12.4.3.7 #5001 Optional storage of ticket number where feature was requested. Fixes #5001
So now you not only have an automatically managed feature list, but also a complete timeline of when a feature/subfeature was added, modified or removed.
Attachments (0)
Change History (4)
comment:1 by , 18 years ago
| Summary: | Automatic feature list of the software being developed → Automatic feature list of the software being developed through commit logs |
|---|
comment:2 by , 18 years ago
| Component: | version control → general |
|---|---|
| Keywords: | tracobject notification added |
| Milestone: | → 2.0 |
| Owner: | changed from to |
comment:4 by , 14 years ago
| Milestone: | triaging |
|---|---|
| Resolution: | → worksforme |
| Status: | new → closed |
Something like this can now be implemented as a plugin using the IRepositoryChangeListener interface.
Sounds like requirement management (Feature lists have a tree structure).
I believe that adding such a subsystem to Trac should be easily done as a plugin once a more generic data model is in place. See GenericTrac.
Also, the link between commit message and actions taken on the requirements would be facilitated by a changeset notification mechanism, see TracDev/Proposals/Journaling.