dev:meetings:2011-11-08
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| dev:meetings:2011-11-08 [2011/11/22 10:53] – First draft of minutes dbs | dev:meetings:2011-11-08 [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 20: | Line 20: | ||
| - Determine the taker of minutes: Dan Scott | - Determine the taker of minutes: Dan Scott | ||
| - Determine meeting leader: Ben Shum | - Determine meeting leader: Ben Shum | ||
| - | - Review past action items: *None* | + | - Review past action items: |
| - New Business | - New Business | ||
| - Evergreen 2.1.0 official announcement | - Evergreen 2.1.0 official announcement | ||
| - Release notes (in RELEASE_NOTES.txt in rel_2_1) should include list of known bugs fixed in 2.1.1 such as OpenLibrary added content | - Release notes (in RELEASE_NOTES.txt in rel_2_1) should include list of known bugs fixed in 2.1.1 such as OpenLibrary added content | ||
| - Evergreen 2.1.1? | - Evergreen 2.1.1? | ||
| - | - *ACTION*: Thomas Berezansky to tweak release-cutting script to accommodate README changes (pointer to download location) | + | - **ACTION**: Thomas Berezansky to tweak release-cutting script to accommodate README changes (pointer to download location) |
| - | - *ACTION*: Thomas Berezansky to cut 2.1.1 release for testing and _severe_ criticism real soon now | + | - **ACTION**: Thomas Berezansky to cut 2.1.1 release for testing and _severe_ criticism real soon now |
| - Evergreen 2.2 alpha? | - Evergreen 2.2 alpha? | ||
| - Agreed to target week of November 15th for the 2.2 alpha | - Agreed to target week of November 15th for the 2.2 alpha | ||
| - End of community supported 1.6 | - End of community supported 1.6 | ||
| - | - *ACTION*: Anoop Atre to write "end of life" announcement | + | - **ACTION**: Anoop Atre to write "end of life" announcement |
| - | - Google Summer of Code Report | + | - Google Summer of Code Mentorship Summit report |
| - | - See dbs [[http:// | + | - See [[http:// |
| + | - Defining a release team separate from the project leads | ||
| + | - Currently Bug Wranglers can nominate series / milestones, but currently only project leads have the ability to target series/ | ||
| + | - Bug Wranglers is an open group, but if we defined a Release Team with approved membership, those folks would have the ability to target series/ | ||
| + | - General positive vibes towards the idea but no defined action item | ||
| - Sign-off by committers-to-be is very valuable | - Sign-off by committers-to-be is very valuable | ||
| - If contributor X pushes a branch out for review and requests a merge, and contributor Y pushes a branch that signs off on contributor X's commits, that is a strong positive sign in favour of the branch | - If contributor X pushes a branch out for review and requests a merge, and contributor Y pushes a branch that signs off on contributor X's commits, that is a strong positive sign in favour of the branch | ||
dev/meetings/2011-11-08.1321977197.txt.gz · Last modified: 2022/02/10 13:34 (external edit)