RSpec at github 8
After a few months of exploring git and hosting RSpec’s git repository at github, we’re happy to announce that github is now RSpec’s official home for Source Code Management.
Tracking will continue to live at the lighthouse.
We will continue to release gems to http://rubyforge.org/projects/rspec, but we will no longer be committing changes to the subversion repository there. For Rails users who are using the rspec plugins for Rails, edge rails now supports git-hosted plugins.
We’ve broken the project up into four separate repositories:
- rspec for the rspec gem/plugin
- rspec-rails for the rspec-rails gem/plugin (formerly rspec_on_rails)
- rspec-tmbundle for the TextMate bundle
- rspec-dev for developers/contributors
See the wikis for each repository for more information about building, installing and contributing to the project.
Great to hear! I have been watching for Rspec on Github and just recently moved my rspec plugins over to git submodules.
I love Github! Every time I watch a new repository I think of Meet the Parents – “I’m watching you Focker” (points two fingers at eyes).
Unfortunately, the git-submodule command (needed for rspec-dev, as per http://github.com/dchelimsky/rspec-dev/wikis/contributingpatches) seems to be missing in git version 1.5.2.5 (Ubuntu 7.10). Oh well, Ubuntu 8.4 will be released in a couple of weeks… perhaps it’s time for me to upgrade to the beta.
I don’t think that I’ll be able to refrain from comments about trendy git-hype, or unfavorable feature/usability comparisons to bzr or darcs… but hey, for a vibrant open source project any DVCS is better than no DVCS! ;-)
@nicholas: try to build git yourself. it’s really damn easy :), you just need some basic dev tools installed.
@david: just added rspec as submodule to my rails projects and wanted to tie it to the latest stable release. but there isn’t any tag in your github repo :((. could you at least add one for the last rspec release? would be nice.
thanks.
ah @david: perhaps you just missed to run `git push—tags` to push the tags to the remote repo. that doesn’t happen by a plain push.
@thomas: Unfortunately, that tag was back when there was a single repository. I could tag the repos, but you’d end up with vendor/plugins/rspec/rspec and vendor/plugins/rspec/rspec_on_rails.
If you want that release, you’re going to have to continue to use subversion at rubyforge until we do the 1.1.4 release.
@nicholas – we bailed on submodules so you should be OK now
I have wanted one of these forever! THANKS for the great work
@david: and just after I’ve upgraded too. ;)