Add comments from @thejpster in #22

Author: James Munns

content/2018-10-28-newsletter-14.md

@@ -21,14 +21,30 @@ Discuss on [users.rust-lang.org], [on twitter], or [on reddit]!
 
 <!-- more -->
 
-## The Newest Embedded WG Team: Cortex-A!
+## Embedded Rust Applications on Stable!
 
 <hr>
 
-![Screenshot of Cortex-A RFC][cortex-a-screenshot]
+<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Rust 1.30 is here! Proc macros, no_std binaries, and a progress bar for cargo! 🎊🎉🦀 <a href="https://t.co/IXm5xFYlhU">https://t.co/IXm5xFYlhU</a></p>&mdash; Rust Language (@rustlang) <a href="https://twitter.com/rustlang/status/1055499747056852993?ref_src=twsrc%5Etfw">October 25, 2018</a></blockquote>
+<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
+
+Now that `#[panic_handler]` is stabilized in [1.30], you can write Cortex-M bare-metal applications with the stable compiler. All our Rust Embedded crates, such as `cortex-m`, `cortex-m-rt` and `embedded-hal` should be ready to use on stable, but please note our two tutorial books [Discovery] and [The Embedded Rust Book] still require 1.30 beta or 1.31 beta as they use 2018 edition syntax (which isn't stabilized until the 1.31 release).
+
+[1.30]: https://blog.rust-lang.org/2018/10/25/Rust-1.30.0.html
+[Discovery]: https://rust-embedded.github.io/discovery/
+[The Embedded Rust Book]: https://rust-embedded.github.io/book/
+
+If you are able to trial 1.31 beta, you can help us test:
+
+* Minimal `const` functions (useful for initializing static variables)
+* 2018 edition syntax (including changes to `use` and `extern crate`)
+
+## The Newest Embedded WG Team: Cortex-A!
 
 <hr>
 
+![Screenshot of Cortex-A RFC][cortex-a-screenshot]
+
 [cortex-a-screenshot]: ../screenshot-cortex-a.png
 
 The Embedded Working Group has launched a Cortex-A team, to focus on supporting developers working on bare-metal, micro kernel, and other low-level tasks using ARM's Cortex-A series of microprocessors.
@@ -49,8 +65,6 @@ The team kicked off with four members: [@andre-richter], [@parched], [@raw-bin],
 <blockquote class="twitter-tweet" data-conversation="none" data-lang="en"><p lang="en" dir="ltr">Astonishing. Smashed my high score! <a href="https://t.co/WG9FXc8Kao">pic.twitter.com/WG9FXc8Kao</a></p>&mdash; Jonathan Pallant (@therealjpster) <a href="https://twitter.com/therealjpster/status/1053698944360951813?ref_src=twsrc%5Etfw">October 20, 2018</a></blockquote>
 <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
 
-<hr>
-
 [@thejpster]'s project, the [monotron], travelled to Ann Arbor Michigan for [Rust Belt Rust 2018]. Since its [last conference appearance], it has gained a whole new [list of features], including a serial application loader, a 3 channel wave table synthesizer, Atari Joystick support, and more!
 
 Check out the video above for a demo of Snake on the monotron hardware.
@@ -83,8 +97,6 @@ let port_a = Pcf8574(manager.acquire(), 0x39).unwrap();
 let port_b = Pcf8574(manager.acquire(), 0x38).unwrap();
 ```
 
-<hr>
-
 In most `embedded-hal` compatible drivers, the driver takes either ownership or a mutable reference to the peripheral used to interact with a component, such as I2C or SPI. For some protocols, such as I2C, which might have multiple devices connected to the same peripheral, managing ownership can be difficult (see [embedded-hal/35] for discussion).
 
 To address this, [@Rahix] developed [shared-bus], a crate which provides safe shared access to these peripherals through the use of a mutex. This allows for access of the underlying peripheral in as many drivers as you need! Check out the [release blog post] for more details, and for examples on how to use this for your projects.
@@ -102,8 +114,6 @@ To address this, [@Rahix] developed [shared-bus], a crate which provides safe sh
 <blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr">Happy Tuesday! Quick poll: What are you using <a href="https://twitter.com/hashtag/embedded?src=hash&amp;ref_src=twsrc%5Etfw">#embedded</a> <a href="https://twitter.com/rustlang?ref_src=twsrc%5Etfw">@rustlang</a> for right now?<br><br>RTs appreciated!</p>&mdash; Rust Embedded Working Group (@rustembedded) <a href="https://twitter.com/rustembedded/status/1052189142065405952?ref_src=twsrc%5Etfw">October 16, 2018</a></blockquote>
 <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
 
-<hr>
-
 As we get closer to our goal of stable embedded development with Rust for the 2018 edition launch, the embedded community is ramping up. We did a quick twitter poll which received hundreds of responses, and heard from developers using or evaluating embedded rust for personal and work projects.
 
 The [Embedded WG] has also grown, starting off this year with 8 developers on a single team, to a group of **27 developers** across **11 teams**, each with their own area of focus within the embedded rust space.
@@ -112,6 +122,8 @@ Now is a great time to start working with Embedded Rust, and we can't wait to se
 
 ## `embedded-hal` Ecosystem Crates
 
+<hr>
+
 As part of the [Weekly Driver Initiative], crates that are part of the `embedded-hal` ecosystem are now tracked in the [Awesome Embedded Rust] repository. Here is a current snapshot of what is available there:
 
 | Type                      | Status    | Count | Diff |