Skip to content

Comments

createrelease: added note about creating performance tracking ticket [skip ci]#8263

Open
firewave wants to merge 1 commit intodanmar:mainfrom
firewave:release-perf
Open

createrelease: added note about creating performance tracking ticket [skip ci]#8263
firewave wants to merge 1 commit intodanmar:mainfrom
firewave:release-perf

Conversation

@firewave
Copy link
Collaborator

the ticket is to track (potential) "regression" in performance across more versions than the actual daca analysis which only compares the latest against the previous version.

@sonarqubecloud
Copy link

@firewave
Copy link
Collaborator Author

I added this to the checklist because I sometimes forget to create this. Having this list allows us to look into potential performance regressions after a release. With some many parts in the air I do not get around to checking the results as often as I would like to.

I have local changes which allow the script to process an dynamic amount of versions (including local binaries). I had these for ages now but never got around to tidy them up (mostly lacking proper formatting of the server pages). It might also make sense to compare against the previous two versions which would make these tickets less relevant.

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

Successfully merging this pull request may close these issues.

1 participant