Reference to Ruby on Rails in Tutorial 2 is unclear

[Sid R]

This is a minor nitpick, but I found the little blurb about the way Ruby on Rails does migrations a little confusing.

The section in question is ​https://docs.djangoproject.com/en/6.0/intro/tutorial02/#creating-models and the text in question is:

This includes the migrations - unlike in Ruby On Rails, for example, migrations are entirely derived from your models file, and are essentially a history that Django can roll through to update your database schema to match your current models."

The 'unlike in Ruby on Rails' is not descriptive enough for a person not knowledgeable in Ruby on Rails to understand what the difference is, or why it might matter.

I now wonder if it's simply unimportant, and not necessary to have in the documentation - i.e. just remove 'unlike in Ruby on Rails, for example', and it's just as useful/helpful?

[Vidhi Singh]

I would like to work on this.

[Sushmita Yadav]

Hi, I would like to work on this issue. Is it available?

[Tim Graham]

The text dates to the introduction of migrations in 2013: 0b3c8fc85168bac7327e7c4372e92b52575547e9. I agree the mention could be removed, or the differing behavior of Ruby on Rails clearly stated.

[Vinay Datta]

Hi, I’ve implemented a fix for this issue and opened a PR:

​https://github.com/django/django/pull/20974#issue-4122932021

The change ensures that when Feed.link is missing, an ImproperlyConfigured exception is raised instead of an AttributeError, with handling for both attribute and callable cases.

Please let me know if any changes are needed.

[GitHub <noreply@…>]

In f3bdfd2:

Fixed #36999 -- Removed mention of Ruby on Rails from tutorial part 2.

This comparison wasn't fleshed out, so it was distracting.

[Jacob Walls <jacobtylerwalls@…>]

In b8cb57fe:

[6.0.x] Fixed #36999 -- Removed mention of Ruby on Rails from tutorial part 2.

This comparison wasn't fleshed out, so it was distracting.
Backport of f3bdfd2065373272ebb637785cea2313582a8b8c from main.