Changes between Version 1 and Version 2 of ThisTicketWasOpenedTenYearsAgo

Timestamp:

Mar 15, 2014, 1:25:34 PM (10 years ago)

Author:

Christian Boos

Comment:

fix a few typos

ThisTicketWasOpenedTenYearsAgo

@@ -1 +1 @@
 = Q: This ticket was opened 10 years ago...
 
- - ... and you're still haven't implemented this feature / fixed this bug!
+ - ... and you still haven't implemented this feature / fixed this bug!
  - ... are you ever going to do finish it one day?
 
@@ -10 +10 @@
 == (long) A: 
 
-Well, 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 up and downs of the project live cycle and the time available in the hands of the maintainers, this can sometimes slow down the adopting of new features (consider that added code will most of the time only //add// to the maintenance burden). There's an easy solution to this: be not only a contributor, but become a maintainer as well!
+Well, 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 in the hands of the maintainers, this can sometimes slow down the adopting of new features (consider that added code will most of the time only //add// to the maintenance burden). There's an easy solution to this: be not only a contributor, but become a maintainer as well!
 
 This clarifications enables me to finish by discussing briefly some of the //properties// of these "long run" tickets, and explain why we still keep them opened:
- - milestone ''next-minor-releases'': fix worthy of being integrated in a maintenance release; no promise made as ''when''
+ - milestone ''next-minor-releases'': fix worthy of being integrated in a maintenance release; no promise made as to ''which'' release that will be
  - 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
  - milestone ''unscheduled'': neither really fits nor is completely at odds with the long term goals; it's more a matter of having a future ''maintainer'' willing to go in this direction