[Tinyos-devel] [nescc-devel] nesC 1.3.0 beta3

[Razvan Musaloiu-E.]

Hi!

On Tue, 24 Jun 2008, Philip Levis wrote:

>
> On Jun 24, 2008, at 7:44 PM, Razvan Musaloiu-E. wrote:
>
>>> It also makes branching a little easier. Git has these benefits, plus
>>> the ability to maintain a local repository.
>> 
>> I consider this a very useful feature but I know that Phil doesn't. :-(
>
> I think the local repository is kind of neat. But basically, I'm wary of 
> going back to someone periodically losing four hours debugging because 
> someone accidentally checked in a change to the AM group.

That's why I like GIT. There you have better control on what to accept and 
what not. You will include in you tree something if either you check it 
yourself or was already checked by somebody you trust. Bad code can still 
sneak in but it will be much harder.

> My experience is that the time managing branches in CVS is a little tricky is 
> when the branched-from code progresses independently. In TinyOS, development 
> tends to be such that a given file has very few people who modify it. So 
> branching out, then merging it back in is not a big deal, as long as you are 
> careful to tag when you branch.
>
>>> 
>> How about moving the tinyos-2.x to SVN and keeping the tinyos-2-contrib in 
>> CVS?
>> 
>
> When we set up contrib, it seemed really important to have contrib in the 
> same repository as TinyOS itself, to increase its visibility.
>
>> Another thing that makes SF very annoying is the fact that is very-very 
>> slow from time to time. Sometime in the most inappropriate moments. :|
>
> Fair enough -- but I'm not sure that it's worse than any other provider in 
> this regard.

How about code.google.com? :-) Their issue tracker might be even a good 
way to keep track of some bugs.

> And not having to worry about physical machines, the integrity of data, 
> or the longevity of the site, is a big relief.

It's not really a significant issue that here is what Sourceforge says 
about backups:

 	Backups: Project's are responsible for backing-up their CVS
 	repository. Projects may retrieve a copy of their repository via
 	rsync to regularly create an offsite backup.

 	http://alexandria.wiki.sourceforge.net/CVS+-+Version+Control+for+Source+Code

--
Razvan ME