Subject:
|
bug report: "cert." list on tracker
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Sun, 5 May 2002 19:38:56 GMT
|
Viewed:
|
411 times
|
| |
|
|
Steve,
There is a "bug" with the certification list on the tracker. It is considering
any primitive listed in the tracker to be a "subfile", regardless of whether or
not that primitive already exists in the field (i.e., has already been included
in a previous release). Thus, any new version of such a primitive will cause
the tracker to say that all files using this primitive "have uncertified
files."
In my opinion, this is flawed logic. An "uncertified subfile" should be a
*subpart* or a *new* primitive; i.e., a file specific to the "main" file, or
else a primitive that has never before existed. The current logic structure
leads to an unreasonably high number of files labelled as having "uncertified
subfiles", *especially* considering your project to "BFC" all the primitives.
This, in turn, leads to an unnecessarily high overload on the tracker. (For
all we know, there could be a hundred of the "288 have uncertified subfiles"
that are actually ready to be released today, since their "uncertified
subfiles" are primitives that already officially released.)
Please consider revising the logical criteria for "uncertified subfile" to
incorporate this exclusion. If, as I suspect, it turns out we can release even
more files right now (or very soon), this will lead to less overload (i.e., a
more manageable number of files) on the tracker.
Thanks, again.
Franklin
|
|
Message has 1 Reply:
 | | Re: bug report: "cert." list on tracker
|
| Franklin, In your estimatation, how many files are waiting for fixed primitives to be certified? Right now, of the 77 primitives on the system, I count 7 as being fixes. Here's another viewpoint: Any primitive files in the PT system *should* have a (...) (23 years ago, 6-May-02, to lugnet.cad.dev)
|
11 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
