User Tools

Site Tools


dev:meetings:2009-10

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
dev:meetings:2009-10 [2009/10/15 17:30] – add acquisitions to the possible agenda dbsdev:meetings:2009-10 [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== IRC developer meeting for October 2009 ====== ====== IRC developer meeting for October 2009 ======
  
-Please add agenda items here:+See also[[:dev:meetings:2009-10:minutes|Meeting Minutes for October 2009]] 
 + 
 +**Agenda:**
  
   * 1.6 release status   * 1.6 release status
Line 21: Line 23:
   * Lowering the barriers to participation   * Lowering the barriers to participation
     * There haven't been many patches submitted from outside of the committer team - are there things that we can do to increase participation from the rest of the community?     * There haven't been many patches submitted from outside of the committer team - are there things that we can do to increase participation from the rest of the community?
 +
 +  * Bug tracking and QA
 +    * Is there general agreement that we should put out a call for a QA team: bug testers & wranglers who would manage the public bug database & verify bugs & build tests to add to the test harness?
 +    * Any interest in talking about non-Trac options? atz had mentioned self-hosted bugzilla; dbs has mentioned screw it, let's move to fully-hosted launchpad
  
   * Release process   * Release process
Line 26: Line 32:
     * DVCS model of feature development in separate branches, with merges to trunk only when the feature has stabilized?     * DVCS model of feature development in separate branches, with merges to trunk only when the feature has stabilized?
       * Devs can do DVCS model today on their own branches, but would be nice to have a single repo that holds all of the branches - or perhaps at least a list of all the different locations that branches are hosted (github, launchpad, google code)       * Devs can do DVCS model today on their own branches, but would be nice to have a single repo that holds all of the branches - or perhaps at least a list of all the different locations that branches are hosted (github, launchpad, google code)
- 
-  * Bug tracking and QA 
-    * Is there general agreement that we should put out a call for a QA team: bug testers & wranglers who would manage the public bug database & verify bugs & build tests to add to the test harness? 
-    * Any interest in talking about non-Trac options? atz had mentioned self-hosted bugzilla; dbs has mentioned screw it, let's move to fully-hosted launchpad 
  
   * Acquisitions (based on the survey, there was a strong interest in talking about acquisitions)   * Acquisitions (based on the survey, there was a strong interest in talking about acquisitions)
dev/meetings/2009-10.1255642218.txt.gz · Last modified: 2022/02/10 13:34 (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.