NSS:UsingHG: Difference between revisions

no edit summary
No edit summary
 
Line 9: Line 9:
We should have two separate repositories, one for NSPR, another one for NSS.
We should have two separate repositories, one for NSPR, another one for NSS.


* NSPR at https://hg.mozilla.org/nspr/ which contains mozilla/nsprpub
* NSPR at https://hg.mozilla.org/projects/nspr/ which contains mozilla/nsprpub


* NSS at https://hg.mozilla.org/nss/ which contains:
* NSS at https://hg.mozilla.org/projects/nss/ which contains:
** mozilla/dbm
** mozilla/dbm
** mozilla/security/dbm
** mozilla/security/dbm
Line 69: Line 69:
   <tr>
   <tr>
     <td valign="top">cvs checkout NSS</td>
     <td valign="top">cvs checkout NSS</td>
     <td valign="top">HG:  hg clone https://hg.mozilla.org/nss/ name-for-directory-that-contains-your-local-tree</td>
     <td valign="top">HG:  hg clone https://hg.mozilla.org/projects/nss/ name-for-directory-that-contains-your-local-tree</td>
   </tr>
   </tr>
</table>
</table>
Line 120: Line 120:
I think we would distinguish between lightweight branches for minor releases, and release repositories for each new major version.
I think we would distinguish between lightweight branches for minor releases, and release repositories for each new major version.
This would allow the NSS team to avoid dealing with the term branch most of the time.
This would allow the NSS team to avoid dealing with the term branch most of the time.
In other words, NSS trunk development would happen on https://hg.mozilla.org/nss/
In other words, NSS trunk development would happen on https://hg.mozilla.org/projects/nss/
We would request a release repository (work done by Mozilla rel-eng?) each time we start a new major version, e.g.:
We would request a release repository (work done by Mozilla rel-eng?) each time we start a new major version, e.g.:
* https://hg.mozilla.org/releases/nss-3.13/
* https://hg.mozilla.org/releases/nss-3.13/
Confirmed users
563

edits