Re: Organising apps in svn

"Dr. Christian Böttger" <[email protected]>
Newsgroups gmane.comp.web.phpgroupware.devel
Organization Dr. Böttger IT_Beratung & Projektmana gement
Message-ID <[email protected]>
Maât schrieb:


> For svn trees organisation this is only a question of keeping things 
> "stupid simple"... and hiding communication about apps statuses  inside 
> the pathes of  svn repos will make phpgw even harder to get in that it 
> is now i think.

basically we have two independent sorting criteria here: core, devtools, 
applications on one hand (regardless of status) and features criteria 
like supported, orphaned, ... on the other. Perhaps even a thrid, again 
indepented set like minimal setup, standrd, full, <various flavors).

Isn't that what tags etc are for? Moving around applications from one 
tree to another on status change seems to be unnatural to any version 
control system. But having a logical tag named "supported apps" or 
"phpGW taylored for <whatever>" resulting in the checkout of all code in 
that status (core + apps) can be a very handy feature.

It's not "hiding the information in the path name", it's more "putting 
it in there additionally" - more communication.

just my 2¢

Regards

CB

-- 
*****    Open Source und Linux im professionellen Einsatz    *****
Dr. Christian Böttger (Dipl.Phys.) DF5OP        Open Source Broker
EMail [email protected] / [email protected]
http://www.boettger.cc/          http://www.mydarc.de/df5op/
OpenBC: http://www.openbc.com/go/invuid/Christian_Boettger2
LinkedIn:  https://www.linkedin.com/in/christianboettger
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.