Add CMake version variables and tag repository

[jcfr]

No description provided.

[jcfr]

@thewtex @pieper @hjmjohnson @millerjv @finetjul @naucoin

Hi Folks,

Following request to tag a version of the SlicerExecutionModel, I just introduced corresponding CMake variables and set the version to be 1.0.0. Let me know what you think.

Introducing a version would also help keeping track of the change related to the XML structure associated with CLI.

Currently (thanks to @finetjul) we have a XSD schema but there are no clear roadmap allowing our collaborators to know what the plan is ...

[thewtex]

+1

What is the versioning plan with regards to the schema? Schema additions
in a minor release bump? Backwards incompatible schema changes in a major
release bump?

On Mon, Oct 21, 2013 at 5:39 PM, Jean-Christophe Fillion-Robin <
[email protected]> wrote:

@thewtex https://github.com/thewtex @pieper https://github.com/pieper
@hjmjohnson https://github.com/hjmjohnson @millerjvhttps://github.com/millerjv
@finetjul https://github.com/finetjul @naucoinhttps://github.com/naucoin

Hi Folks,

Following request to tag a version of the SlicerExecutionModel, I just
introduced corresponding CMake variables and set the version to be 1.0.0.
Let me know what you think.

Introducing a version would also help keeping track of the change related
to the XML structure associated with CLI.

Currently (thanks to @finetjul https://github.com/finetjul) we have a XSD
schemahttps://github.com/Slicer/SlicerExecutionModel/blob/master/ModuleDescriptionParser/ModuleDescription.xsdbut there are no clear roadmap allowing our collaborators to know what the
plan is ...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/21#issuecomment-26738786
.

[hjmjohnson]

This looks like a good plan Matt.

From: Matt McCormick [email protected]
Reply-To: Slicer/SlicerExecutionModel
<reply+i-21330520-9d6bc595f3c2a956bb89b011c89286d8d0c01f3f-313970@reply.gith
ub.com>
Date: Monday, October 21, 2013 1:14 PM
To: Slicer/SlicerExecutionModel [email protected]
Cc: Hans Johnson [email protected]
Subject: Re: [SlicerExecutionModel] Add CMake version variables and tag
repository (#21)

+1

What is the versioning plan with regards to the schema? Schema additions
in a minor release bump? Backwards incompatible schema changes in a major
release bump?

On Mon, Oct 21, 2013 at 5:39 PM, Jean-Christophe Fillion-Robin <
[email protected]> wrote:

@thewtex https://github.com/thewtex @pieper https://github.com/pieper
@hjmjohnson https://github.com/hjmjohnson
@millerjvhttps://github.com/millerjv
@finetjul https://github.com/finetjul @naucoinhttps://github.com/naucoin

Hi Folks,

Following request to tag a version of the SlicerExecutionModel, I just
introduced corresponding CMake variables and set the version to be 1.0.0.
Let me know what you think.

Introducing a version would also help keeping track of the change related
to the XML structure associated with CLI.

Currently (thanks to @finetjul https://github.com/finetjul) we have a XSD

schema<https://github.com/Slicer/SlicerExecutionModel/blob/master/ModuleDescript
ionParser/ModuleDescription.xsd>but there are no clear roadmap allowing our
collaborators to know what the
plan is ...

‹
Reply to this email directly or view it on
GitHub<#21 (comment)
38786>
.

‹
Reply to this email directly or view it on GitHub
<#21 (comment)
759> .

[millerjv]

My recollection is that the Schema does not match the XML parser.