New release?

[adamgreig]

We might be due another release. A patch release would land #130 which is blocking thumbv8 in cortex-m-rt and other repos, while a minor release could also land outstanding #97, #126, and #127 (and perhaps we could do #106 as well).

Any thoughts @rust-embedded/cortex-m ?

[therealprof]

Big fan of RERO.

[korken89]

Sounds good to me

[korken89]

Ping @rust-embedded/cortex-m

[adamgreig]

Any thoughts on minor vs patch? I'm happy to prep for either, though I'm not sure what precisely we'd have to do for the semver trick.

[thejpster]

This is blocking something I'm working on. Anything I can do to push it out the door?

(I also need rust-embedded/cortex-m-rt#167, which this blocks)

[thejpster]

Let's get #97 in and go to 0.6.0. No point holding back.

[korken89]

SGTM

[Disasm]

Do we have any consensus on this? There are 3 PRs waiting for the minor release.

[thejpster]

https://twitter.com/42Technology/status/1099009843967471617

I can't publish the nRF9160 demo until we get this in, as I've had to vendor and patch the whole cortex-m.* set of crates.

[korken89]

Ping @rust-embedded/cortex-m - if there are no objections withing 12 hours from now, I will merge the PRs and do the 0.6.0 release.

[japaric]

We have a process for things like this. Using voting and the accepted reduced majority RFC you could have gotten a minor release approved in like 2 weeks, 2 weeks ago. In any case, this seems to be the tally for a new minor release:

• @adamgreig
• @korken89
• @thejpster
• @therealprof
• @ithinuel
• @japaric abstains

I will abstain from participating this time as I want to see the team handle a release without me.

I'm not sure what precisely we'd have to do for the semver trick.

The semver trick is documented here. Consider what happens if you mix code that depends on 0.5.x and code that depends on 0.6.0, whether the semver trick can be applied in this case or not and whether applying the semver trick actually helps or not.

Go team!

[therealprof]

@korken89 We do have a voting majority. Still interested in cutting the release?

[korken89]

I can do the release, however I was thinking about what @japaric was talking about:

Consider what happens if you mix code that depends on 0.5.x and code that depends on 0.6.0, whether the semver trick can be applied in this case or not and whether applying the semver trick actually helps or not.

Are there any ideas here, as linking in 2 cortex-m crates might cause issues with symbol names (I am on a conference right now and can't give it a test). Has anyone given it a try?
I can test it more tomorrow when I am back home, and try to mitigate if there are issues.

[thejpster]

Any more thoughts on this anyone?