Mark Banner wrote:
[follow-ups set to mozilla.dev.tech.ldap]
As most people will know, the majority of Mozilla development has moved
over to using Mercurial (aka hg) [1]. This includes the Thunderbird and
SeaMonkey repositories (comm-central [2] and mozilla-central).
One of the minor issues left is that we are still pulling the LDAP c-sdk
from a static tag in CVS into the Thunderbird & SeaMonkey builds that we
do.
We'd like to move the source that we use in our builds from CVS to
Mercurial. For Thunderbird this would mean that we can drop the use of
CVS completely, for SeaMonkey, we wouldn't quite be able to, but we'd be
nearly there. This would also simplify our release processes and the
source control systems a user has to interact with.
There are several ways we can do this mainly depending on what the LDAP
SDK developers wish to do:
a) Move LDAP SDK development to Mercurial. Most of the implications for
this should be obvious. The directory/ code in cvs could be moved to its
own repository on hg.mozilla.org. Development would then continue in
hg.mozilla.org. Tagging and branching would be available if required.
There is also access control available should it be required.
The slight downside of this for comm-central is that comm-central would
have to decide what to do with its current directory/xpcom files as they
would want to exist in the same directory as the SDK files. We could
either add a sub-directory for the SDK or move the directory/xpcom back
alongside the SDK code.
b) Keep LDAP SDK development in CVS, snapshot LDAP SDK to Mercurial.
This would mean status-quo for the LDAP SDK developers.
For comm-central I would recommend going for the importing the source of
a specific tagged version directly into comm-central (as opposed to
creating a separate repository). The main reason for this is that
typically we only update the c-sdk a few times a year - therefore it
won't add much noise to the comm-central changesets.
This isn't urgent, but I would like to get agreement on the way forward
in the next few of weeks so that we know in which direction we are heading.
Moving to Mercurial is fine with me. I've been using git now for quite
some time and have really grown to like how much better it is than CVS.
I understand hg is similar to git. As far as the repo layout, it
doesn't matter to me if the c-sdk has its own top level repo or is part
of a larger repo, as long as it is easy to
1) checkout just the c-sdk
2) build just the c-sdk
3) tag individual and separate c-sdk releases
4) produce individual source code releases of the c-sdk
Standard8
[1] https://developer.mozilla.org/en/Mercurial
[2] https://developer.mozilla.org/en/comm-central
_______________________________________________
dev-tech-ldap mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-ldap
