mirror of
https://github.com/corda/corda.git
synced 2025-02-21 01:42:24 +00:00
Add a page that briefly describes the proposed release process.
This commit is contained in:
parent
4271693b85
commit
61605b18e3
@ -1,26 +1,24 @@
|
||||
Welcome to the R3 prototyping repository!
|
||||
=========================================
|
||||
Welcome to the Corda repository!
|
||||
================================
|
||||
|
||||
This documentation describes the first prototype of a possible future R3 shared ledger platform.
|
||||
This documentation describes the prototype of a proposed architecture for distributed ledgers.
|
||||
|
||||
The goal of this prototype is to explore fundamentally better designs for transactions, states and smart contract APIs
|
||||
than what presently exists on the market, tailor made for the needs of the financial industry. We are attempting to
|
||||
prove or disprove the following hypothesis:
|
||||
The goal of this prototype is to explore fundamentally better designs for distributed ledgers than what presently exists
|
||||
on the market, tailor made for the needs of the financial industry. We are attempting to prove or disprove the
|
||||
following hypothesis:
|
||||
|
||||
*The combination of*
|
||||
|
||||
* *An upgraded state transition model*
|
||||
* *Industry standard, production quality virtual machines and languages*
|
||||
* *Limited data propagation*
|
||||
* *Conflict resolution without proof of work or blocks*
|
||||
|
||||
*is sufficiently powerful to justify the creation of a new platform implementation.*
|
||||
The combination of
|
||||
|
||||
* An upgraded state transition model
|
||||
* Industry standard, production quality virtual machines and languages
|
||||
* An advanced orchestration framework
|
||||
* Limited data propagation
|
||||
* Conflict resolution without proof of work or blocks
|
||||
|
||||
is sufficiently powerful to justify the creation of a new platform implementation.
|
||||
|
||||
Read on to learn:
|
||||
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
:caption: Overview
|
||||
@ -45,6 +43,7 @@ Read on to learn:
|
||||
:maxdepth: 2
|
||||
:caption: Appendix
|
||||
|
||||
release-process
|
||||
visualiser
|
||||
codestyle
|
||||
building-the-docs
|
||||
|
23
docs/source/release-process.rst
Normal file
23
docs/source/release-process.rst
Normal file
@ -0,0 +1,23 @@
|
||||
Release process
|
||||
===============
|
||||
|
||||
Corda is under heavy development. The current release process is therefore geared towards rapid iteration.
|
||||
|
||||
Each Corda development release is called a *milestone* and has its own branch in the git repository. Milestones are
|
||||
temporarily stabilised snapshots of the Corda code which are suitable for developers to experiment with. They may
|
||||
receive backported bugfixes but once announced a milestone will not have any API or backwards compatibility breaks.
|
||||
|
||||
Between milestones backwards compatibility is expected to break. Every new milestone comes with a short announcement
|
||||
detailing:
|
||||
|
||||
* What major improvements have been made.
|
||||
* How to forward port your code to the new milestone.
|
||||
* What new documentation has become available.
|
||||
* Important known issues.
|
||||
|
||||
Eventually, Corda will stabilise and release version 1. At that point backwards compatibility will be guaranteed
|
||||
forever and the software will be considered production ready. Until then, expect it to be a building site and wear your
|
||||
hard hat.
|
||||
|
||||
Our goal is to cut a new milestone roughly once a month. There are no fixed dates. If need be, a milestone may slip by
|
||||
a few days to ensure the code is sufficiently usable.
|
Loading…
x
Reference in New Issue
Block a user