Skip to content

Instantly share code, notes, and snippets.

From the DTR protocol, the most effective piece that I noticed was having Mod 3&4 students share their experiences of working on teams with students from newer cohorts. The role playing felt a bit forced nad unatural, but there seemed to be great value in sharing group experiences that I've had and how to producively work through them.

@matt-stj
matt-stj / Cutting Release Branches.md
Last active March 6, 2018 19:31
How to cut release branches for Peak repos

When shipping code for an upcoming release, we're responsible for creating release branches (and closing previous ones) for any of the following repos with new code changes:

  • peak
  • legistarweb
  • chronus
  • atreyu

We use git flow to manage our branches around releases, so be sure to set it up and read through the docs here if you don't already have it.

  1. Before cutting new release branches, make sure all open release/hotfix branches are closed.
const MinHeap = require('min-heap')
module.exports = class Sorter {
constructor(logSources, printer, async = false) {
this.heap = new MinHeap
this.min = null
this.logsObj = {}
this.currentMinLog = null
this.complete = false
this.logSources = logSources