| Title: | PATHWORKS for Windows 95 |
| Notice: | PWW95 1.0A Available -- See notes 3.39 and 8.7 |
| Moderator: | JAMIN::SYSTEM ROM |
| Created: | Thu Nov 17 1994 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 646 |
| Total number of notes: | 2900 |
Does anyone object to write locking this notes file? Jeff
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 639.1 | $.02 | VMSNET::mickey.alf.dec.com::s_vore | Smile, Mickey's watching! [email protected] | Fri May 02 1997 07:31 | 8 |
Well, there are still customers out there running 1.0/1.0A, and this is still a good place to ask about yet-unseen problems. I do agree that most folks should be pointed at PW32, but there are always customers who won't pay for an upgrade -- see the PCSA 4.x debacle *still* going on! | |||||
| 639.2 | JAMIN::WASSER | John A. Wasser | Fri May 02 1997 11:10 | 17 | |
> Does anyone object to write locking this notes file? I assume that we still have to maintain PWW95 V1.0A for a while (I don't know when it will be officially unsupported). I would prefer to see the file open till then. It might be useful to create a LEGACY_PATHWORKS conference to cover all releases prior to the currently shipping release. If that were done I would have no objection to locking a version-specific conference as soon as a replacement product ships. It might be a good idea to rename the locked conference to something like PWW95_ARCHIVED to be sure people know that the conference is locked. A single-note, write-locked conference under the old name could point to the LEGACY_PATHWORKS conference. | |||||