On Tue, Aug 14, 2018, 2:45 PM Nathan Heldt-Sheller < nathan.heldt-shel...@intel.com> wrote:
> Hi Devs, > > > > Going forward I’d like to make the release notes as useful as possible > without putting undue work on the release manager (which is me for now, but > will be taken over soon by Greg Labavitch from Thug Design). > > > > At a minimum, the notes will include: > > > > 1. Link and/or reference to the Specification Version implemented > in the release > > 2. A list of known issues (open Jira tickets, possibly filtered by > severity so only P2 or P1 issues show up) > > 3. A list of patches submitted since the last release (basically a > git log <release_tag>..<prev_release_tag> dump to txt file) > > > > I’d also like to include a high-level “what’s new” in a major release, but > might just reference the OCF Specification version of that blurb. > > > > What else would be helpful? > Clean distinction between "core" Iotivity and extras (e.g. cloud). I would even make a distinction between core and RD, for example. > > Thanks, > Nathan > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9865): https://lists.iotivity.org/g/iotivity-dev/message/9865 Mute This Topic: https://lists.iotivity.org/mt/24528365/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
