Skip to content

Development Process

Christopher Anderson edited this page May 17, 2016 · 2 revisions

This document is a proposal for our Development Process and is still in development. As such, is not yet in effect for the project.

Milestones

We will create milestones for every minor version we plan on shipping. We may create milestones for patch versions, if needed. We follow the semantic versioning v2.0.0 system. There is also a backlog milestone. The goal is to have at least 3 milestones: current minor version, next minor version, and backlog.

Releases

We will create release builds as needed. They'll be named {version}(-{prerelease stage})-{build number} (e.g. v0.2.1-alpha-19234). These should include release notes of what changes were included.

Feature planning

For planning, the team will hold a planning meeting before starting a new milestone in earnest. In that meeting, we'll will triage features and assign to developers. Those features will be the primary goals for the version. Additional 'low-hanging-fruit' features may be added to a version afterwards, if they do not significantly delay shipping that version or violate semver, at the discretion of team.

Triage

The team meets Monday and Thursday to triage issues and significant PRs.

Learn

Azure Functions Basics

Advanced Concepts

Dotnet Functions

Java Functions

Node.js Functions

Python Functions

Host API's

Bindings

V2 Runtime

Contribute

Functions host

Language workers

Get Help

Other

Clone this wiki locally