Changes between Version 3 and Version 4 of ThisTicketWasOpenedTenYearsAgo
- Timestamp:
- Jan 4, 2015, 3:05:32 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ThisTicketWasOpenedTenYearsAgo
v3 v4 2 2 3 3 - ... and you still haven't implemented this feature or fixed this bug? 4 - ... a re you ever going to do finish it one day?4 - ... and are you ever going to finish it one day? 5 5 6 6 == (short) A: PatchWelcome! … … 12 12 In practice a patch is not enough, even if it meets the appropriateness and quality criteria enumerated in the PatchWelcome page. You need to have a committer to approve it and integrate it in the code base. Depending on the ups and downs of the project life cycle and the time available of the maintainers, this can sometimes slow down the adoption of new features. Furthermore, consider that added code will most of the time also //add// to the maintenance effort. There's an easy solution to this: be not only a contributor, but become a maintainer as well! 13 13 14 Some of the //properties// of "long run" tickets and an explanation of why they are still kept open edare:14 Some of the //properties// of "long run" tickets and an explanation of why they are still kept open are: 15 15 - milestone ''next-minor-releases'': fix worthy of being integrated in a maintenance release; no promise made as to ''which'' release that will be 16 16 - milestone ''next-major-releases'': enhancement that fit in the long term vision we had for Trac; still no promise relative as to ''when'' this might happen