dev:meetings:next
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dev:meetings:next [2014/05/01 15:33] – [Brief Release Notes Discussion] rjs7 | dev:meetings:next [2024/03/27 14:42] (current) – Updating the meeting name to development, going back to a 2017 change to make the meetings more inclusive. klussier | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Next Developer | + | ====== Next Development |
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. | 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 Development |
+ | **Date:** Day Month Year | ||
+ | |||
+ | **Time:** 3:00 pm Eastern / 12:00 pm Pacific | ||
+ | |||
+ | **Location: | ||
+ | |||
+ | ===== Action Items from Last Meeting ===== | ||
+ | * [placeholder] | ||
===== Updates ===== | ===== Updates ===== | ||
Line 19: | Line 27: | ||
[placeholder] | [placeholder] | ||
- | ===== New Business ===== | + | === Hatch === |
- | ==== Brief Discussion about Release Notes ==== | + | [placeholder] |
- | Some have expressed confusion about the difference between Release Notes and regular documentation. | + | === Documentation |
+ | |||
+ | [placeholder] | ||
+ | |||
+ | === Launchpad Status | ||
+ | |||
+ | == 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 " | + | |
- | be kept short and should usually not include screenshots or step-by-step | + | |
- | instructions. Files can be added to the source directory " | + | |
- | in the appropriate subdirectory. Upgrade notes can be included in an " | + | |
- | Notes" section of your release notes or added as a separate file to an " | + | |
- | 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 " | + | |
- | information would fit best in the existing Evergreen documentation, | + | |
- | mention that on the DIG email list or add your files to the appropriate | + | |
- | subdirectory under the " | + | |
- | ==== Feedback for New Features Under Development ==== |
dev/meetings/next.1398972800.txt.gz · Last modified: 2022/02/10 13:34 (external edit)