Release 0.7.1

[devmotion]

I propose to release StructArrays 0.7.1.

I just came across #321 and only then realized that even older fixes such as #311 are not available in StructArrays 0.7. As large parts of the Julia ecosystem, due to CompatHelper I upgraded my packages to StructArrays 0.7. As discussed in #321, I think development should focus on 0.7 and - if deemed necessary and feasible maintenance-wise - possibly fixes could be backported to a 0.6 backport release.

Fixes #321.

[devmotion]

@jishnub @aplavin you seem to be the most active contributors of this package, maybe you could review this PR?

[jishnub]

I'm a bit lost on the versions of this package. From what I recall, v0.7 was tagged as a mistake, and further development focused on the v0.6.x series. Perhaps v0.7 should be yanked from the registry. However, I'm unsure what that'll mean for the next breaking release: will it be v0.7.1?

[devmotion]

0.7 won't be yanked: JuliaRegistries/General#119607 In my opinion, as mentioned by others in #321, it's a mistake to continue developing and releasing 0.6.x versions. Many packages and users have already switched to 0.7 (e.g. due to CompatHelper or just Pkg updates), and continuing releasing 0.6.x versions just means that they don't receive any bugfixes or new features. IMO the correct thing to do is to make 0.7.x releases whenever a bugfix or feature is released. If there's a breaking change, it should be released as 0.8.0.

[jishnub]

I agree. I guess the 0.7 branch needs to be updated to include the changes from the 0.6 one? After all, these seem compatible. Subsequent development may happen in the 0.7 branch.

[devmotion]

There are no different branches (which makes the current situation even more confusing). The version bump in the repo was reverted on the main branch, and development and 0.6.x releases just continued there. A separate branch would only become necessary if it is later decided to backport changes to 0.6.x (which I think should not be necessary).