Re: [twsocket] Using SourceForge for ICS ?
Francois PIETTE wrote: >> The goal is to make development easier for a workgroup isn't it? > > Yes, it is. > >> ICS can only benefit from such a concept. That must not mean >> to move the source to SourceForge, all we need is a server that >> runs SVN, 24 hours a day, ideally under your control. > > What are the requirement for such a server ? If there are just a few users members of the development team and main distribution of the source remains dowloading archives from your website I think that a ADSL line was totally OK. There's a svnserver that can be installed as a service and also a plugin for Apache (more secure, allows SSL) both well documented in the online help. > > -- > [EMAIL PROTECTED] > The author of the freeware multi-tier middleware MidWare > The author of the freeware Internet Component Suite (ICS) > http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
>> What are the requirement for such a server ? Not much. 1. Enough disk space to hold the growing repository 2. Connected to the Internet (hopefully with a firewall :) 3. Apache (to allow for web-based repository access, which is easier to maintain) Here's a link with a discussion on the subject: http://subversion.tigris.org/servlets/BrowseList?list=users&by=thread&from=330941 -dZ. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
> The goal is to make development easier for a workgroup isn't it? Yes, it is. > ICS can only benefit from such a concept. That must not mean > to move the source to SourceForge, all we need is a server that > runs SVN, 24 hours a day, ideally under your control. What are the requirement for such a server ? -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
Francois PIETTE wrote: >> very easy to maintain. If Francois does not want to put the >> SSL code into the project/repository as well ? I think we >> won't safe very much. What do you think? > > Currently I don't plan to put ICS-SSL on SourceForge. The goal is to make development easier for a workgroup isn't it? ICS can only benefit from such a concept. That must not mean to move the source to SourceForge, all we need is a server that runs SVN, 24 hours a day, ideally under your control. -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html > > -- > [EMAIL PROTECTED] > The author of the freeware multi-tier middleware MidWare > The author of the freeware Internet Component Suite (ICS) > http://www.overbyte.be > > > - Original Message - > From: "Arno Garrels" <[EMAIL PROTECTED]> > To: "ICS support mailing" > Sent: Monday, October 08, 2007 7:03 PM > Subject: Re: [twsocket] Using SourceForge for ICS ? > > >> DZ-Jay wrote: >>> On Oct 7, 2007, at 14:57, Arno Garrels wrote: >>> >>>> Isn't it safe to use the Copy-Modify-Merge solution, described in >>>> the online-help ? >>> >>> Yes, it is very safe. >> >> Now that I checked how to merge particular changes made in >> branches to the main source tree under trunk I would like >> to suggest the following, same structure for two different >> repositories one for V5 and one for V6: >> >> /icsv(n) >> |-branches >> | |-ics-ssl >> |-tags >> | |-ics-ssl >> | | |- beta(n) >> | |-ics >> | |- release(n) >> |-trunk >> |-ics >> >> Where the ics-ssl branch and tags cannot be accessed by >> common ics users. AFAIK it is only possible to merge >> between common and SSL when the SSL code is in the same >> repository, is that true? It works very well and makes it >> very easy to maintain. If Francois does not want to put the >> SSL code into the project/repository as well ? I think we >> won't safe very much. What do you think? >> >> -- >> Arno Garrels [TeamICS] >> http://www.overbyte.be/eng/overbyte/teamics.html >> >> >> >> >> -- >> To unsubscribe or change your settings for TWSocket mailing list >> please goto http://www.elists.org/mailman/listinfo/twsocket >> Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
--QUOTE: Arno Garrels It's the latter, however the point when V6 has been split from the common base is already some years back and hard to restore. There will be no new features in V5 so merging between V5 and V6 is most likely not required. Also revision numbers are incremented for the entire project/repository. But I could very well live with both in the same repository as well, locally I also treat them as two different projects. -- END. Ok, I understand. I was thinking that perhaps code fixes done to V6 may need to be merged with V5 for maintenance and legacy support, but I'm not sure if that will be case since the code may be so much different. About the revision numbers, do not think of them as version numbers -- they are _not_ -- they represent the revision number of the repository, and do not relate to any specific file, project or module; and in this, SVN is different than CVS and other version control systems. Project version numbers are usually maintained by tagging: You create a new "Tag" and call it "ICS_v6.5" or whatever (and add a log note specifying the revision number from where it was created, for reference). This marks a specific milestone or point in time in the repository as belonging to that version. The revision numbers are for internal repository use and code maintenance and administration; and they identify merely a change to the repository, not even which files where changed (although this is available in the revision log). SVN does not make any distinction between files, directories, projects, etc -- all those things are for the developer's convenience. To SVN, the repository is one big file stream, so adding a directory or a project means nothing but a change to the repository (like a diff patch), which increments its revision number. This is a very subtle point, but it is very important when dealing with SVN. Therefore, it makes no difference if all projects exist in the same repository or not, as long as your file organization is coherent. -dZ. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
[EMAIL PROTECTED] wrote: >> /icsv(n) >> |-branches >> | |-ics-ssl >> |-tags >> | |-ics-ssl >> | | |- beta(n) >> | |-ics >> | |- release(n) >> |-trunk >> |-ics > > There's a few questions I have with your suggested > structure: > > 1. Is ICS-SSL really a branch of ICS, or should it be > considered a separate project? It's no separate project. It shares most of the files with common ICS, most of the SSL code is available as .inc files compiled in conditionally. And it has its own demo-folder. > Branches, in my > opinion, should be temporary code paths destined to > eventually merge with the main trunk, Basically that's true, however think of it as a persistent branch, you can change everything however ever only merge those changes to the main trunk effecting the shared files. People can work with either common ICS or SSL and commit their changes. Merging with the branch or the other way around was very easy (allowed to admin users only). But I just read Francois reply, so this discussion is useless in any case. > > 2. Does ICS v6 represent a completely different > code-base than ICS v5, or is it a natural progression > for it? It's the latter, however the point when V6 has been split from the common base is already some years back and hard to restore. There will be no new features in V5 so merging between V5 and V6 is most likely not required. Also revision numbers are incremented for the entire project/repository. But I could very well live with both in the same repository as well, locally I also treat them as two different projects. -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html > If the former, then they indeed should be > separte projects. But if the latter, they should > form part of the same code base: If ICS v5 is > currently the "stable" version, and ICS v6 represents > a new version that will eventually supplant it, then > I suggest ICS v5 represent the main trunk, and ICS v6 > become a branch of it. Once ICS v6 matures and > replaces v5, it will be merged into the main trunk, > and v5 set as a Tag. But if v6 represents the > version where most development will be done, and v5 > is only for legacy support, then it should be the > other way around. > > Also, keep in mind that merging is done locally in > the user's working directory, not directly in the > repository. > To merge, you select a source path from > the repository, and specify which revisions to > include; SVN will then merge those changes with your > working directory (representing the target repository > path). Once all conflicts are resolved, the updated > (merged) working directory can be commited by the user. > > Therefore, it is possible for users to revert > accidentally changes commited previously, by > commiting "wrongly" merged files. The good thing is > that the changes were not lost (they are still in the > repository history), and can easily be returned. > > By "wrongly merged files", I mean that the user > mistakenly overwrote other's changes with his own or > with an older version of code. This is the scenario > that I alluded to before, and it is fairly common > among people who are not used to version control systems. > > -dZ. > > > >> --- Original Message --- >>> From: Arno Garrels[mailto:[EMAIL PROTECTED] >> Sent: 10/8/2007 1:03:09 PM >> To : twsocket@elists.org >> Cc : >> Subject : RE: Re: [twsocket] Using SourceForge for ICS ? >> > >DZ-Jay wrote: >> On Oct 7, 2007, at 14:57, Arno Garrels wrote: >> >>> Isn't it safe to use the Copy-Modify-Merge solution, described in >>> the online-help ? >> >> Yes, it is very safe. > > Now that I checked how to merge particular changes > made in > branches to the main source tree under trunk I would like > to suggest the following, same structure for two > different > repositories one for V5 and one for V6: > > /icsv(n) > |-branches > | |-ics-ssl > |-tags > | |-ics-ssl > | | |- beta(n) > | |-ics > | |- release(n) > |-trunk > |-ics > > Where the ics-ssl branch and tags cannot be accessed by > common ics users. AFAIK it is only possible to merge > between common and SSL when the SSL code is in the same > repository, is that true? It works very well and makes it > very easy to maintain. If Francois does not want to > put the > SSL code into the project/repository as well ? I think we > won't safe very much. What do you think? > > -- > Arno Garrels [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html > > > > > -- > To unsubscribe or change your settings for TWSocket > mailing list > please goto > http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
> But if v6 represents the version where most development > will be done, and v5 is only for legacy support That's it. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
Currently I don't plan to put ICS-SSL on SourceForge. I also wouldn't recommend it, until that time when you release it as open source (if ever you intend to do so). Still, it wouldn't hurt at all to set up SVN in your local machine to maintain the source :) -dZ. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
> /icsv(n) > |-branches > | |-ics-ssl > |-tags > | |-ics-ssl > | | |- beta(n) > | |-ics > | |- release(n) > |-trunk > |-ics There's a few questions I have with your suggested structure: 1. Is ICS-SSL really a branch of ICS, or should it be considered a separate project? Branches, in my opinion, should be temporary code paths destined to eventually merge with the main trunk, such as to add new features, fix bugs, etc. 2. Does ICS v6 represent a completely different code-base than ICS v5, or is it a natural progression for it? If the former, then they indeed should be separte projects. But if the latter, they should form part of the same code base: If ICS v5 is currently the "stable" version, and ICS v6 represents a new version that will eventually supplant it, then I suggest ICS v5 represent the main trunk, and ICS v6 become a branch of it. Once ICS v6 matures and replaces v5, it will be merged into the main trunk, and v5 set as a Tag. But if v6 represents the version where most development will be done, and v5 is only for legacy support, then it should be the other way around. Also, keep in mind that merging is done locally in the user's working directory, not directly in the repository. To merge, you select a source path from the repository, and specify which revisions to include; SVN will then merge those changes with your working directory (representing the target repository path). Once all conflicts are resolved, the updated (merged) working directory can be commited by the user. Therefore, it is possible for users to revert accidentally changes commited previously, by commiting "wrongly" merged files. The good thing is that the changes were not lost (they are still in the repository history), and can easily be returned. By "wrongly merged files", I mean that the user mistakenly overwrote other's changes with his own or with an older version of code. This is the scenario that I alluded to before, and it is fairly common among people who are not used to version control systems. -dZ. >--- Original Message --- >From: Arno Garrels[mailto:[EMAIL PROTECTED] >Sent: 10/8/2007 1:03:09 PM >To : twsocket@elists.org >Cc : >Subject : RE: Re: [twsocket] Using SourceForge for ICS ? > >DZ-Jay wrote: > On Oct 7, 2007, at 14:57, Arno Garrels wrote: > >> Isn't it safe to use the Copy-Modify-Merge solution, described in the >> online-help ? > > Yes, it is very safe. Now that I checked how to merge particular changes made in branches to the main source tree under trunk I would like to suggest the following, same structure for two different repositories one for V5 and one for V6: /icsv(n) |-branches | |-ics-ssl |-tags | |-ics-ssl | | |- beta(n) | |-ics | |- release(n) |-trunk |-ics Where the ics-ssl branch and tags cannot be accessed by common ics users. AFAIK it is only possible to merge between common and SSL when the SSL code is in the same repository, is that true? It works very well and makes it very easy to maintain. If Francois does not want to put the SSL code into the project/repository as well ? I think we won't safe very much. What do you think? -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
> very easy to maintain. If Francois does not want to put the > SSL code into the project/repository as well ? I think we > won't safe very much. What do you think? Currently I don't plan to put ICS-SSL on SourceForge. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be - Original Message - From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Monday, October 08, 2007 7:03 PM Subject: Re: [twsocket] Using SourceForge for ICS ? > DZ-Jay wrote: >> On Oct 7, 2007, at 14:57, Arno Garrels wrote: >> >>> Isn't it safe to use the Copy-Modify-Merge solution, described in the >>> online-help ? >> >> Yes, it is very safe. > > Now that I checked how to merge particular changes made in > branches to the main source tree under trunk I would like > to suggest the following, same structure for two different > repositories one for V5 and one for V6: > > /icsv(n) > |-branches > | |-ics-ssl > |-tags > | |-ics-ssl > | | |- beta(n) > | |-ics > | |- release(n) > |-trunk > |-ics > > Where the ics-ssl branch and tags cannot be accessed by > common ics users. AFAIK it is only possible to merge > between common and SSL when the SSL code is in the same > repository, is that true? It works very well and makes it > very easy to maintain. If Francois does not want to put the > SSL code into the project/repository as well ? I think we > won't safe very much. What do you think? > > -- > Arno Garrels [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html > > > > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
DZ-Jay wrote: > On Oct 7, 2007, at 14:57, Arno Garrels wrote: > >> Isn't it safe to use the Copy-Modify-Merge solution, described in the >> online-help ? > > Yes, it is very safe. Now that I checked how to merge particular changes made in branches to the main source tree under trunk I would like to suggest the following, same structure for two different repositories one for V5 and one for V6: /icsv(n) |-branches | |-ics-ssl |-tags | |-ics-ssl | | |- beta(n) | |-ics | |- release(n) |-trunk |-ics Where the ics-ssl branch and tags cannot be accessed by common ics users. AFAIK it is only possible to merge between common and SSL when the SSL code is in the same repository, is that true? It works very well and makes it very easy to maintain. If Francois does not want to put the SSL code into the project/repository as well ? I think we won't safe very much. What do you think? -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
On Oct 7, 2007, at 14:57, Arno Garrels wrote: > Isn't it safe to use the Copy-Modify-Merge solution, described in the > online-help ? Yes, it is very safe. Besides, all merging occurs on your working directory, and will not be committed automatically. And also, commits are transactional, so if anything fails, or conflicts, it won't be committed. My comment was because some people try to avoid merging, since it may be time consuming, as you have to determine which changes should override. But there isn't a problem with it. dZ. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
DZ-Jay wrote: > On Oct 5, 2007, at 02:49, Olivier Sannier wrote: > > SubVersion on the other hand was created to enable more efficient > collaboration, purely as a source control tool. You can mark files > with "requires lock", which will require a developer to acquire a lock > before committing changes. We use this mostly for sensitive files > where a merge gone awry may be critical; or for project documentation, > which should not change that often. In the case of ICS, for example, > *if* you were to use locking, I would suggest it on the highest files > of the TWSocket class hierarchy, which if changed, may affect all > other units. That way you make sure that, say, Francois and Arno > will not be changing the same things at the same time. Isn't it safe to use the Copy-Modify-Merge solution, described in the online-help ? -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
On Oct 5, 2007, at 02:49, Olivier Sannier wrote: > Yes, but it's not in the "spirit" of SVN and is not implemented like > people are used to when coming from, say, SourceSafe. > To me, this was put in to please a few users, but it must not become a > basis for a team work. In my opinion, Visual Source Safe is more of a project management control tool that happens to do version control too. Its strongest features are those that allow managers to control access to the code and delegate tasks by individual. SubVersion on the other hand was created to enable more efficient collaboration, purely as a source control tool. You can mark files with "requires lock", which will require a developer to acquire a lock before committing changes. We use this mostly for sensitive files where a merge gone awry may be critical; or for project documentation, which should not change that often. In the case of ICS, for example, *if* you were to use locking, I would suggest it on the highest files of the TWSocket class hierarchy, which if changed, may affect all other units. That way you make sure that, say, Francois and Arno will not be changing the same things at the same time. However, as you mentioned, this is contrary to the "spirit" of SVN, which promotes collaboration. If Francois and Arno want to change the same thing, then they *should* talk to each other and communicate and organize better, instead of relying on the software to block each other. That said, Francois, whether you choose to go to SourceForge or not, I strongly recommend you check out SVN: You will not regret it, and after doing your first revert or merge, you'll wonder how you ever worked without it! dZ. -- DZ-Jay [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
Dan wrote: > SVN does actually support locking files aswell. Useful for binary files that > you can't merge. > Yes, but it's not in the "spirit" of SVN and is not implemented like people are used to when coming from, say, SourceSafe. To me, this was put in to please a few users, but it must not become a basis for a team work. Regards Olivier -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Olivier Sannier > Sent: 02 October 2007 18:22 > To: ICS support mailing > Subject: Re: [twsocket] Using SourceForge for ICS ? > > SVN is meant to replace CVS so the natural choice would be SVN. AFAIK, > CVS services are only on SourceForge for legacy reasons but SVN is the > new favored backend. I personally much prefer SVN as it allows far > greater flexibility in terms of file operations, like move, renaming, > and the like. Of course, and its the same with both, you have to accept > the "never lock, always merge" mechanism but it comes naturally after > about 15 minutes of using it. > > If you have any question, please do not hesitate to contact me. > Cheers > Olivier > SVN does actually support locking files aswell. Useful for binary files that you can't merge. Dan -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
I've moved to SVN for all my projects. Its definitely superior to CVS. Glad you are finally choosing to use version control :) you wont regret it. Dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Francois PIETTE Sent: 02 October 2007 17:55 To: twsocket@elists.org Subject: [twsocket] Using SourceForge for ICS ? Hello Guys ! I'm considering the option of pushing ICS to SourceForge and I would like to have your opinion. Does someone already have a real experience of SourceForge as a developper ? The first decision is should I select CVS or SVN ? Any advice appreciated. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
Hello, > The first decision is should I select CVS or SVN ? > Any advice appreciated. I'm using SVN together with TortoiseSvn each day in my work for more than a year now. Did not have any serious problems since (the only thing that I stumbled over is the filename case-sensitivity issue - but that is the same for CVS AFAIK). One big advantage of SVN in my opinion is the fact that it does not require a server process. This comes handy for smaller projects, e.g. if I am the only developer or all developers are in the same LAN. This would not be the case with ICS on SourceForge, of course :-) And SVN comes with very good documentation. /Tobias -- NOA Audio Solutions Vertriebsges. m.b.H. Tel: +43-1-5452700 Johannagasse 42/4 Fax: +43-1-545270014 A - 1050 Wien Www: http://www.noa-audio.com -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
Arno Garrels wrote: > Maurizio Lotauro wrote: > > >> I see that jcl has switched from CVS to SVN, so probably it will be >> better to choice SVN. >> > > Yes, and TortoiseSVn looks like a very cool and powerfull tool on the > first glance! Trust me, the more you use, the better it gets. Been using it for public and private projects for over two years now, can't imagine living without such a tool now. Cheers Olivier -- Olivier Sannier JVCL Coordinator http://jvcl.sf.net/ Find more about me on LinkedIn: https://www.linkedin.com/in/obones -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
> Yes, and TortoiseSVn looks like a very cool > and powerfull tool on the first glance! It is. I don't need nor care about BDS integration anymore; I do all manipulations of the source files through the Explorer shell using TortoiseSVN. It even overlays the folder/file icons with symbols of their status (modified, conflict, updated, etc.). -dZ. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
Maurizio Lotauro wrote: > I see that jcl has switched from CVS to SVN, so probably it will be > better to choice SVN. Yes, and TortoiseSVn looks like a very cool and powerfull tool on the first glance! -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
Scrive Francois PIETTE <[EMAIL PROTECTED]>: > Hello Guys ! Hello! > I'm considering the option of pushing ICS to SourceForge and I would like to > have your opinion. > Does someone already have a real experience of SourceForge as a developper ? Sorry, no. > The first decision is should I select CVS or SVN ? I see that jcl has switched from CVS to SVN, so probably it will be better to choice SVN. Bye, Maurizio. This mail has been sent using Alpikom webmail system http://www.alpikom.it -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
SVN gets my vote. Darin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Francois PIETTE Sent: Tuesday, October 02, 2007 12:55 PM To: twsocket@elists.org Subject: [twsocket] Using SourceForge for ICS ? Hello Guys ! I'm considering the option of pushing ICS to SourceForge and I would like to have your opinion. Does someone already have a real experience of SourceForge as a developper ? The first decision is should I select CVS or SVN ? Any advice appreciated. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
Francois PIETTE wrote: > Hello Guys ! > > I'm considering the option of pushing ICS to SourceForge and I would like to > have your opinion. > That would be most excellent for me. > Does someone already have a real experience of SourceForge as a developper ? > Does the JVCL count as an experience? Both as a developer, then as an administrator for a few projects. Very nice site, very easy for file releases. > The first decision is should I select CVS or SVN ? > SVN is meant to replace CVS so the natural choice would be SVN. AFAIK, CVS services are only on SourceForge for legacy reasons but SVN is the new favored backend. I personally much prefer SVN as it allows far greater flexibility in terms of file operations, like move, renaming, and the like. Of course, and its the same with both, you have to accept the "never lock, always merge" mechanism but it comes naturally after about 15 minutes of using it. If you have any question, please do not hesitate to contact me. Cheers Olivier -- Olivier Sannier [EMAIL PROTECTED] http://www.obones.com/ Retrouvez-moi sur Viaduc : http://www.viaduc.com/invitationpersonnelle/0023asu3wwgwpzx -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
Hello: I've used SourceForge before, and it is a nice environment for distribution and project sharing and participation. I will suggest you use SubVersion (SVN) -- it is a considerably better than CVS. As a matter of fact, it was designed to overcome some of the limitations of CVS. SVN and CVS have different ways of working, so if you are used to using CVS, you'll have to unlearn some concepts and learn some new ones. It may seem confusing at first, but once you understand SubVersion's concepts, everything seems so natural. (even more so than with CVS, which is clunky). Plus, if you use the TortoiseSVN client, it integrates very nicely with the Windows Explorer (and I believe there's a BDS plug-in), so you'll never have to face the dreaded WinCVS GUI ever again. I've worked with SVN for the past few years, so I am willing to offer any assistance you may need. -dZ. >--- Original Message --- >From: Francois PIETTE[mailto:[EMAIL PROTECTED] >Sent: 10/2/2007 12:55:22 PM >To : twsocket@elists.org >Cc : >Subject : RE: [twsocket] Using SourceForge for ICS ? > >Hello Guys ! I'm considering the option of pushing ICS to SourceForge and I would like to have your opinion. Does someone already have a real experience of SourceForge as a developper ? The first decision is should I select CVS or SVN ? Any advice appreciated. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] Using SourceForge for ICS ?
Hello Guys ! I'm considering the option of pushing ICS to SourceForge and I would like to have your opinion. Does someone already have a real experience of SourceForge as a developper ? The first decision is should I select CVS or SVN ? Any advice appreciated. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
