On 4/3/07, Tom C wrote:
> On Tuesday 03 Apr 2007, Dinner wrote:
> > As always, the PITA of linking or sharing components is that you gotta
> > really test everything that uses that component whenever you make a
> > change to it. It's harder to stage roll-outs when code is shared, and
>
> Not reall
On Tuesday 03 Apr 2007, Dinner wrote:
> As always, the PITA of linking or sharing components is that you gotta
> really test everything that uses that component whenever you make a
> change to it. It's harder to stage roll-outs when code is shared, and
Not really - remember you can peg an svn:ext
On 4/2/07, Dinner <[EMAIL PROTECTED]> wrote:
>
>
> It's a good recurring thread, that one about "do all projects move along
> as
> you do, just the ones you're currently working on"...
Until just recently, I was essentially the only person doing 99% of the web
work in our department. One of my c
On 4/2/07, Rick R wrote:
> The tricky part is cases where applications share files for example, I
> have an "include" directory at my web root which contains images, css files,
> and a few cfm files that are used not only across various applications
> within the main web site, but across mult
On 4/2/07, Tom Chiverton <[EMAIL PROTECTED]> wrote:
>
>
> > What if I have multiple coldfusion applications residing on a given web
> > site (for example, www.it.dev.duke.edu has *MANY* "applications")
>
> I'd go with
> /customer/sitename/appname
> or
> /sitename/appname
> though if you sell the sa
On Monday 02 Apr 2007, Rick Root wrote:
> The problem here of course is that *ALL* of the flex project files are part
> of version control, including the project properties and such... which
> seems to make life difficult for having multiple developers working on the
> same flex application.
So ad
Rick,
According to the best practices each project should have its own repository,
now if in your case you have a main repository, you can have projects
underneath but they must have there own trunk / branches / tags. Which I am
not sure if you have, so if you need to switch to a particular versio
So we've been using Subversion to track changes to our web site applications
for a few months now, and I don't think we're doing it "right"
when I set up the subversion server originally, I set up a single repository
which holds everything we want to maintain version control for... each web
site
8 matches
Mail list logo
