# Deprecation notices?

**URL:** <https://community.keyboard.io/t/deprecation-notices/2454>\
**Category:** Programming\
**Created:** [January 24, 2019, 11:49am UTC](https://community.keyboard.io/t/deprecation-notices/2454 "2019-01-24T11:49:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamadagni](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/jamadagni/32/2030_2.png) [@jamadagni](https://community.keyboard.io/u/jamadagni)\
**Post date:** [January 24, 2019, 11:49am UTC](https://community.keyboard.io/t/deprecation-notices/2454/1 "2019-01-24T11:49:15Z")

</div>

> <https://github.com/keyboardio/Kaleidoscope/commit/bbfede8cccbf46841e406ec2d51e9c06ea2b8b2f>

Was there an announcement re these deprecations on this forum? What is an easy way to keep track of such deprecations?

My sketch doesn’t compile right now and it would seem these changes are the reason…

---

<div class="post-metadata">

**Author:** ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)\
**Post date:** [January 24, 2019, 12:18pm UTC](https://community.keyboard.io/t/deprecation-notices/2454/2 "2019-01-24T12:18:44Z")

</div>

> [@User-visible major / breaking changes coming in Kaleidoscope](https://community.keyboard.io/t/user-visible-major-breaking-changes-coming-in-kaleidoscope/1665):
>
> We used to list breaking changes and major features in this thread, but we failed to keep the list up to date. It was too far removed from the code where the changes happen. Because a significant number of people expressed interest in a change log, one that’s more succinct than the git logs, we ended up with two new files in the master [Kaleidoscope](https://github.com/keyboardio/Kaleidoscope) repository: [NEWS.md](https://github.com/keyboardio/Kaleidoscope/blob/master/NEWS.md) provides a high-level overview of major features, breaking changes, important fixes. [UPGRADING.md](https://github.com/keyboardio/Kaleidoscope/blob/master/UPGRADING.md) goes into a bit more detail…

This used to be the topic for these announcements, but it always went out of sync. The best way to keep up with deprecations is to look at `UPGRADING.md` once in a while. Mind you, we are adding warnings whenever possible, in which case you get a compile-time warning if you use a deprecated interface, and have Kaleidoscope updated.

Sadly, for some interfaces this wasn’t possible, and the only way to know about them would’ve been `UPGRADING.md`. We’ve learned the lesson, and most - if not all - new interfaces we add, are added in a way that allows us to add a compile-time deprecation notice if it turns out to be necessary.

If it helps, I can bump the thread mentioned above when we deprecate things in the future - I wouldn’t list the deprecation itself, just post a note to check `UPGRADING.md`. Bumping is considerably easier than keeping it up-to-date with details, so this process could work better.

---

<div class="post-metadata">

**Author:** ![jamadagni](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/jamadagni/32/2030_2.png) [@jamadagni](https://community.keyboard.io/u/jamadagni)\
**Post date:** [January 24, 2019, 12:27pm UTC](https://community.keyboard.io/t/deprecation-notices/2454/3 "2019-01-24T12:27:19Z")

</div>

Yes please at least do the bumping of some simple notice that links to `UPGRADING.md`.

Anyhow I got my sketch fixed as all I needed was to include `plugin::` in a few places.
