If you need to format (e.g. code examples, etc.) then markdown is fine. So is plain text.
-Taylor > On Jan 23, 2019, at 5:24 AM, Stig Rohde Døssing <[email protected]> > wrote: > > I'll write something for 5 - Kafka related changes. > > We have dropped Druid support, so 13 should be only Kinesis. > > Which format should the blurbs be written in? (Markdown?) > > Den ons. 23. jan. 2019 kl. 08.57 skrev Roshan Naik > <[email protected]>: > >> Like Taylor’s suggestion of collectively contributing small blurbs on >> features for the Release announcement. Thats the first thing people look on >> hearing a release announcement. The jira list is not very understandable at >> first glance. >> >> >> Based on suggestions so far and a quick scan of the jiras in release notes >> here is a draft list in no particular order. I am sure I am missing a few >> impt ones. This can be pruned or modified as needed: >> >> 1- Re-architecture - [Roshan] >> 2- Windowing enhancements >> 3- SQL enhancements >> 4- Metrics >> 5- Kafka related changes >> 6- Security (nimbus admin groups, delegation tokens, optional >> impersonation) >> 7- PMML (Machine Learning) support. >> 8- Streams API >> 9- Module restructuring & dependency mitigation >> 10- Java porting >> 11- DRPC cmd line >> 12- Lambda support >> 13- New spouts: Kinesis & Druid ? >> 14- Changes to deployment and cli submission >> 15- RAS changes >> 16- Trident enhancements >> 17- New Admin cmds to debug cluster state >> 18 ... others ? >> >> Please pick the topics you can contribute blurbs for. I have put my name >> against one. It will help Taylor aggregate them and do the necessary final >> edits. >> >> >> -Roshan >> >> >> >> >>
signature.asc
Description: Message signed with OpenPGP
