[haiku-development] Re: Haiku git migration status?
- From: Niels Sascha Reedijk <niels.reedijk@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 2 Aug 2011 13:00:53 +0200
Hi,
2011/8/1 Travis Geiselbrecht <geist@xxxxxxxxxx>:
> On Mon, Aug 1, 2011 at 2:31 PM, Oliver Tappe <zooey@xxxxxxxxxxxxxxx> wrote:
>> Hi,
>>
>> On 2011-08-01 at 21:32:04 [+0200], Alexander von Gluck
>> <kallisti5@xxxxxxxxxxx> wrote:
>>> Good afternoon!
>>>
>>> Has there been any further developments in the Haiku svn -> git
>>> migration?
>>
>> Yes, there has been some (albeit slow) progress, as can be seen here:
>>
>> http://dev.haiku-os.org/wiki/GitMigration
>>
>> Last week I finally managed to get the git hook script for commit-mails and
>> -cia-notices into a usable shape.
>>
>> There's some policy decisions we need to make, as those influence git's
>> server config:
>>
>> 1. do we want to allow adding branches to our central repos?
>> 2. do we want to allow deleting and/or rewinding branches?
>> 3. do we want to allow adding unannotated (leightweight) tags?
>>
>> I have currently deactivated all of these actions via the git
>> configuration, so none of these can be done remotely. Please note that all
>> of these actions can still be done explicitly when logged into the vmsvn VM.
>>
>> I think the only of these actions that is of actual interest is being able
>> to add a branch, but since only 'master' and the release branches are being
>> hosted in our central repo, I suppose the need for adding a new branch is
>> rare enough that it is ok to have to log into vmsvn and do it there.
>
> I think it'd make sense to have an auxiliary repository for people to
> put temporary and development branches into. Ideally different
> developers could even create their own entire repository, but I'm sure
> that'd be a lot more work to set up. At various places I've worked
> where git was in use, we usually had a main repo that has release tags
> and official branches and is pretty locked down and then have a
> separate scratch repository for developers to publish various branches
> in progress.
>
> The scratch repos generally get pretty messy pretty fast, but at least
> the average person that just wants to poke at the source doesn't have
> to sort through all of that. They just clone the main one.
I think that outsourcing the 'scratch repository' to Github (still)
has the preference for me. They have great tools for social aspects of
development embedded in their systems.
Regards,
N>
Other related posts:
