I once proposed a new [`@was`](https://drupal.org/node/1561464) tag; basically the opposite of `@since`.

It would allow documentation parsers that are generating documentation pages for multiple major versions of a project to automatically generate a decent level of _upgrade documentation_ for developers migrating from a previous major version.

The syntax would simply be:
```
@was <"FQSEN">
```
Thus, when a public class/method/function is renamed in a new major version, then you can simply inform the (cross-major-version) documentation parser to generate a relationship between the old and the new resource, like this:
```php
/**
 * @was foo()
 */
function bar() {
}
```

Do you think that would be a good idea to add?