Loading ...
Sorry, an error occurred while loading the content.
Skip to search.

Messages List

160447

Re: Early history of CI / How did version control & CI work on the C

Hi … ... We were all working on a single system: for a brief time, one might be working on a “branch” but the intention was to remain integrated "all the
Ron Jeffries
Apr 15
#160447
 
160446

Re: Early history of CI / How did version control & CI work on the C

Thanks, that's very interesting. Was the ENVY server a separate server or did it run on the integration machine? And were the nightly tests triggered by
martijn_meijering
Apr 15
#160446
 
160445

Re: Early history of CI / How did version control & CI work on the C

i think of the central repo in git as being more of a central *sync* than a central *repo*. it's the place i can go to keep my repo up to date with everyone
Michael Hill
Apr 11
#160445
 
160444

Re: Early history of CI / How did version control & CI work on the C

Hi, I think it never occurred to us to do it differently. Our previous source control experience was with Panvalet, which was in no way distributed. It made
Chet Hendrickson
Apr 11
#160444
 
160443

Re: Early history of CI / How did version control & CI work on the C

I suspected it might be something like that. But as I understand it, ENVY already has a way to have a designated latest and greatest version among all the
martijn_meijering
Apr 11
#160443
 
160442

Re: Early history of CI / How did version control & CI work on the C

On Sun, Apr 9, 2017 at 8:50 AM, martijn@... [extremeprogramming] < ... Okay, I'll bite... the authoritative central server is not needed for technical
David Nicol
Apr 11
#160442
 
160441

Early history of CI / How did version control & CI work on the Chrys

Hello all, I have a few historical questions after being away from this group for more than 10 years... Because I've never more than played with Smalltalk I'm
martijn_meijering
Apr 9
#160441
 
160440

Re: Frontend/backend team with different technology stacks

Thank you all for your replies, I will keep them in mind as we go forward! ... I was actually a proponent of a joint feature team. The whole story is that I
Jan Michelfeit
Feb 28
#160440
 
160439

Re: Frontend/backend team with different technology stacks

On Sat, Feb 25, 2017 at 6:06 PM, Eb amaeze@... [extremeprogramming] < ... If a unified team is too large, two separate full-stack feature teams is better
Steven Gordon
Feb 25
#160439
 
160438

Re: Frontend/backend team with different technology stacks

Hi Jan - ... What is the cost of joining the two groups together? How many people in total are we looking at that would be in this new team? Eb -- blog:
Eb
Feb 25
#160438
 
160437

Re: Frontend/backend team with different technology stacks

If Team A speaks Language A and Team B speaks Language B, and you want Teams A & B to work on the shipping the same system, how do they intend to speak? It
Michael Hill
Feb 25
#160437
 
160436

Re: Frontend/backend team with different technology stacks

20+ years of development across several industries, in shops not knowing from agile, shops claiming to be Agile (and not really being so) and shops quite
Larry Brunelle
Feb 25
#160436
 
160435

Re: Frontend/backend team with different technology stacks

Jan, I am curious how your team(s) are handling testing. Is testing also siloed? If not, how was that accomplished?
Steven Gordon
Feb 25
#160435
 
160434

Re: Frontend/backend team with different technology stacks

Hi Jan, ... Well, the point of cross-functional teams is that the individuals may share little knowledge but together they have enough to b build a whole
Ron Jeffries
Feb 25
#160434
 
160433

Re: Frontend/backend team with different technology stacks

Hello Jan. IMO you should build a cross-functional team by all means. "To help each other" not just means doing pair programming sessions. It also means to **
Alexander Kriegisch
Feb 25
#160433
 
View First Topic Go to View Last Topic