Release vs tech debt

Tech debt seems to be the gift that keeps on giving, the more we fix it, the more new opportunities open up.

This is definitely important work, but I am wondering how much of it should go into the upcoming release. For example, should build improvements and dependencies tracking be into the first community release or should it be only about modifications done up to this day and obvious functionality improvements/fixes?

I am fine either way, but this probably should affect what would be on the release branch.

Review the release-scope question in this issue, especially whether build improvements and dependency tracking belong in the first community release. Resolve the choice and record the agreed scope for the release branch; the issue is done when that decision is documented.

Written by the indexing model from the issue text.