• 11:00:00 a.m. Monday, May 19, 2014 in America/Los_Angeles
• 2:00:00 p.m. Monday, May 19, 2014 in Canada/Eastern
• 18:00:00 Monday, May 19 2014 in UTC

• bshum to summarize bug tracking based on feedback from developers
  • Status: Done-ish, see http://wiki.evergreen-ils.org/doku.php?id=dev:bug_wrangler:faq
• eeevil After 2.6.0 is cut, eeevil to publish detailed plan about freezing baseline schemas between EG releases and using deprecates/supersedes in database upgrade scripts. This will go on the mailing list and the thread should structure further discussion of pros and cons of eeevil's plan.
  • Status:
• jeff to review OpenSRF bug 1109301 for consideration, may solicit the review of others as well
  • Status: Reviewing, have not yet opted to solicit review of others.
• jeff to call for RM 2.7 vote on open-ils-dev within the next few days
  • Status: Done. Congrats, Ben!

Some have expressed confusion about the difference between Release Notes and regular documentation. The Documentation Interest Group (DIG) has approved these basic definitions, and we would like feedback from developers.

Every new feature (or otherwise significant change to Evergreen) should have a short description of what it does differently than before, and how to get it working. In particular, it should list any new settings or permissions included with the feature, and any existing settings or permissions that are required to use the feature. Also, if the feature influences the upgrade process (e.g. by adding required steps, increasing the ingest time, etc.), you should include this information in an "Upgrade Notes" section. Otherwise, Release Notes should be kept short and should usually not include screenshots or step-by-step instructions. Files can be added to the source directory "RELEASE_NOTES_NEXT" in the appropriate subdirectory. Upgrade notes can be included in an "Upgrade Notes" section of your release notes or added as a separate file to an "upgrade" subdirectory within your appropriate subdirectory.

This should contain everything an Evergreen user or administrator needs to know about the new feature (or otherwise significant change to Evergreen). Screenshots and step-by-step instructions are generally very helpful. Files can be added to the source directory "DOCS_NEXT". If you know where this information would fit best in the existing Evergreen documentation, please mention that on the DIG email list or add your files to the appropriate subdirectory under the "docs/" source directory.