Hi team, what changes are pending for detekt 2.0.0 release?

# detekt

[Atul Gupta]

Hi team, what changes are pending for detekt 2.0.0 release?

[Sebastian Schuberth]

Maybe look at https://github.com/detekt/detekt/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.0.0?

[Brais Gabin]

Also this: https://github.com/detekt/detekt/discussions/6035 but there is not a clear line right now to know when 2.0 is complete. https://github.com/detekt/detekt/pull/7263 this PR, at least for me, is a big milestone.

[Brais Gabin]

Probably moving formatting to another repo is another big milestone: https://github.com/detekt/detekt/discussions/5997

[Atul Gupta]

@Brais Gabin @Sebastian Schuberth we can ignore things which are not breaking for 2.0 release. Right? or do we need to release all those things in one go? Asking as there are lots of new rules which are not being added in 1.x.xx releases

[Brais Gabin]

we can ignore things which are not breaking for 2.0 release

Maybe, it depends. In general that's true, My priorization goes to refactor the core/api because those are the things that we can't change easily once 2.0 is released. I'm not focusing on the rules themselves.

[Brais Gabin]

For example, I would like to re-review the rule API. We did changes already but I'm not 100% sure if I like how it looks right now. More things that should be defined for 2.0: https://github.com/detekt/detekt/pull/7393. For that one we need a way to properly measure the performance of detekt and its rules. The feature to measuer the performance is not a breaking change but it's a prerequisite for something else and that other thing probably requires breaking changes.

[Brais Gabin]

But I agree with you, I would like to release 2.0 asap. We didn't release a proper version for long time and we have a lot of (good) changes unreleased.

[Atul Gupta]

I think I was looking a list of items without which we will not go with 2.0.0 release which I think you already shared above. Also the fact that we are not shipping any new rules to 1.x.xx version is really pain as lots are things will get to market very late and we will get the feedback very late

[Brais Gabin]

Also the fact that we are not shipping any new rules to 1.x.xx version is really pain as lots are things will get to market very late and we will get the feedback very late

Agree

[Brais Gabin]

I think I am looking in list of items without which we will not go with 2.0.0 which I think you shared.

I don't understand you here.

[Atul Gupta]

Updated above

[Brais Gabin]

If you are looking for a full list of things that should be done for 2.0: it doesn't exist.