# Design a friendly, easy-updatable/iterable system

**URL:** <https://forum.polkadot.network/t/design-a-friendly-easy-updatable-iterable-system/1674>\
**Category:** Tech Talk\
**Created:** [January 13, 2023, 3:32am UTC](https://forum.polkadot.network/t/design-a-friendly-easy-updatable-iterable-system/1674 "2023-01-13T03:32:06Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![alejandro](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/alejandro/32/55_2.png) [@alejandro](https://forum.polkadot.network/u/alejandro)\
**Post date:** [January 13, 2023, 9:46am UTC](https://forum.polkadot.network/t/design-a-friendly-easy-updatable-iterable-system/1674/2 "2023-01-13T09:46:55Z")

</div>

I have been involved in crafting [the release analysis](https://forum.polkadot.network/t/polkadot-release-analysis-v0-9-35/1509) we have been publishing in the forum, where we try to cover PRs that are relevant for builders, obviously there will be very concrete scenarios where different PRs might be relevant on different levels for various teams.

But I wanted to bubble up the new labels that are being included, so far in Cumulus repo.

- [Description for new cumulus labels by the-right-joyce · Pull Request #1879 · paritytech/cumulus · GitHub](https://github.com/paritytech/cumulus/pull/1879)

That has been an effort led by @joyce (big shout out!) and I am positive that these would make it much easier for teams to track changes and keep projects up to date with their deps, and for me and my colleagues to create the release analysis in a more efficient manner.

---

_[View the full topic](https://forum.polkadot.network/t/design-a-friendly-easy-updatable-iterable-system/1674)._