>
> I dont think this would fit a standard project
> layout where we can tag all the scripts for each
> release. It also doesnt seem to make sense to create
> a module out of every script. Changes could be as
> frequent as multiple times a day to maybe once in
> two years. Almost all the changes result in an
> immediate release.
>
> Any thoughts or pointers would be highly
> appreciated.
>
>
what are the problems in creating a separate project
for each folder ?
Also, please provide information on how the scripts
will be deployed. It is a good practice to create
version control structure to mimic deployment.
regards
VK
Engineers normally have problem with every solution. If not they have a
solution in search of a problem.
Disclaimer
The facts expressed here belong to everybody, the opinions to me. The
distinction is yours to draw...
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
linux-india-help mailing list
linux-india-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-india-help
