Hi, Bunch of comments inline:
> Michelle, > Just to be clear, here is what I am suggesting, using 1.3 as an > example: > > + Release 1.3 <---- if the user clicks on Release 1.3, without > expanding, they would see the release notes for 1.3 (See below for > proposed outline of what could be included per release page) > > - Release 1.3 <--- if the user expands the Release 1.3 page(s) > they see an expanded view which includes sub-pages that are > stand-alone. -- Release 1.3.1 <--- if the user clicks on Release > 1.3.1 they would see the release notes for only 1.3.1 -- Release 1.3.2 I think this structure sounds good. > 1. Release Highlights - high level overview +1 > 2. Major Release Changes - describe major features that have been > changes, altered, etc. +1 >3. Installation Changes - if there is a > "master" page for installations it should be referenced here and only > changes to that process should be highlighted and called out -0 Instead details should be on the install and configuration page. E.g. calloutboxes would identify that a different version of ffmpeg needs to be installed for 1.2.2 or something like that. >4. > Upgrading from Previous Version - Describe how to upgrade Ha! :) >5. Detailed > change List - what is currently listed on 1.3 page is example of what > could be found here Links to JIRA issues would be my preference. >6. API Changes - API changes, if any, could be > listed +1 I like. -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
