DDMS 4.0 is going through a last round of voting this week, and is expected to be released around the beginning of September. Because IC-IRM was merged into DDMS in this release, there are some major changes throughout the specification. I have opened 48 tickets related to DDMS 4.0 in the DDMSence Issue Tracker:
http://code.google.com/p/ddmsence/issues/listI will not start implementing DDMS 4.0 until after the voting is complete. I believe that the specification is stable and all-but-complete right now, but anything could happen during community voting. I estimate that this release will take 3 to 4 times longer to develop, test, and release than previous releases, so it will definitely not come out overnight.
My goals for the next release of DDMSence are:
1)
Avoid having parallel downloads based on the DDMS Version: There should only ever be 1 "latest" copy of DDMSence, and it should support as many DDMS versions as is viable.
2)
Maintain support for DDMS 2.0, 3.0, and 3.1: While it does make sense to phase out old versions to keep the code clean, I would prefer to give a large advance warning that an older version is going away, maybe even a full year.
3)
Aim for Minor release: I'm hoping to be able to add DDMS 4.0 without breaking any backwards compatibility.
Depending on how tricky development gets once I dive in, I feel that #1 is a must, while the rest will take backseat priority to having a robust codebase. If you have any opinions, I'd love to hear from you!
Regards,
BU