pmake .ORDER bug with -j 1 or misuse?

[Garrett Cooper]

Hi hackers,
    I'm getting used to pmake after using GNU make for the past couple
years, and I'm used to `in-order prerequisites', where if I specified
a list of targets a specific way, then it would execute the targets
serially in-order.
    I tried to do the following with .ORDER, but it doesn't appear to
be working as I expect it to:

[gcooper at optimus /scratch]$ make
do
something
[gcooper at optimus /scratch]$ cat BSDmakefile
.ORDER: something do

all: do something

do something:
        @echo ${.TARGET}
[gcooper at optimus /scratch]$ make -j 2
something
do

    It does function as I expect it to via -j 2 (executes the
`something', then `do' goals), but not with -j 1 -- could someone help
me understand what behavior is correct so I can adjust my behavior
and/or get a fix started?
Thanks!
-Garrett