I'm becoming increasingly worried about this problem as well. This release cycle, where we did a bunch of SDT evolution, created a lot of user-visible API changes and we haven't been good at all about tracking them.
I am wondering about whether we should try adding a custom field to Jira called something like "user-visible API change" that would be a check box or something that would indicate that this issue involves a modification that might break existing user-level code, such as their build scripts. (This would also mean that the issue should have some comment associated with it that compares/contrasts the old and new API. Cheers, Philip ----- Original Message ----- From: Aaron Kagawa <[EMAIL PROTECTED]> Date: Friday, May 26, 2006 12:45 pm Subject: [HACKYSTAT-DEV-L] Notifying our users of changes To: [email protected] > Hey Guys, > > I just figured out a problem I was having with the Emma sensor (see > http://hackydev.ics.hawaii.edu:8080/browse/HACK-709). The problem > was that my emma sensor was working fine, then one day after an > upgrade of our Hackystat version it stopped working. It took me a > little while to figure out that the sensor now requires a specific > depth in the xml report. It didn't before or the depth > changed. Regardless of the specific details of the change, i think > we need to figure out how to notify our users of changes like > this. This isn't the first time that this has happened. > > I know that this isn't an easy task, but as our user base grows it > will become increasingly important. Anyone have any ideas? > > thanks, Aaron >
