[Perl-workflow-devel] Working on maintenance release

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hello All,

I am currently quite busy with work, but that does not mean that  
Workflow has been put totally on ice.

I am working on the next maintenance release currently and I have  
migrated from CVS to Subversion.
I have adapted the patch from Jim Brandt (thanks Jim).

Since Subversion uses a different revision number format I have  
adapted all of the version numbers
from release 0.26 as versions for out components, this mean that  
these no longer are automatically
updated. We have to do this by hand from now on. I do however only  
recommend increasing these if
major changes are made. So POD additions and occasional whitespace/ 
curly flip-flopping does not
require a version update.

I have tested some more components, here follows the current test  
coverage report:

---------------------------- ------ ------ ------ ------ ------  
------ ------
File                           stmt   bran   cond    sub    pod    
time  total
---------------------------- ------ ------ ------ ------ ------  
------ ------
blib/lib/Workflow.pm           76.4   48.4   40.0   81.8  100.0     
2.4   67.6
blib/lib/Workflow/Action.pm    87.7   66.7    n/a   80.0   88.9     
1.1   85.6
...flow/Action/InputField.pm   78.1   65.4   50.0   70.0   83.3     
1.0   72.8
...Workflow/Action/Mailer.pm   85.7    n/a    n/a   66.7    n/a     
0.0   80.0
...b/Workflow/Action/Null.pm  100.0    n/a    n/a  100.0  100.0     
0.1  100.0
blib/lib/Workflow/Base.pm      96.4   86.4  100.0  100.0  100.0     
2.7   94.8
...lib/Workflow/Condition.pm   84.6    n/a    n/a   80.0  100.0     
0.2   85.0
...low/Condition/Evaluate.pm   41.7    0.0    0.0   71.4  100.0     
0.4   33.9
...flow/Condition/HasUser.pm   52.2    0.0    0.0   66.7  100.0     
0.0   45.9
blib/lib/Workflow/Config.pm    87.5   62.5    0.0   90.9  100.0     
2.1   80.5
...b/Workflow/Config/Perl.pm   96.6   72.2   66.7  100.0  100.0     
2.1   91.0
...ib/Workflow/Config/XML.pm   97.8   60.0   60.0  100.0  100.0     
2.3   85.7
blib/lib/Workflow/Context.pm  100.0    n/a    n/a  100.0  100.0     
0.1  100.0
...lib/Workflow/Exception.pm   70.6   50.0    n/a   63.6   16.7     
1.0   62.3
blib/lib/Workflow/Factory.pm   88.8   61.7   41.5   97.1   92.3     
7.1   77.5
blib/lib/Workflow/History.pm   92.0   83.3    n/a   87.5   60.0     
0.7   86.4
...lib/Workflow/Persister.pm   72.7   75.0   57.1   57.1   60.0     
0.4   68.4
...Workflow/Persister/DBI.pm   72.6   42.3   25.0   80.8   92.9     
1.5   63.1
...er/DBI/AutoGeneratedId.pm   36.4    0.0    n/a   57.1   33.3     
0.1   27.0
...ersister/DBI/ExtraData.pm   21.8    0.0    0.0   66.7   50.0     
0.1   18.5
...rsister/DBI/SequenceId.pm   51.7    0.0    0.0   71.4    0.0     
0.1   44.4
...orkflow/Persister/File.pm   94.2   48.0   33.3  100.0   75.0    
70.0   81.6
...low/Persister/RandomId.pm  100.0    n/a  100.0  100.0   33.3     
0.4   92.0
...rkflow/Persister/SPOPS.pm   89.2   50.0    n/a  100.0  100.0     
0.1   84.4
...orkflow/Persister/UUID.pm  100.0    n/a    n/a  100.0    0.0     
0.2   85.0
blib/lib/Workflow/State.pm     47.0   16.3   23.8   77.3   91.7     
2.4   40.1
...lib/Workflow/Validator.pm   86.7  100.0    n/a   80.0  100.0     
0.5   87.5
...dator/HasRequiredField.pm   88.2   50.0    n/a  100.0  100.0     
0.2   84.6
...dator/InEnumeratedType.pm   90.0   66.7    n/a   87.5  100.0     
0.2   87.5
...ator/MatchesDateFormat.pm   81.5   50.0   33.3  100.0  100.0     
0.4   74.5
Total                          76.9   46.1   35.4   84.4   79.7   
100.0   68.7
---------------------------- ------ ------ ------ ------ ------  
------ ------

I finally got SPOPS installed and with my latest test additions our  
test coverage has risen to: 68.7 percent

For the record release 0.25 had a coverage of 67.2 percent.

The goal is to get as close as possible to the 100%. The next step to  
follow this will be a major static code
analysis using Perl::Critic with proper and useful policies. Then  
will follow a major refactoring based on the
Perl::Critic reports.

I am not decided, but when this is completed perhaps we should label  
the release 1.0.0

The maintenance release will follow sometime shortly, I just want to  
add some more POD, since the POD
coverage is pretty bad.

Any thoughts, suggestions or anything?

jonasbn