jasonmp85

/*!
 * jQuery JavaScript Library v1.7.2
 * http://jquery.com/
 *
 * Copyright 2011, John Resig
 * Dual licensed under the MIT or GPL Version 2 licenses.
 * http://jquery.org/license
 *
 * Includes Sizzle.js
 * http://sizzlejs.com/

jasonmp85

#!/bin/bash

set -eux

status=0

# Create Ubuntu's PostgreSQL socket dir and relax permissions.
sudo mkdir -p /var/run/postgresql
sudo chown -R `whoami` /var/run/postgresql

jasonmp85

#!/usr/bin/env ruby
# encoding: UTF-8

require 'optparse'
require 'ostruct'
require 'mechanize'

options = OpenStruct.new

parser = OptionParser.new do |p|

jasonmp85

#include "demo.hpp"

int main(void)
{ printf("hello world"); }

jasonmp85

CREATE TABLE dist (id integer);
CREATE TABLE ref  (id integer);

SELECT create_distributed_table('dist', 'id');
SELECT create_reference_table('ref');

CREATE FUNCTION dist_func()
RETURNS void LANGUAGE plpgsql AS $$
BEGIN
    EXECUTE 'SELECT id, $1 FROM dist' USING 1;

jasonmp85

require "formula"

class Chpg < Formula
  desc "PostgreSQL environment tool"
  homepage "https://gist.github.com/jasonmp85/218f3bba809ec086343a"
  url "https://gist.githubusercontent.com/jasonmp85/218f3bba809ec086343a/raw/db7e002ba593512b3a9ae27eb52762d104dae416/chpg.sh"
  sha256 "4a3d5165364e3f8289613dfe37d8e2a7615116b8a09c6a940c3207fe30e30d76"
  version "0.1.1"

  depends_on "petere/postgresql/postgresql-common"

jasonmp85

#!/bin/bash

# make bash behave
set -euo pipefail
IFS=$'\n\t'

# adapted from: http://stackoverflow.com/a/32239112

# create tmpdir and register cleanup callback
tmpdir=$(mktemp -d ~/.docker-man.XXXXXXXX)

jasonmp85

These instructions assume you have $VERSION, $PROJECT, and $REPO environment variables set in your shell (e.g. 6.1.1, citus, and citus). With those set, code from most steps can be copy-pasted.

After this checklist, you're still not done: open a release checklist in Enterprise and release there, too!

Prepare Project

• Ensure all needed changes are in the relevant release-x.y branch. git log --cherry-pick --no-merges release-x.y...master can be helpful. Be sure to cherry-pick changes in the same order they were merged to the main branch (but do not cherry-pick merge commits themselves)
• Add a CHANGELOG entry in the master branch summarizing meaningful changes
• Use git cherry-pick to add the new CHANGELOG entry to the release-x.y branch
• Use git tag -a -s v$VERSION to create an annotated, signed tag for the release. Summarize the release in the one-line tag annotation (beneath 52 characters). Push the tag with git push origin v$VERSION