Rails 2.1 and svn externals

Hey folks--

Does anyone know when the rails 2.1 stuff will appear in the SVN repo
for folks mapping Rails as externals?

The latest I can find tagged is:
http://svn.rubyonrails.org/rails/tags/rel_2-0-2/

I know edge has moved to git, but my understanding was that releases
would still update the svn repo.

   Cheers,
   Jake

Jake, I've found that it really doesn't make sense to map Rails as an external.

Much better to just add it to your repo. This ensures you always have
access to the code, if for some reason the Rails SVN goes down.

Not sure how frequent it happens these days, but I ran into major
problems with deployments because of that issue about a year ago.

I've switched to downloading the tar file from the git repo, then
adding that to my SVN project.

Same goes for gems / plugins.

I've switched to downloading the tar file from the git repo, then
adding that to my SVN project.

Same goes for gems / plugins.

...I'll add one exception. If you're developing the said gem/plugin it
does make sense to use externals :wink:

Subimage Interactive wrote:

Jake, I've found that it really doesn't make sense to map Rails as an
external.

Much better to just add it to your repo. This ensures you always have
access to the code, if for some reason the Rails SVN goes down.

Yeah, this was, of course, another option. I was just wondering why
they haven't updated the SVN repo with the latest rev.

I believe they've shunned SVN in favor of git. I'm guessing the
release support on SVN will be spotty at best.

Because svn isn't being used for development anymore.
svn.rubyonrails.org has been kept up and running to not mess with
people's externals and so on but it's never ever going to change again
(at least that was my understanding of the announcement made when the
switch happened.

fred

Frederick Cheung wrote:

Frederick Cheung wrote:

...but it's never ever going to change again
(at least that was my understanding of the announcement made when the
switch happened.

fred

It would seem so. I guess I misunderstood. I thought the svn repo
would be updated with release revs, but not used for development.

You could always setup your own SVN repository, download the release git tarballs, and svn-external to your local copy...