Roadmap

What is missing to reach next releases' stage?
#742768-7: Limit to alpha/beta/RC version names

- proof of concept: let the node form go through its natural workflow so 3rd party modules can react to hooks (insert/update/form_alter/etc)
- guarantee security (via FAPI #access)
- provide per content type settings
-- each content type may choose what node properties are allowed to be driven through comments
- support bundling all driven properties into a fieldset without braking the form
-- make the fieldset title configurable
-- make the fieldset optional DISCARDED (might be reconsidered depending on the outcome from #722792: optionally get rid of the fieldset altogether)
- optionally allow empty comment body (only if driven properties were changed)
- provide per content type permissions
- summary of changes
-- display them above the comment
-- provide them via token (markup ul/li and its text plain version) #710806: Method for adding change notes in comment
- keep track of changes (aka schema)
- provide hooks for other modules to be able to:
-- include more supported properties and provide change detection for them
-- alter existing supported properties?? (what for?) (reviewed)
- settings page for global settings
- resolve what to do with images? provide our own?
-- currently CSS points to uncommitted images at img/[ok|error|warn].png
- performance review
-- static cache for available properties (which should be refreshed on property def changes)
- implement hook_comment delete (currently change history is never cleared)
- bring more theme support
-- support kind of mark to signal potential non-visible changes
- help (better if it is advanced_help)
-- describe what live_render is, and the pro-cons of having it enable/disable (this exists as UI descriptions of comment_driven_inspect)
-- settle down FAQs (README.txt at least)
--- #771590: preparing a frist draft for README.txt
---- #746870: FAQ: what might be the problem with comment-related modules?
---- #727738: FAQ: is this another tracker-like module?
---- #727816: FAQ: comment_driven_path & pathauto
---- #766960: FAQ: purpose of the Producer/Consumer Policy
- known bugs when re-previewing
-- preview doesn't seems to be a popular feature, since core's taxonomy have bugs recently discovered while testing comment_driven #716788: option none causes "Invalid argument supplied for foreach()" when previewing
-- when re-previewing some extra items (added with CCK add_more button) get vanished (located, i.e. what causes it, and how it could be addressed is known)
-- after X time of inactivity a re-preview vanishes changes made
--- happened with node properties without AHAH, but with menu provoking cache (related to node_form being cached?), this was with an old version, would still apply after above bug fixed?

- implement change detection:
-- node (title, publishing options, comment settings)
-- path (haven't looked at contrib modules providing more path features)
-- checkboxes (on/off, yes/no, true/false, 0/1, checked/unchecked ??)
-- radios (have integer/string-machine-name values, use their titles I guess)
-- taxonomy (hierarchical, non-hierarchical, tags, multi-value, single-value)
-- workflow (state, schedule, comment) #758086: Support workflow states
-- CCK
--- nodereference
--- userreference
--- number (shouldn't be themed with +/- prefix)
--- text (pending multiline & format, same as node:body)
--- content_multigroup #741728: Compatibility with CCK3.x multigroup & #773962: CCK 3.x multigroup as a whole

- guarantee flexible API:
-- support disabling driven properties from node edition (driven_nep)
-- #739712: optionally follow per node/field permissions instead of driven permissions (driven_acp)
-- #741274: Using comment driven programmatically
-- incoming/outgoing policies (aka producer/consumer) required for alternative to comment_upload proposed at #739690-28: Compatibility with comment_upload

- support other modules:
-- taxonomy related:
--- active_tags (seamlessly)
--- taxonomy_single_tag
--- hierarchical_select
--- taxiselect (introduced FAPI element taxiselect_element)
--- betterselect (blocker bug: #705984: broken default_value into betterselect_process)
-- comment related:
--- mail2web (aka mailcomment) (seamlessly) #710808: Compatibility with MailComment
--- comment_subject (seamlessly)
--- flatcomments (seamlessly)
--- notifications_team #761288: Compatibility with Team Notifications
--- casetracker #768202: Compatibility with casetracker
--- comment_upload #739690: Compatibility with comment_upload & #741544: comment_upload breaks on preview
--- ajax_comments #722734: Compatibility with ajax comments
-- CCK related:
--- date #734446: support date fields, regression #770194: warning: Missing argument 2 for driven_diff_drop_keys (driven_cck date fields), #792198: unmodified dates get shifted (having time zone)
--- filefield #727546: Supporting FileField fields
--- content_taxonomy #739286: Support content_taxonomy field
--- hs_content_taxonomy #741968: support hs_content_taxonomy widget
-- others:
--- WYSIWYG #747616-2: Compatibility with WYSIWYG & #764626: support for comment_driven
--- vertical_tabs #765972: Compatibility with Vertical Tabs
--- features / ctools #769128: Support for exportables and the Features module

- migration paths
-- comment_cck #722546: migrate from comment_cck
-- comment_alter_taxonomy (blocker issue: #725354: honor revisions)
-- D7 #741548: Is there a D7 upgrade path?

verify "don't brake" list:
- node revisions
- comment preview
- our own exposed tokens (since rarely I check them) (now we have driven_inspect)

finally:
- code cleanup (remove assertions)
- invite other maintainers to review/critize (or co-maintain if desired)
-- comment_alter_taxonomy #647148-5: Merge with Comment CCK
-- comment_cck #647150-4: Merge with Comment alter taxonomy

Demo site
- unstable3 is at http://sandbox.990.cl/tracker

[EDIT]
demo site was moved, it now resides at http://arhak.s4w.biz/tracker, however, if this new URL doesn't work then check the project page to know if it got moved again

avoid replying directly to the first comment (keep it editable)
post comments bellow

wow! really can't wait
we are releasing today, you got us in the middle of it
I would recommend start tasting unstable3 instead

lets make clear that this roadmap is still valid (also updated)