I've been thinking it's about time I'll give GIT a try.
So what do I need in order to get the most out of it?
What extension to make my life easier as a .net developer working under VS
IDE?
Lior Friedman
Agile Consultant - AUT/TDD Expert | Mobile:
972.52.833.3660 | Email: lfri...@gmail.com
Blog - http://imistaken.blogspot.com
Ok ill start there.
I also saw a some nice beginner materials on the GIT main site. Any thoughts about them?
On a different matter doesn’t Alt.Net USA give us the urge to have ALT.NET IL 2?
Lior
Last Thursday we had a 4hr overview about a commercial product by the name
of RTI DDS (http://www.rti.com/) which looks like WOW but then... it has its
price which I haven't received yet :-)
The other tool is great as a multi platform engine as it does support
C,C++,C#,Java, Corba, VxWorks,Windows, Linux etc... and work FAST !
Ohad.
I am using retlang for an application we are currently work on in my company. It is a real world application, not in production yet however we had no issues with retlang in the load tests.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "altnetisrael" group.
To post to this group, send email to altnet...@googlegroups.com
To unsubscribe from this group, send email to altnetisrael...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/altnetisrael?hl=en
-~----------~----~----~----~------~----~------~--~---
--
You received this message because you are subscribed to the Google Groups "altnetisrael" group.
To post to this group, send email to altnet...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/altnetisrael?hl=.
--
You received this message because you are subscribed to the Google Groups "altnetisrael" group.
To post to this group, send email to altnet...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/altnetisrael?hl=.
You won’t need to merge.
And then you could stop spending your time on evaluating SCM’s which for most is not that interesting.
(at least not as interesting as adding new functionality to your product)
Lior Friedman
Blog - http://imistaken.blogspot.com
Hi Ariel,
Just to make sure I understand your context,
You MUST branch because you work in a big company that has clients using an older version of your product, refusing to upgrade while still demanding bug fixes on that specific older version they use?
If by any chance you are working in a small company with no paying customers (yet), or with a product who has yet to be release.
Then I think MUST is not really appropriate. In fact I think that AVOID would probably serve you better.
Ken, the following link should be relevant:
And branching is your solution for that?
I think that there are other better ways to be able to release bug fixes within minutes without resorting to branches.
Actually, the reason I don’t like branches is completely different.
For the long version:
http://imistaken.blogspot.com/2008/10/source-branches.html
and http://imistaken.blogspot.com/2009/09/branching-is-evil.html
The short version:
Branching is the easy way out, the longer the branch the higher the risks and the harder it will be to integrate back.
Also working on a single main source line, encourages higher quality standards and higher quality (as I think you already heard me saying) is the best/only way to become more productive.
The added bonus of choosing not to branch is that you then don’t have a merge problem (ever).
BTW, I don’t have a stand about SCM’s in some contexts (e.g. a single programmer working with the SCM server just under his feet) SVN does a great job, and GIT from what I’ve seen is an excellent system as well.
Divide and Conquer,
I would try, splitting it the work one window at a time,
after each window is “Done”
and by “Done” I mean at least: implemented, tested and explored.
I would commit it into the mainline.
And yes the trick, is how to split the UI into meaningful windows which are mostly independent and can be added into the product without making the entire application useless.
BTW what’s the purpose of the entire rewrite?
Is it a cosmetic change aiming to make things just look better? A logical change aimed at improving the user experience? Or just a general cleanup aimed to make the internal code structure better?
The tactic for splitting the work will probably differ depending on the context.
Lior
On the same single window at the same time?
Why are they doing so?
But how about putting them on the same machine?
I’m dead serious. This practice even have a big name: Pair Programming, and deserves it own discussion.
More to the point how exactly branching will help this cause? I must be missing something, I thought branching is used in order to avoid the need to share your changes until they are done.
I think the scenario you referring to is covered by basic usage of SCM. And really does not warrant a full pledged branch.
That being said, to some extend each time you work on a local copy it can be viewed as a “branch”.
Obviously this is not the kind of branching which is in question here.
From: Dotan N.
[mailto:dip...@gmail.com]
Sent: Monday, November 16, 2009 12:47 PM
To: altnet...@googlegroups.com
Subject: Re: Using GIT
what if two developers must work on that...

--
I really think that most likely they should pair.
Also I kind of suspect that I would try to avoid such a scenario in the first place,
or make it so short as not to include usage of the SCM at all.
But if you are working on a big feature that you can’t break to independent tasks, and you have more the one person working on that.
You are not at a very good place to begin with are you?
From: Dotan N.
[mailto:dip...@gmail.com]
Sent: Monday, November 16, 2009 4:43 PM
To: altnet...@googlegroups.com
Subject: Re: Using GIT
on the same feature. interdependent too.
I really think that most likely they should pair.
Also I kind of suspect that I would try to avoid such a scenario in the first place,
or make it so short as not to include usage of the SCM at all.
But if you are working on a big feature that you can’t break to independent tasks, and you have more the one person working on that.
You are not at a very good place to begin with are you?
From: Dotan N. [mailto:dip...@gmail.com]
Sent: Monday, November 16, 2009 4:43 PM
on the same feature. interdependent too.
they have to commit to somewhere common which is not head
--
Yes, reality does tend to interfere ;)
And I don’t have clear cut answer for this situation.
I just know that for every problem there is more than a single solution , and that Branching is usually
very low on that list.
Lior
From: Dotan N.
[mailto:dip...@gmail.com]
Sent: Monday, November 16, 2009 7:36 PM
To: altnet...@googlegroups.com
Subject: Re: Using GIT
On Mon, Nov 16, 2009 at 5:37 PM, Lior Friedman <lfri...@gmail.com> wrote:
--
You received this message because you are subscribed to the Google Groups "altnetisrael" group.
To post to this group, send email to altnet...@googlegroups.com.
To unsubscribe from this group, send email to altnetisrael...@googlegroups.com.