# HG changeset patch # User František Kučera # Date 1543345659 -3600 # Node ID 5697a01db3882f48219050b7c8e444bdf1bb44bd # Parent 7d7d4e1f293f80230354a469f176e3d145eb03ab roadmap diff -r 7d7d4e1f293f -r 5697a01db388 relpipe-data/classic-example.xml --- a/relpipe-data/classic-example.xml Tue Nov 27 17:12:12 2018 +0100 +++ b/relpipe-data/classic-example.xml Tue Nov 27 20:07:39 2018 +0100 @@ -116,7 +116,7 @@

- There are also other problems like character encoding, missing meta-data (e.g. field names and types), joining multiple files (Is there always a new-line character at the end of the file? Or is there a BOM at the beginning of the file?) + There are also other problems like character encoding, missing meta-data (e.g. field names and types), joining multiple files (Is there always a new-line character at the end of the file? Or is there some nasty BOM at the beginning of the file?) or passing several types of data in a single stream (we have list of animals and we can have e.g. also a list of foods or list of our staff where each list has different fields).

diff -r 7d7d4e1f293f -r 5697a01db388 relpipe-data/faq.xml --- a/relpipe-data/faq.xml Tue Nov 27 17:12:12 2018 +0100 +++ b/relpipe-data/faq.xml Tue Nov 27 20:07:39 2018 +0100 @@ -16,7 +16,7 @@ So it is not a big difference whether it will be released this month or the next one. We understand the release early, release often rule. But it fits better to application software than to standards and APIs. - Of course, we expect some evolution after the v1.0.0 release, but we need to stabilize and verify many things before the release in order to be able to maintain hackward compatibility in future. + Of course, we expect some evolution after the v1.0.0 release, but we need to stabilize and verify many things before the release in order to be able to maintain backward compatibility in future.

diff -r 7d7d4e1f293f -r 5697a01db388 relpipe-data/roadmap.xml --- a/relpipe-data/roadmap.xml Tue Nov 27 17:12:12 2018 +0100 +++ b/relpipe-data/roadmap.xml Tue Nov 27 20:07:39 2018 +0100 @@ -8,8 +8,218 @@

- The world is relational! + Releases before v1.0.0 are development and are not intended for production use. + Releases after v1.0.0 should follow the rules of Semantic versioning. +

+ +

v0.8

+ +

+ First public release for brave and courageous. +

+ +

Data types

+ +

Inputs

+ +

Transformations

+ +

Outputs

+ + + +

v0.9, v0.10, v0.11 etc.

+ +

+ Releases for discussion and verification of the format and API design. +

+ +

Data types

+ + +

Inputs

+ +

Transformations

+ +

Outputs

+ + + +

v1.0

+ +

+ First version for production use. + Brings no new features, just stabilized result of previous development. + Stable must be: +

+ + + +

+ Other parts might be released as stable later. +

+

+ After this point, all components (the format specification, particular libraries and particular tools) + will be versioned independently and the compatibility matrix will be maintained.

+ +

Further versions

+

+ Plans for next decades: +

+ +

Data types

+ +

Inputs

+

Systems, commands:

+ + +

Formats:

+ +

Transformations

+ +

Outputs

+ + +

Libraries and tools

+

Readers (SAX-like parsers) and writers (generators) for:

+ +

Other libraries and tools:

+ + +