On 13/02/2013 11:56, Christian Schneider wrote:
I think labels would not help a lot. Labels allow to mark several pages
to belong to the same theme. But we need just one page per version.
This is how camel does it:
http://camel.apache.org/download.html
http://camel.apache.org/camel-2103-release.
I think labels would not help a lot. Labels allow to mark several pages
to belong to the same theme. But we need just one page per version.
This is how camel does it:
http://camel.apache.org/download.html
http://camel.apache.org/camel-2103-release.html
http://camel.apache.org/camel-295-release.htm
On 13/02/2013 10:41, Christian Schneider wrote:
I think the release pages are not really versioned content like code.
All pages are visible in parallel.
Of course...
The name only makes it easier for users to see what each release is.
Look at what Atlassian does for Confluence own documenta
I think the release pages are not really versioned content like code.
All pages are visible in parallel.
The name only makes it easier for users to see what each release is.
Christian
On 13.02.2013 10:04, Francesco Chicchiriccò wrote:
> On 13/02/2013 09:49, Christian Schneider wrote:
>> Hi all,
>
On 13/02/2013 09:49, Christian Schneider wrote:
Hi all,
our current wiki pages for the minor releases only have names. While
experienced syncope users may already know which version number this
correlates to new users will have no clue.
So I propose to add the version number to the names of the
Hi all,
our current wiki pages for the minor releases only have names. While
experienced syncope users may already know which version number this
correlates to new users will have no clue.
So I propose to add the version number to the names of the wiki pages
like this:
0.5 - Crescendo
0.6 - Sost
