Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release vs tech debt #5

Open
ppenzin opened this issue Apr 24, 2020 · 1 comment
Open

Release vs tech debt #5

ppenzin opened this issue Apr 24, 2020 · 1 comment

Comments

@ppenzin
Copy link
Member

ppenzin commented Apr 24, 2020

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.

@rhuanjl
Copy link
Contributor

rhuanjl commented Apr 25, 2020

I'm unsure on this - though agree it's something to think about.

I don't see any obvious reason to exclude any useful tech debt work we fix from a release unless it breaks something an end user would want to be doing.

I do however wonder what we should prioritise for our first release, considering none of us are full time on this so what we can do is limited.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants