[wsf-c-dev] Configuration management with WSF projects

[Samisa Abeysinghe]

Given that everybody seems to be happy with the proposal, here is the 
initial process for branching WSF/C for dependent projects:

1. svn up WSF/C and ensure that everything builds, note down the 
revision number for externals such as Axis2/C
2. svn propedit svn:externals . WSF/C and set the revision number of the 
externals to that found in step one
3. svn cp https://wso2.org/repos/wso2/trunk/wsf/c/ 
https://wso2.org/repos/wso2/branches/wsf/c/ddmmyy Replace ddmmyy with 
current date. If you want to do the copy more than once in a given date 
suffix ddmmyy with 01, 02 etc.
4. svn propedit svn:externals . WSF/C and drop the revision numbers
5. svn propedit svn:externals . the dependent project and set 
https://wso2.org/repos/wso2/branches/wsf/c/ddmmyy as WSF/C external

NOTE: Please do not commit anything to the 
https://wso2.org/repos/wso2/branches/wsf/c/ddmmyy branch of WSF/C, you 
have to always commit to https://wso2.org/repos/wso2/trunk/wsf/c/ 
anything that is WSF/C related. As a best practice, always keep a 
separate https://wso2.org/repos/wso2/trunk/wsf/c/ checkout with you.

Thanks,
Samisa...

Chintana Wilamuna wrote:
> On Thu, 12 Jul 2007 10:04:23 +0600, Samisa Abeysinghe <samisa at wso2.com>
> wrote:
>
>   
>>     Instead of using the WSF/C svn head as external dependency for 
>> projects like WSF/PHP, I propose that we use a copy of WSF/C svn made
>> in the branch section. This way we will get away form the problems of
>> an unstable WSF/C svn head due to active development. If a dependent 
>> project needs a new fix in WSF/C, they need to get it fixed in the
>> WSF/C svn head and get a copy of that on to branch and extern on that.
>>     
>
> I too, am cool with this.
>
> Bye,
>
>     -Chintana
>
>   


-- 
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal)