We are changing the nomenclature of "Announce" to "Pin". Thoughts?

In our newer designs we are strongly thinking of changing the nomenclature of discussion announcing to pinning. Here are my reasons:

1. A pin icon makes sense at a glance and having the name of the operation match is a better UX.
2. Pinning us really what we are doing. The discussion is pinned to the top of a list. No more, no less.
3. Pinning is somewhat of a forum standard. The other word commonly used is "sticky", but that's very old-school. Vanilla using announce is sort of off the norm.
4. By using "announce" we are using up nomenclature that can be better used for future features. For instance we have promoted content that could also be called announced content. Just using synonyms is not the best UX.

Cons

1. The database field can't be changed, at least at this time. So the internal terminology will remain "announce" for some time. On the other hand we can and should change this in API v2. In fact, the API v2 is really pushing for any of the changes to be made now. Once we release it we can't change it so now is the time.
2. From the users perspective, any change is painful so I don't want to just change things for no reason.

This post is more of a heads up to the team, but also looking for thoughts from people that are interested in UX. So many points for such a small thing.