-
-
Notifications
You must be signed in to change notification settings - Fork 3k
Release procedure
marcelklehr edited this page Oct 12, 2012
·
17 revisions
- Consider, which changes (aka commits) you want to release into master.
- Determine the new version number, following semantic versioning spec.
- Move the relevant commits into a new branch
release/releases-x.x.x - Ensure, all version numbers a up-to-date
- Be sure the API version is correct (new hooks shouldn't be added to already existing API versions)
- Update the version number in
package.json(and elsewhere?) - Push
release/releases-x.x.xto github - Open a pull request from
release/releases-x.x.xtomaster
- Docs
- Translating
- HTTP API
- Plugin framework (API hooks)
- Plugins (available)
- Plugins (list)
- Plugins (wishlist)
- Etherpad URIs / URLs to specific resources IE export
- Etherpad Full data export
- Introduction to the source
- Release Procedure
- Etherpad Developer guidelines
- Project to-do list
- Changeset Library documentation
- Alternative Etherpad-Clients
- Contribution guidelines
- Installing Etherpad
- Deploying Etherpad as a service
- Deploying Etherpad on CloudFoundry
- Deploying Etherpad on Heroku
- Running Etherpad on Phusion Passenger
- Putting Etherpad behind a reverse Proxy (HTTPS/SSL)
- How to setup Etherpad on Ubuntu 12.04 using Ansible
- Migrating from old Etherpad to Etherpad
- Using Etherpad with MySQL
- Customizing the Etherpad web interface
- Enable import/export functionality with AbiWord
- Getting a list of all pads
- Providing encrypted web access to Etherpad using SSL certificates
- Optimizing Etherpad performance including faster page loads
- Getting to know the tools and scripts in the Etherpad /bin/ folder
- Embedding a pad using the jQuery plugin
- Using Embed Parameters
- Integrating Etherpad in a third party app (Drupal, MediaWiki, WordPress, Atlassian, PmWiki)
- HTTP API client libraries