Meeting 2014 07 07

Agenda / Notes

• Deployment automation: Deepika starting soon?
  • STATUS: Has finished Drupal training, and getting familiar with LAMP stack. She's now downloading CheckbookNYC and will be trying to set it up locally. REI will also post a near-term plan for Deepika's activities.
• GitHub/JIRA issue filing has begun! Thanks, Ajibola.
  • CheckbookNYC "Create Alerts” functionality (#34). Added the "enhancement" label.
  • Checkbook NYC Top row freezing (#35) Added the enhancement label.
  • EDC Agency - UAT Defect (#36). Removed Ed's email signature block from the description.
• The 'checkbook_edc_maint_fork' branch sometimes mentions JIRA issue numbers, sometimes mentions GitHub issue numbers. For example, see Ram's commits 4e735ca2ec and 9c43340c1, which mention GitHub issue #36; contrast with Alicia Torkelson's commits on the same branch, which mention only JIRA ticket numbers. It looks like the policy is "If there is a GitHub issue number, just use that, because we can get to the JIRA ticket from there anyway. Otherwise, use the JIRA ticket number." Is that accurate?
• Commit messages: 14e6d76d383 for example. Message is just "NYCCHKBK-3714 - "Create Alerts” functionality"; commit touches 10 files and makes massive changes.
• Discuss new branching and versioning system.
  • DECISION: API will always remain backward compatible, even across major number increments.
  • QUESTION: Version number of running instance will be made available via API?
  • These branches will all be branched from master.
  • Changes will be cherry-picked to parallel branches as needed. For example, if 2.2.1 is deployed, and then a bugfix is discovered, a 2.2.2 branch might be created to fix it. But in the meantime, 2.3.0 already exists and was branched from master. So when 2.2.2 is deployed, and thus merged to master, 2.3.0 won't get that fix automatically -- it has to be ported across, using 'git merge' to cherry-pick the appropriate changes.
• Posts that might become issue tickets:
  • Nicole's "Top Navigation Bar". Later posted "please withdraw this ticket".
  • "Two Issues - Export and Data Feeds" from Adrissha.
  • "Fixed sticky header on data tables in CheckbookNYC". Was to be discussed on call. This is issue #35. Karl to cross-link.
  • "UAT Contract Spending Transaction Page v. Production Contract Spending Transactions Page". Was to be discussed on call; should issue be filed?
    • DECISION: No issue for now. Ed to look at this in more detail.