<snip>
> There are also branches/releases for "doc" and "test" that need to be created 
> at the same time. This way we have all sources at the same level.
> 

I take care of that during the build, it is in my workflow
> Note however, that the source is placed into "main/branches/x.y.z/trunk" and 
> "doc/branches/x.y.z/trunk", but for the test directory the trunk subdirectory 
> does not exist, hence "test/branches/x.y.zā€œ.
> 

> We could either leave that as is, add the sources to "trunk" in "test" 
> ("test/branches/x.y.z/trunk") or remove "trunk" from "main/branches/x.y.z" 
> and "doc/branches/x.y.z". If changing the directory structure we need to make 
> sure that all scripts will continue to work correctly.
> 
> Any comments?
> 
I think that should be as it is, all test jobs rely on that, only the revision 
should be bumped, I would do that manually in all test jobs after a successful 
release
>> There is a /main/sandbox that is empty, is it allowed to put things in 
>> there? If so I could make a test before we go ahead.
> AFAIK no, "sandbox" is meant to allow developers to work on a feature off the 
> main trunk. The changes in the sandbox could be applied to trunk later or 
> removed, if the sandbox versions are not carried over.
> 
>> There is still the problem that the rexx -v reports the SVN version number 
>> of the release. I understand it should report something else (1?).
> IMHO there is no problem with the revision number at all. It gets also 
> reported in .RexxInfo~revision.
> 
>> Same goes for the naming of the built artifacts.
> Not sure what you mean here.
>> Maybe this works if built under a different branch than trunk? Anyone with 
>> understanding of how this works is welcome to explain, this was not solved 
>> for the 5.0.0 release.
> Again, could you elaborate please?
> 
The SVN revision is used to build the artifact name, there is a section in 
CMakeLists.txt for that. In that section there is code to change the number to 
something else than the SVN revision for a release. This code is not working. 
If all are fine with having the revision number in the Artifacts & the rexx -v 
than nothing needs to be done.

Example: If you build without working SVN (from a repository that is fixed) the 
code give out version ā€ž0ā€œ and that corrupts the naming of all artifacts AND the 
rexx -v reports 0.
> Best regards
> 
> ---rony
> 
> 
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to