6 messages in com.perforce.perforce-userYee ha! Was "Re: Can't retrieve by da...| From | Sent On | Attachments |
|---|---|---|
| Pete...@auspex.com | 13 Mar 1998 15:00 | |
| WesP...@xmission.com | 17 Mar 1998 18:57 | |
| Kevi...@Auspex.Com | 18 Mar 1998 12:11 | |
| WesP...@xmission.com | 18 Mar 1998 13:45 | |
| Pete...@auspex.com | 18 Mar 1998 13:55 | |
| Kevi...@Auspex.Com | 18 Mar 1998 14:03 |
| Subject: | Yee ha! Was "Re: Can't retrieve by date?"![]() |
|---|---|
| From: | Pete...@auspex.com (Pete...@auspex.com) |
| Date: | 03/13/1998 03:00:11 PM |
| List: | com.perforce.perforce-user |
Chris:
There's no news like good news!
I hate to jump in here, because I think I'm about to get skewered.
Not likely. You're right on.
The intent of atomic changes with monotonically increasing numbers is to make it possible for people to "grok" (get their mind around) their depot. You can say, with relative ease and confidence, that your depot has taken N discrete steps since some milestone. That's not easy to do with RCS, CVS, or even many Very Expensive SCM Systems.
Agreed 100+10%
So as it turns out, we have put support for using "@date time" as a revision indicator into our upcoming 98.2 release. We plan to look and see where else dates make sense (and culling through this wad of mail will be part of that).
I think I can provide some concrete examples, but think globally. I hate to introduce the 3 most expensive words in home improvement, "While we're here," but could you allow for DATE RANGES rather than simply UP TO DATE functionality. And of course, nothing you do should destroy the sacred atomicity your system so consistently provides.
In general, we recognize that more flexible reporting would be good. For now, we're solving specific problems until the big picture comes into focus.
A fine strategy.
| Maybe we need some The Zen of Perforce SCM white papers. ;)
Oddly enough, we're about to post to our web pages a draft of our "SCM Best Practices" paper that will be presented at the SCM8 conference in Brussels in July. We're also participating in the Chili-PLOP next week in the workgroup on SCM (Best Practice) Patterns. We expect something usable will come of that.
Very cool. We might have some ideas for that as we proceed with our ClearQuality / Perforce integration.
Thanks Much, Christopher!
Peter ===================== Peter DiPrete Consultant, ITE Corp pdiprete at auspex.com Office: (408)566-2432 Cellular: (408)221-1601 Pager (numeric): (888)533-3727, PIN# 4082211601 Pager (text): 4082211601 at paging.cellone-sf.com




