Style info_release page

[mpanik]

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[mpanik]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[chaopeng]

Seeing issues on low resolution.

1. on Mac 1080p (which on my external monitor), see screenshot 1, some texts are overlap
2. on more low resolution, linux 1536*864 (which we use on remote desktop), releasing item texts are overlap and the main div is bigger than page

I thing we need to fix issue 1, issue 2 maybe ok if it is hard to fix

screenshot 1:

screenshot 2:

[mpanik]

@chaopeng I did fix those overlapping labels, this should not be a problem anymore (let me know if is). I have also tried to improve responsiveness for smaller screens, but this is definitely not mobile friendly.