[Lemon-devel] 100 commits in HG - some experiments

[Alpár Jüttner]

Hi,

Now we have over 100 commits in HG, thus I think its time to summarize
the experiments.

I can say, generally it works very well. It makes the concurrent
development much easier, and also provides much better control over the
development.

The only is difficulty is when a modification is needed on a changeset.
Currently developers typically push their changes on their public
repository. Unfortunately hg currently does not support changeset
removals, so, if you want to withdraw a changeset and change it to
another one then you must 
      * ssh to the server 
      * clone your current repository in a way that contains everything
        but the wrong commit. (it can be difficult if you have several
        heads)
      * move the config file from the old repo to the new one. 
      * remove the old repo 
      * rename the new repo to the original name,
which is very tedious. If someone has already pulled your repo, then
(s)he should alse recreate the local clone of your repo.

The other problem is that it is hard to refer to the tentative
changesets from the trac tickets.

Fortunately, there is a more convenient solution: sending the
changegroup files created by 'hg bound' (or by 'hg export') instead.
They could be sent to the lemon-devel mailing list, but I suggest using
the trac ticket system for this purpose as well, as it provides a way to
see the status of the changesets.

Thus, if you want to contribute to lemon, you should create a
changegroup file of your changes against the latest main branch, then
create a new 'defect' or 'enhancement' ticket in the trac system (here:
http://lemon.cs.elte.hu/trac ), where you can describe the purpose of
your changes and you can also attach the changegroup file. Then others
can comment it, can request some modifications, or even can add new
commits to it before it goes into the main branch.

Let's try this approach and see how it works!

Regards,
Alpar