The version control system of Mozilla community

The current version control system for Mozilla codebase is CVS. But it can't fulfill the development of the Mozilla community. In the Firefox summit this year, there is a session on this topic. Lots of VCSes are brought into consideration. At last, only two of them are survived -- Mercurial and Bazaar. Here is the detail. It's glad to see that Sun's VCS investigation also gives some help:-)

So what's the requirement of the new VCS?

It can provide the following access control:
\* restrict people to specific areas;
\* restrict areas/branches to specific people;
\* group membership;
\* being able to query where people have access;
\* audited ACL changes;
\* versioned ACLs.

It can also work well with the following tools integration: blame(like current bonsai); revision history; source browsing; source indexing; tree closure/override; reports/metrics; commits, committers, etc.

It should have some more features. Check out this link to get more information.

Performance issue is also an important factor for the choice. Here is the investigation from Johnny.

No matter which VCS is finally chosen, it's a new start for Mozilla2.

Comments:

Post a Comment:
Comments are closed for this entry.
Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today