Migrate to Mercurial

[Darwin Bautista]

Hi guys,

Do you think we can migrate to Mercurial any time soon? If you look at
the whole Halalan SVN repository, you'll notice that it already has
lots of tags. Thus, a checkout of the whole repo takes a lot of time
and space. Also, Mercurial, like most DVCS, has lots of goodies that
SVN currently does not, and will never have. Google Code already has
good support for Mercurial and migrating to it from Subversion is
quite easy.

What do you think?

[Waldemar Bautista]

+1 from me. I think the project can benefit with this change.

--
Waldemar Amado Bautista

[Darwin Bautista]

Hi,

I already went ahead and tried converting Halalan's SVN repo to Mercurial.
That said, I've temporarily switched Halalan's VCS to Mercurial for
testing (the SVN repo is still intact and can be accessed normally).
The repo was split into three separate repos--one for the code, one
for the documentation, and another for the wiki.

Code: https://halalan.googlecode.com/hg/
Wiki: https://wiki.halalan.googlecode.com/hg/
Docs: https://docs.halalan.googlecode.com/hg/

Notes:
* The docs repository contains what was in branches/documentation
* SVN trunk is now the 'default' branch in the code repo.
* branches/* are now "named branches" and are also stored in the code repo
* The active branches are: default, 1.x.x, halalanup
* The closed branches are: halalanupd, halalanesc, bananafish
* tags/* are also "stored" in the code repo
* --datesort was used in the conversion process to preserve the changelogs

Please test and check if the converted repos are okay.
Also, suggestions for a better conversion scheme is welcome.

Thanks,
Darwin

[Waldemar Bautista]

On Sat, Sep 4, 2010 at 11:09 PM, Darwin Bautista <dar...@gmail.com> wrote:
> I already went ahead and tried converting Halalan's SVN repo to Mercurial.
> That said, I've temporarily switched Halalan's VCS to Mercurial for
> testing (the SVN repo is still intact and can be accessed normally).
> The repo was split into three separate repos--one for the code, one
> for the documentation, and another for the wiki.
>
> Code: https://halalan.googlecode.com/hg/
> Wiki: https://wiki.halalan.googlecode.com/hg/
> Docs: https://docs.halalan.googlecode.com/hg/

I think this is okay.

> Notes:
> * The docs repository contains what was in branches/documentation
> * SVN trunk is now the 'default' branch in the code repo.

Can you make 1.x.x the default branch? Let's create another branch
for version 2 after CI 2.0 is released.

> * branches/* are now "named branches" and are also stored in the code repo
> * The active branches are: default, 1.x.x, halalanup

Let's make the active branches default and halalanup for now.

> * The closed branches are: halalanupd, halalanesc, bananafish

We can remove bananafish since that project didn't took off.

--
Waldemar Amado Bautista

[Darwin Bautista]

On Sat, Sep 4, 2010 at 11:55 PM, Waldemar Bautista
<waldemar...@gmail.com> wrote:
> On Sat, Sep 4, 2010 at 11:09 PM, Darwin Bautista <dar...@gmail.com> wrote:
>> I already went ahead and tried converting Halalan's SVN repo to Mercurial.
>> That said, I've temporarily switched Halalan's VCS to Mercurial for
>> testing (the SVN repo is still intact and can be accessed normally).
>> The repo was split into three separate repos--one for the code, one
>> for the documentation, and another for the wiki.
>>
>> Code: https://halalan.googlecode.com/hg/
>> Wiki: https://wiki.halalan.googlecode.com/hg/
>> Docs: https://docs.halalan.googlecode.com/hg/
>
> I think this is okay.
>
>> Notes:
>> * The docs repository contains what was in branches/documentation
>> * SVN trunk is now the 'default' branch in the code repo.
>
> Can you make 1.x.x the default branch?  Let's create another branch
> for version 2 after CI 2.0 is released.

What should I do with SVN trunk? Should I just exclude it from the
conversion process?

>> * branches/* are now "named branches" and are also stored in the code repo
>> * The active branches are: default, 1.x.x, halalanup
>
> Let's make the active branches default and halalanup for now.
>
>> * The closed branches are: halalanupd, halalanesc, bananafish
>
> We can remove bananafish since that project didn't took off.

Okay, I'll remove bananafish.

[Waldemar Bautista]

On Sun, Sep 5, 2010 at 12:09 AM, Darwin Bautista <dar...@gmail.com> wrote:
> What should I do with SVN trunk? Should I just exclude it from the
> conversion process?

I think so. There's no meaningful code in trunk, anyway.

--
Waldemar Amado Bautista

[Darwin Bautista]

Okay. I've already pushed the converted repo with the requested changes.