add changelog link to rubygem linkset

[farukaydin]

Related with #728, #324

cc: @sferik @qrush

[qrush]

Nice. I'd love for us to parse this out of the gemspec too.

[arthurnn]

Is this on part of the gemspec? cc @drbrain
I am ok with us moving forward with this and do the parse in a next PR.
@dwradcliffe @qrush @sferik if you are all good with this change, I can take care of merging it, and deploying it and run the migration.

[arthurnn]

@olivierlacan thoughts?

[olivierlacan]

@arthurnn I'm pretty sure we have a nice PR idea (it might even already be on master) where everything was moved to the serialized column instead of adding discrete columns for these new (and valuable) pieces of metadata. I'd be interested in going that way rather than adding yet another column because it seems unlikely we would query by it.

[kbrock]

I too want this in the serialized metadata column.
I really want changelog links in, but would prefer to go the route of #724

Also, I promise to fix #728 once #724 merges.

[olivierlacan]

While testing #1104 (comment) I noticed that linksets SELECTs were consistently the worse performing queries from the rubygem GET endpoint. I'd really like to help @kbrock with that serialized metadata idea, I feel like that would improve the performance of the API endpoint by about a third on the SQL-side alone.

[arthurnn]

I will be closing this, as I think we should have this data as serialized metadata. We already have the metadata been populated from the gemspec,

rubygems.org/app/models/version.rb

Line 186 in 71e4b50

metadata: spec.metadata || {},

Thanks for the PR.

[olivierlacan]

:thumbs_up: