-
Notifications
You must be signed in to change notification settings - Fork 1
Conversation
jonathanpallant
commented
Sep 11, 2023
- Adds the first draft of the slides
- Cleans up the example code
- Ensures the code examples are tested
d8a3d82
to
59e22cd
Compare
ecc7670
to
e774466
Compare
e774466
to
957ec0a
Compare
Thank you for all the comments! I really value and appreciate your attention to detail. |
this was a joy to read, thanks for writing it |
Now taken from ISO 26262-1:2018 as published in summary form at iso.org.
@pietroalbini is this OK now? |
Except for the pricing, it looks good! |
OK, that's tracked in #2 |
Closes: #2
@pietroalbini, pricing has now been fixed. |
* Access to the open-source code is free | ||
* Includes the source of the Qualification Documentation | ||
* A Binary Subscription is €25/month | ||
* Includes pre-rolling, rolling, beta and stable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Includes pre-rolling, rolling, beta and stable | |
* Includes upstream Rust releases (pre-rolling and rolling channels) | |
* Includes Ferrocene stable releases (beta and stable channels) |
Then we should mention while speaking that pre-rolling is upstream's beta, and rolling is upstream's stable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that voice-over goes with the diagram. Not sure I'd call beta a stable release though?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few lines above it says:
What upstream calls stable we rename to rolling. What they call beta we
call pre-rolling.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also I'm not sure that saying "upstream Rust releases" is sufficiently precise here. AIUI we ship our binary builds of the upstream Rust source releases, but with our patches on top. Most people would consider, I think, that "upstream Rust release" means the binaries shipped by upstream.
This is where the Enterprise Linux analogy falls down, because The Linux Kernel makes only source releases, not binary releases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, also explaining what rolling and pre-rolling are would be good (rather than this). My main concern was people not confusing our beta/stable with upstream's beta/stable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll break that out into its own slide for clarity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Called it out separately. Also noted that a binary subscription doesn't get you rendered docs, only doc source code.
This slide is normally done live, but it's a note for the presenter that the install method shown will change in the future.
@pietroalbini, good to go? |