Newsgroups : Borland : borland.public.delphi.internet.winsock : 2007 Nov : Re: Verison of Indy 10 without Memory Leak?
| Subject: | Re: Verison of Indy 10 without Memory Leak? |
| Posted by: | "Remy Lebeau (TeamB)" (no.spam@no.spam.com) |
| Date: | Wed, 7 Nov 2007 12:27:12 |
"Jamie Dale" <jamie.dale@yahoo.com> wrote in message
news:4731a63b$1@newsgroups.borland.com...
> To my understanding (Remy will correct me if I'm wrong) the code
> is shared to members of the Indy pit crew from one location - IE
> the server, and they work on it remotely.. or lock it, download it,
> work on it, upload and unlock it.
The latter is the case. That is standard source control behavior.
The Fulgan download server is a mirror, it is not the live VCS server. It
retreives the latest files from the VCS server nightly and packages them up
into zip files for users to download. Fulgan is not run by the Indy team.
It is a third party that the Indy team has granted access VCS to.
> Now unfortunately, to change that would undoubtedly mean a
> MAJOR change in the way the team does things (I think..).
What Steve is asking for is for the Indy team to periodically decide when
Indy's code is stable enough to package into a stable standalone
distribution, and then provide a releasable version of it with installation,
etc. That has nothing to do with the Fulgan mirror. That releasable stage
is what Indy has not done in a long time, and frankly, we don't have much
man power to do it right now. And with the constant changes that are being
made to Indy (especially with the upcoming Unicode changes), once a release
is made, it will be outdated fairly quickly.
> It might be a possibility for me to download it once a month,
> upload it to the site (or another server) and then link to that
> from the indy website.
That is not enough to guarantee stable releases, though. Changes made from
month to month need testing and validating, and that is where manpower is
really lacking right now.
Gambit