[Kde-scm-interest] Project release tags on Gitorious

[Ian Monroe]

2009/11/29 Chani <chanika at gmail.com>:
> On November 29, 2009 14:38:50 Eike Hein wrote:
>> On 11/29/2009 11:22 PM, Albert Astals Cid wrote:
>> >> So I don't really see why testing the waters should be
>> >> exclusive to Amarok.
>> >
>> > Because that is what was decided.
>>
>> I'm not really sure what to make of this, tbh. It's in stark
>> contrast to the general "you should get going with git, too!"
>> vibe on IRC and the blogs promoted by the Amarokers. They
>> seem to be really happy they made the switch, and we at Konvi
>> don't see any additional needs we have over Amarok.
>
> the idea was to minimize the transition period: right now, if you move to git
> then anyone who wants to contribute to it has to know git, and the techbase
> documentation isn't where I'd like it to be at.
>
> main modules of KDE *will* stay in svn until we can provide a smooth
> transition for them.
>
> projects that are on the fringe... well, in the end we can't force you to
> stay, but please *please* consider all the consequences of a premature move to
> git.
>
> important technical consequences:
> -you won't have a log of who pushed what until whenever that TODO item gets
> done. sure, this isn't *likely* to be important... but you're not likely to
> need your backups, either, are you? :)
> -you won't be part of commit-filter, you won't be able to use BUG: or CCMAIL:
> or any of those hooks until they're done.
> -if you've got a docbook folder, remember to separate it out and leave it
> somewhere in svn for the translators.
>
> there are also social consequences - I think it'll create more pressure to
> move to git before it's ready, and there'll be less pressure to actually
> resolve that todolist. it also feels less "KDE" right now - we don't have a
> kde page on gitorious or anything... or am I putting the cart before the horse
> on that one? :)
>
>
> so... if you think the move is worth it in spite of that, I won't try to stop
> you. however, I really think it would be better for all of us if you put
> pressure on (or volunteered to help with) fixing the technical issues *first*.
>
> all I ask is that you consider all the consequences before making a decision.

Yea I mostly agree. Phonon might move early, but it was actually on
the list of things to move to Git with Amarok since Nokia is really
bad at SVN. Amarok moving early itself put some pressure to solve the
scripty issue and getting some of the filters worked out now. But I
don't see much benefit to other extragear projects moving to Git,
seems like mostly a distraction.

Ian