Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.planning
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Obsoleting NSPRPUB_PRE_4_2_CLIENT_BRANCH
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Kai Engert  
View profile  
 More options Jul 6 2007, 3:43 pm
Newsgroups: mozilla.dev.planning
From: Kai Engert <kengert-nospam-remove182ij28...@redhat.com>
Date: Fri, 06 Jul 2007 21:43:13 +0200
Local: Fri, Jul 6 2007 3:43 pm
Subject: Obsoleting NSPRPUB_PRE_4_2_CLIENT_BRANCH
Print | Individual message | Show original | Report this message | Find messages by this author
After discussing with Wan-Teh Chang, in order to simplify the
maintenance of NSPR, we'd like to obsolete the
NSPRPUB_PRE_4_2_CLIENT_BRANCH.

As of today, NSPR actively uses:
- NSPR_4_6_BRANCH
- HEAD
- NSPRPUB_PRE_4_2_CLIENT_BRANCH

Releases based on NSPR_4_6_BRANCH are used by stable Mozilla branches.

NSPRPUB_PRE_4_2_CLIENT_BRANCH is used by Mozilla trunk.

NSPRPUB_PRE_4_2_CLIENT_BRANCH got introduced at some point in the past
when there was a need to have a separate snapshot for Mozilla.

As of today, HEAD and NSPRPUB_PRE_4_2_CLIENT_BRANCH are mostly in synch.
Whenever checkins are made to HEAD, usually the patch will land on
NSPRPUB_PRE_4_2_CLIENT_BRANCH, too.

We'd like to avoid having to check in NSPR development patches to two
branches.

However, Mozilla trunk should not pull NSPR HEAD directly. Instead, we
propose to produce static tags of NSPR's HEAD as needed and change
NSPR_CO_TAG in mozilla/client.mk to pick up new tags.

(Mozilla on stable branches shall continue to use NSPR releases based on
an NSPR stable branch, not NSPR HEAD.)

Please let us know if you have objections to this proposal.

Thanks,
Kai


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google