Closed Bug 87695 Opened 24 years ago Closed 15 years ago

Check in new order file prior to release

Categories

(Core :: JavaScript Engine, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: rogc, Unassigned)

Details

Before we release 0.9.2 we should check in a new .order file, both for mozilla and netscape. I will attach a new order file to this bug later today or early tomorrow for mozilla; netscape will come later. waterson's going to check in for me because I don't have CVS write access. Also, we should configure --enable-reorder for the official Linux build. -Roger
Adding nsBranch keyword per chofmann.
Keywords: nsBranch
Target Milestone: --- → mozilla0.9.2
All right, we don't need a new mozilla-bin order file right now. The new one I generated isn't any better with the current code that what's already checked in. We will need a new one for the commercial release, though. waterson: should I clear the nsBranch keyword? Thanks! -Roger
Target Milestone: mozilla0.9.2 → ---
clearing nsbranch keyword
Keywords: nsbranch
To Cathleen.
Assignee: rogc → cathleen
Does this very old bug about the 0.9.2 release serve any purpose now? I'll resolve in a few weeks if nobody is opposed.
it could, but the tools in question are broken and have been for ages. i believe bryner recently starting doing similar stuff for mac os x.
Product: Browser → Seamonkey
OK, now, how relevant is "this old bug about the 0.9.2 release" [of Mozilla] about tools which "are broken and have been for ages"?
Assignee: cathleennscp → general
QA Contact: doronr → general
The only .order file I could find in MXR is comm-central/ mozilla/ js/ src/ win32.order
Assignee: general → general
Component: General → JavaScript Engine
Product: SeaMonkey → Core
QA Contact: general → general
Should be enough time by now, could not find .order file either.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.