Embrace.
We are moving the Roslyn code to GitHub
21–30 of 225 posts
Re: We are moving the Roslyn code to GitHub
#22Earlier quoted context omitted.
There's plenty of competition, from Bitbucket, which is better. "Social" effects notwithstanding, of course.
What's better about Bitbucket? I've never used it, just wondering.
Free private repositories and out-of-the-box mercurial support. Works well for those small side projects which you do not (yet) want to maintain. I have lots of stuff in there which i want to keep as reference for projects to come and would never want to release to the public.
Re: We are moving the Roslyn code to GitHub
#23One of the GitHub founders has talked about being offered a job at Microsoft out of college, and deciding to take the risk starting GitHub instead. Must feel satisfying.... Edit: Ok, not straight out of college. No less satisfying though.
Not exactly straight out of college:
"I was still working full time at Powerset on July 1, 2008 when we learned that Powerset had just been acquired by Microsoft for around $100 million. This was interesting timing. With the acquisition, I was going to be faced with a choice sooner than I had anticipated. I could either sign on as a Microsoft employee or quit and go GitHub full time. At 29 years old..."
http://tom.preston-werner.com/2008/10/18/how-i-turned-down-3...
Re: We are moving the Roslyn code to GitHub
#24Earlier quoted context omitted.
There's plenty of competition, from Bitbucket, which is better. "Social" effects notwithstanding, of course.
I like Bitbucket and have been using them for some time but their interface is slow and not as intuitive as Github's.
Also like Bitbucket, and agree with the interface. They made things responsive a while ago, and there were lots of complaints about the 'create a README' decision as a space-waster, they haven't done anything about it since.
I like their revenue model, but because of the existence of JIRA and Stash, Atlassian are refusing/reluctant to improve the issue tracker in Bitbucket. For example, I can't manage releases, create epic(?) issues, and a few other things.
That's all well, but the problem's that getting a JIRA license gives you the ability to manage your issues at a more granular level, until you realise that you also need Stash to create epic(?) issues. I got into JIRA for a few months, and was disappointed by it. I've been considering moving some of my private repos to GitHub.
Re: We are moving the Roslyn code to GitHub
#25Earlier quoted context omitted.
There's plenty of competition, from Bitbucket, which is better. "Social" effects notwithstanding, of course.
What's better about Bitbucket? I've never used it, just wondering.
If you're working in a team the code review workflow is a bit better, because as a reviewer you can explicitly Approve a pull request. I've used it in a team where the requirement was to get two approvals before a pull request can be shipped. Having the number of approvals visible on the pull request list/overview screen is a tiny detail, but very useful.
At my current job we're using a "ship it" label on GitHub to track this, I really don't understand why GitHub still cannot track this in a native way.
Re: We are moving the Roslyn code to GitHub
#26Earlier quoted context omitted.
I like Bitbucket and have been using them for some time but their interface is slow and not as intuitive as Github's.
Also like Bitbucket, and agree with the interface. They made things responsive a while ago, and there were lots of complaints about the 'create a README' decision as a space-waster, they haven't done anything about it since. I like their revenue model, but because of the existence of JIRA and Stash, Atlassian are refusing/reluctant to improve the issue tracker in Bitbucket. For example, I can't manage releases, creat…
We use jira at work, and there are definitely epics available...?
Re: We are moving the Roslyn code to GitHub
#27> HOW: This will be a simple switch – turn off CodePlex, turn on GitHub. You’ll be able to see our check-ins on GitHub that same day. It's probably a safe bet that CodePlex's days are numbered. Which is kind of a shame. It was definitely heavily lacking but I can't help but think that some more competition in the space would be a good thing.
There's plenty of competition, from Bitbucket, which is better. "Social" effects notwithstanding, of course.
My only complaint about bitbucket is that I want to see the code easily, not click through heaps of buttons to do that.
Re: We are moving the Roslyn code to GitHub
#28Earlier quoted context omitted.
Also like Bitbucket, and agree with the interface. They made things responsive a while ago, and there were lots of complaints about the 'create a README' decision as a space-waster, they haven't done anything about it since. I like their revenue model, but because of the existence of JIRA and Stash, Atlassian are refusing/reluctant to improve the issue tracker in Bitbucket. For example, I can't manage releases, creat…
We use jira at work, and there are definitely epics available...?
Interesting, I was on 6.0-6.1, and unless I'm completely wrong, I went a month seeing an 'activate Stash to use this feature' button/link. If you've had epics before then, then I was probably doing something wrong.
Re: We are moving the Roslyn code to GitHub
#29Earlier quoted context omitted.
Also like Bitbucket, and agree with the interface. They made things responsive a while ago, and there were lots of complaints about the 'create a README' decision as a space-waster, they haven't done anything about it since. I like their revenue model, but because of the existence of JIRA and Stash, Atlassian are refusing/reluctant to improve the issue tracker in Bitbucket. For example, I can't manage releases, creat…
We use jira at work, and there are definitely epics available...?
His point is that because of Jira, Bitbucket can't have epics. Cannibalizing sales.
Re: We are moving the Roslyn code to GitHub
#30Earlier quoted context omitted.
I like Bitbucket and have been using them for some time but their interface is slow and not as intuitive as Github's.
Also like Bitbucket, and agree with the interface. They made things responsive a while ago, and there were lots of complaints about the 'create a README' decision as a space-waster, they haven't done anything about it since. I like their revenue model, but because of the existence of JIRA and Stash, Atlassian are refusing/reluctant to improve the issue tracker in Bitbucket. For example, I can't manage releases, creat…
Bitbucket has issue with cross-referencing. You can reference an issue from an issue but to make a two-way reference you need to edit both. This is a showstopper for projects that use tracker for planning too, not just for logging bugs.