[Rainbowportal-devel] Re: CVS Cleanup announce and a request for feedback

[Emmanuele De A. <ma...@gm...>]

This command was issued to sourceforge.
You can track here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1071803&group_id=1&atid=200001

Be aware of all the issues i have pointed out before.
The project taken from CVS will not build until the project is changed
to reflect the move. Please BACKUP you local copy before update from
cvs.
This will be approx 48 hours after sourceforge will confirm the move
and all went fine on sf cvs side.
I will post here the result. Please stay tuned.

Manu


On Fri, 19 Nov 2004 11:23:16 +0100, Emmanuele De Andreis
<ma...@gm...> wrote:
> This is an announce and a request for feedback.
> I have scheduled these changes to be issued to source forge team on Monday.
> 
> CVS Cleanup: rainbowportal
> 
> I want to clean up the rainbow project tree.
> This is the first phase of a multiple phase clean up
> 
> ****************************************
> PHASE 1
> ****************************************
> In this phase I will move all code to a single tree.
> The path will resemble the namespace.
> 
> Why:
> Easy of deployment (code directory can safely remain on your development pc)
> Easy of management (it is easy to find a cs file)
> 
> Directory affected (and all subfolders of them):
> /cvsroot/rainbowportal/CVSROOT/Rainbow/BLL
> /cvsroot/rainbowportal/CVSROOT/Rainbow/Configuration
> /cvsroot/rainbowportal/CVSROOT/Rainbow/Helpers
> /cvsroot/rainbowportal/CVSROOT/Rainbow/KickStarter
> /cvsroot/rainbowportal/CVSROOT/Rainbow/Security
> /cvsroot/rainbowportal/CVSROOT/Rainbow/Service
> /cvsroot/rainbowportal/CVSROOT/Rainbow/UI
> 
> Will be moved to:
> /cvsroot/rainbowportal/CVSROOT/app_code/Rainbow
> 
> Why 'app_code'?
> app_code is the new convention chosen by aspnet 2.0 for store code
> related files.
> Rainbow is the default namespace every class have in rainbow.dll
> This will let us in future have other namespaces without mixing files.
> 
> Users affected:
> CVS users and developers.
> 
> Excpected issues:
> Minimal: we move only files. Namespaces and classes remain unchanged.
> If you use CVS you may loose you changes at first commit after the
> move, please backup any changes not committed before update.
> Rainbow cvs may not compile until solution is not upgraded to reflect
> new code position. This may happen a couple of day after moving.
> Embedded resource can be affected since moving means changing namespace.
> 
> ****************************************
> PHASE 2
> ****************************************
> In this phase I will move ecommerce related things to a separate module.
> Module will be called 'ecommerce' or 'modules/ecommerce' or
> 'extensions/ecommerce'
> 
> Why:
> Rainbow core will be lighter.
> Ecommerce can be easily get from cvs any time.
> Rainbow core distributing (zipped or msi), will not include ecommerce
> anymore, but it will be available as separate download.
> 
> Directory affected (and all subfolders of them):
> /cvsroot/rainbowportal/CVSROOT/Rainbow/ECommerce
> /cvsroot/rainbowportal/CVSROOT/BankGateway
> 
> Files affected:
> /cvsroot/rainbowportal/CVSROOT/Rainbow/Ecommerce Nant Readme.txt
> /cvsroot/rainbowportal/CVSROOT/Rainbow/Ecommerce.build
> /cvsroot/rainbowportal/CVSROOT/Rainbow/ECommerce.csproj
> /cvsroot/rainbowportal/CVSROOT/Rainbow/ECommerce.csproj.webinfo
> /cvsroot/rainbowportal/CVSROOT/Rainbow/ECommerce.sln
> /cvsroot/rainbowportal/CVSROOT/Rainbow/ECommerce.suo
> /cvsroot/rainbowportal/CVSROOT/Rainbow/Ecommvs2nant.bat
> /cvsroot/rainbowportal/CVSROOT/Rainbow/UseEcommerceSolution.txt
> 
> Will be moved to:
> /cvsroot/rainbowportal/ecommerce
> 
> Alternatives:
> /cvsroot/rainbowportal/modules/ecommerce
> /cvsroot/rainbowportal/extensions/ecommerce
> 
> Users affected:
> CVS users and Ecommerce users.
> 
> Expected issues:
> Ecommerce users will have to install upgrades to ecommerce manually.
> If you use CVS you may loose you changes at first commit after the
> move, please backup any changes not committed before update.
>