Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 209.85.128.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20140323211910.DA2842388993@eris.apache.org>
References: <20140323211910.DA2842388993@eris.apache.org>
Date: Mon, 24 Mar 2014 15:52:37 +0000
Message-ID: 
 <CAOGo0VaC7k_nMC48oQqN5DWgY_yfizBz6zqUV_ivmibR-f35zA@mail.gmail.com>
Subject: Re: svn propchange: r1580369 - svn:log
From: sebb <sebbaz@gmail.com>
To: dev@commons.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Note that SVN commit messages are not versioned, so can be replaced at
any time (and then only live on in mail archives).
But the main issue is that the ASF releases source, and svn log
messages are not included the standard releases.

IMO SVN log messages should be regarded as short-term comments which
tell the commit message viewer why the update was committed, and are
mostly useful for reviewing the commit message.

If any of the information in the log message is necessary to the
understanding of the code, it really needs to be added to the Javadoc
or some other documentation file that is included in the source
releases.


On 23 March 2014 21:19,  <ate@apache.org> wrote:
> Author: ate
> Revision: 1580369
> Modified property: svn:log
>
> Modified: svn:log at Sun Mar 23 21:19:10 2014
> ------------------------------------------------------------------------------
> --- svn:log (original)
> +++ svn:log Sun Mar 23 21:19:10 2014
> @@ -1 +1,42 @@
> -SCXML-200:
> +SCXML-200:Normalize and complete the SCXML object model and parsing
> +See: https://issues.apache.org/jira/browse/SCXML-200
> +
> +The Commons SCXML object model was rather 'flat' and de-normalized, and many
> +of the current SCXML specification features as well as restrictions were
> +(thus) not fully mapped.
> +
> +This commit restructures the SCXML model to bring it more/mostly in line
> +with the specification and normalizes the object hierarchy to cleaner separate
> +and restrict the features belonging to the right level and element.
> +
> +The previous state and transition model hierarchy was like this:
> +
> +  TransitionTarget
> +    <- Initial
> +    <- History
> +    <- State
> +         <- Final
> +    <- Parallel
> +
> +  Executable
> +    <- Transition
> +
> +With this restructuring it will now looks like this:
> +
> +  Initial
> +
> +  TransitionTarget
> +    <- History
> +    <- EnterableState -> DocumentOrder
> +         <- TransitionalState
> +              <- State
> +              <- Parallel
> +         <- Final
> +
> +  Executable
> +    <- SimpleTransition
> +         <- Transition -> DocumentOrder
> +
> +With this restructuring, each of the model objects now cleanly
> +represents their functional role in the SCXML specification and only
> +contains the features and relations they are supposed to have.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org