I'm not sure if I understand this correctly because from what I'm reading it seems like you're saying any particular change cannot be committed to the mainline...
At OOPSLA I handed out copies of a "quick reference card" for the SCM Pattern language. People liked it, so I put a PDF of it on the scmpatterns.com web site....
Steve, Does the refcard contain all SCM patterns? Frank. Steve Berczuk <steve@...> wrote: The card has a brief summary of each pattern and describes...
Hi Jason, No, that 's not what I intended to say. I wonder why you got the impression... Anyone can request a timeslot at any time. When there is no...
As it happens, someone pointed out that I left out "Unit Test." (but everyone knew that one anyway ;) ) I updated the PDF to include the missing pattern. ...
... I don't understand why you're merging back to the trunk in order to release. The purpose of the release branch would be to isolate yourself from other...
Have you looked at the release line pattern (chapter 17)? You appear to be using a release line to make bug fixes to the release in production. I am curious...
... Thank you for your reply, my apologies for not responding sooner. ... appear ... After further review, it seems that we are indeed using the release line...
Could you clarify which codeline contains the emergency fixes that are released to production? From what you stated in your posts, the emergency fixes are...
... Ok, here is the situation: The codeline that contains the emergency fixes is cut from the trunk when a release goes out. At that point, the emergency...
We use VSS here which doe snot have much of a branch merge feature so I was forced to use the same model as you do. Specifically, for each release ( service...
Hi, Our situation is a bit different ... we are using CVS here.. We have two branches from main line 'dev' and 'testing' branch... dev branch we use for...
After studying your reply I have a much better idea of how your organization uses branching. ... trunk ... and ... This sounds reasonable...even the merging of...
... development ... melting ... This puzzles me also and I don't see any benefit from doing this. ... merged ... the ... need ... I agree. I think the problem...
The branching approach that you describe below sounds reasonable. I assume you are not doing any development along the mainline, i.e., you only branch from the...
Those who followed the thread "Moving Integration Target Window" within the last month or so may recall a variety of codeline->sandbox and sandbox->codeline...
Hi, I have a real need for some Perforce scripts to import a file system into the depot. This script needs to compare files, and only update those files that...
... Hi Brooke! Did you take a peek at the Perforce related-software page at http://www.perforce.com/perforce/loadsupp.html Its a lot of user-contributed /...
I'd second the perforce user list recommendation. To get you started though, if I haven't misunderstood, what you are trying to do is import a load of files in...
Greetings- I currently am in search of a tool that helps correlate bugs to releases and uses cvs as the repository. I have seen cvstrac, but it doesn't seem...
... Hi Eric! When you say "uses CVS" do you mean CVS is the repository for the source-code, or do you mean CVS is used as the repository for the bugs? What are...
Thanks for the quick reply. I use CVS as a source code repository and currently have an internal change/incident/release ticket management system. We...
<PLAINTEXT> ... Are you looking (or open to) replacing the internal system above wth an open-source alternative such as Bugzilla (see bugzilla.org) or Scarab...
Hi, I'm having a bit of a problem picking out a strategy for dealing with "diamond-shaped" dependencies (which should be really common, so I just can't...
... Are these all physical (build-time) dependencies? I got the impression they are - is that correct? If my impression is correct - I'm uncertain where...
... with ... I just ... Perforce, so ... As opposed to run-time, or? Well, they are mostly build-time dependencies (compile + link). ... branches/branching ......