Skip to content

v0.9.0 Release Tracking Issue #125

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

Closed
8 of 11 tasks
jamesmunns opened this issue Nov 23, 2019 · 14 comments · Fixed by #142
Closed
8 of 11 tasks

v0.9.0 Release Tracking Issue #125

jamesmunns opened this issue Nov 23, 2019 · 14 comments · Fixed by #142

Comments

@jamesmunns
Copy link
Member

jamesmunns commented Nov 23, 2019

We're probably due up for a new release, as the Instance changes have not been released yet.

CC #122.

Are there any other changes we would like to land before the next release?

Must do:

  • Update relevant version numbers
  • Update BSP crates

Could do:

Do we have any other (potentially breaking) changes we would like to land soon?

CC @nrf-rs/nrf52 crew

I'd suggest we aim for a release next weekend (I have some time on a train next Saturday, so I'd be up to take the lead on this).

@hannobraun
Copy link
Contributor

This is a bit off-topic, but I'm here already, and we're talking about PACs: We should consider merging the PACs into one crate (not just one repository), like stm32-rs is doing. That would be simpler to maintain and I don't see any drawbacks. It would have the additional advantage that we could easily merge the HALs into one crate, which I think we should do (with multiple PACs, the single HAL crate would need multiple rt features, like here).

Not saying we need to do it before the release, but if we're doing a release anyway and everyone happens to agree instantly, then why not. If not, don't worry. I'll prepare a proper proposal at some unspecified point in the future.

@korken89
Copy link
Contributor

On #102, Per and I are going to have a sit this week to fix the outstanding issues with it.
Hopefully it will be ready for merge then, but I do not see it as critical for 0.9.0, it can be in 0.9.1.

@JJJollyjim
Copy link

I have submitted regens to the 3 remaining PACs, though I did that before reading you talking about merging them :)

Either way, I will have a go at updating the HAL to use these.

@hannobraun
Copy link
Contributor

I have submitted regens to the 3 remaining PACs, though I did that before reading you talking about merging them :)

I think what you did was definitely worthwhile! I don't think merging the PACs will happen before the next release, if it happens at all.

@thejpster
Copy link
Contributor

We should talk to @themadinventor about moving themadinventor/nrf91 to nrf-rs/nrf9160-pac, and republishing to crates.io under the new name.

@nikyta777

This comment has been minimized.

@dbrgn
Copy link
Contributor

dbrgn commented Jan 29, 2020

We're probably due up for a new release, as the Instance changes have not been released yet.

Digital v2 trait impls are also missing 🙂

Do we need to do all open issues as part of 0.9, or could some of them be postponed to 0.10?

@Yatekii
Copy link
Contributor

Yatekii commented Jan 29, 2020

I guess some could be postponed, but did we have so many changes yet? Also there is so much open stuff :/

@thejpster
Copy link
Contributor

Can we get this pushed out the door? Release early, release often and all that. Publishing the actinius-icarus board support crate is blocked on this release.

@jonas-schievink
Copy link
Contributor

Yup, let's do it. Just let me fix the soundness bug in #123 before.

@thejpster
Copy link
Contributor

Is this gated on nRF51 support?

@fmckeogh
Copy link
Contributor

There's 3 modules left to do and while I have been testing as I go, it will definitely need review and testing from someone else. I'm not sure how fast this process can/should be so skipping nRF51 support for 9.0.0 might be a good idea.

AFAIK adding the nrf51-hal crate doesn't affect the other HALs so could be released later without bumping the other versions? Or is that bad practice?

@thejpster
Copy link
Contributor

I think #123 is done via #135?

@Yatekii
Copy link
Contributor

Yatekii commented Apr 12, 2020

I think #123 is done via #135?

yes :)

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 a pull request may close this issue.

10 participants