| Package home | Report new bug | New search | Development Roadmap | Status: Open | Feedback | All | Closed Since Version 1.32.0 |
| Request #10150 | Allow "future" roadmap versions | ||
|---|---|---|---|
| Submitted: | 2007-02-22 00:27 UTC | ||
| From: | aharvey | Assigned: | cellog |
| Status: | Closed | Package: | pearweb (version 1.6.1) |
| PHP Version: | Irrelevant | OS: | Irrelevant |
| Roadmaps: | 1.9.0 | ||
[2007-02-22 00:27 UTC] aharvey
(Adam Harvey)
Description:
------------
It would be nice to be able to mark roadmap milestones as "future", or some other value that's not an actual date, much in the style of Trac. Case in point: DB, which is in a state where new releases are driven by bugs being reported and fixed, rather than having a roadmap of features that are going to be added over time. Even given this, I'd still like to be able to assign bugs to, say, DB 1.7.10 without locking myself down to a release date if I'm not quite sure when it would be.
Comments
[2007-02-25 18:27 UTC] cellog
(Greg Beaver)
This bug has been fixed in CVS.
If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET).
If this was a problem with the pear.php.net website, the change should be live shortly.
Otherwise, the fix will appear in the package's next release.
Thank you for the report and for helping us make PEAR better.