Closed Bug 1577 Opened 26 years ago Closed 26 years ago

[PP]Need nspr using the last released branch tag, all platforms.

Categories

(SeaMonkey :: Build Config, defect, P1)

Product:
SeaMonkey
Component:
Build Config
Platform:
Other
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED INVALID

People

(Reporter: leger, Assigned: Chris.Yeh)

Details

Assignee: kipp → cyeh
ok chris - you got a stop ship now, I guess you can check it in :-)
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
checked in. nglayout.mak now pulls mozilla/nsprpub from NSPR_RELEASE_3_0 tag.
Status: RESOLVED → VERIFIED
marking as verified. cc'ing kipp, since he implemented a fix after me.
Status: VERIFIED → REOPENED
Yes, but what about unix? only windows is using the tag...
linux/unix pull/build nspr as a pre-requisite to building xpviewer and viewer. currently, the tag is not enforced, and there is no mechanism for enforcement. since we're only shipping on windows at this point, i think this can stay closed.
Resolution: FIXED → ---
Summary: ss:Need nspr using the last released tag. → Need nspr using the last released tag. (Linux)
Clearing Fixed resolution and taking off ss:. Fixed for Windows, but leaving bug Reopened for Linux fix.
OS: Windows NT → Linux
Hardware: PC → Other
Setting all current Open Critical and Major to M3
Component: Platform: MFC/Win32 on Windows → Build Config
Summary: Need nspr using the last released tag. (Linux) → Need nspr using the last released tag. (Linux)
What's the status on this?
Status: REOPENED → ASSIGNED
Target Milestone: M3 → M4
assigned and changing target fix version to M4. M3 will be built off the tip. M4 will need to go to the static release tag or whatever-agreement-we can-come-to with-nspr-eng
srinivias will be scheduling a meeting w/client engineering manager weenies to discuss development strategies w/regards to nspr.
Summary: Need nspr using the last released tag. (Linux) → Need nspr using the last released branch tag, all platforms.
Target Milestone: M4 → M5
this is too high risk for m4. moving to m5
Summary: Need nspr using the last released branch tag, all platforms. → [PP]Need nspr using the last released branch tag, all platforms.
Target Milestone: M5 → M6
moving to m6
Target Milestone: M6 → M7
moving to m7. we are still on the tip, so we are very current. :) Need to follow up with NSPR about this issue.
Target Milestone: M7 → M8
Status: ASSIGNED → RESOLVED
Closed: 26 years ago → 26 years ago
Resolution: --- → INVALID
we are building on the tip. we will be building on the tip unless told otherwise. closing as invalid. if this changes, will reopen.
Status: RESOLVED → VERIFIED
Ok...marking Verified as Invalid...will reopen if needed.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.