Differences

This shows you the differences between two versions of the page.

--- dev:meetings:next [2014/05/01 15:32] – [Feedback for New Features Under Development] rjs7
+++ dev:meetings:next [2023/05/09 16:53] – dyrcona
@@ Line 3: / Line 3: @@
 This page is a placeholder for items to discuss at the next developer meeting, whenever that is. Cut and paste from here into wherever the actual meeting agenda gets created.
-===== Action Items from Last Meeting =====
+====== Month, Year Developer Meeting ======
+**Date:** Day Month Year
+**Time:** 3:00 pm Eastern / 12:00 pm Pacific
+**Location:** #evergreen IRC channel on Libera
+===== Action Items from Last Meeting =====
+  * [placeholder]
 ===== Updates =====
@@ Line 19: / Line 27: @@
 [placeholder]
-===== New Business =====
+=== Hatch ===
-==== Brief Release Notes Discussion ====
+[placeholder]
-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.
+=== Documentation ===
+[placeholder]
+=== Launchpad Status (as of noon Eastern) ===
+== Snapshot ==
+  * Open Bugs -
+  * Pullrequests -
+  * Signedoff -
+== Updates Since Last Meeting ==
+  * Bugs Added -
+  * Pullrequest tag Added -
+  * Signedoff tag Added -
+  * Fix Committed -
+===== New Business =====
+[placeholder]
-=== Release Notes ===
+===== Announcements =====
-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.
-=== Normal Documentation ===
+  * Next Meeting is XYZ
-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.
-==== Feedback for New Features Under Development ====