Bug 1867219 - Ruby on Rails 6.0
Summary: Ruby on Rails 6.0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Valena
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F33Changes
TreeView+ depends on / blocked
 
Reported: 2020-08-07 18:08 UTC by Ben Cotton
Modified: 2020-11-30 03:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-30 03:37:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ben Cotton 2020-08-07 18:08:15 UTC
This is a tracking bug for Change: Ruby on Rails 6.0
For more details, see: https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_6.0

Ruby on Rails 6.0 is the latest version of well known web framework written in Ruby.

Comment 1 Ben Cotton 2020-08-12 14:27:45 UTC
Branching F33 Change Tracker bugs.

Yesterday was the code complete (testable) deadline. All bugs should be at least in MODIFIED state by now to indicate they are testable.

Comment 2 Pavel Valena 2020-08-13 08:38:04 UTC
(In reply to Ben Cotton from comment #1)
> Branching F33 Change Tracker bugs.
> 
> Yesterday was the code complete (testable) deadline. All bugs should be at
> least in MODIFIED state by now to indicate they are testable.

Yes, sorry, I forgot about branching :( It's currently pending in Bodhi, built in side-tag:

https://bodhi.fedoraproject.org/updates/FEDORA-2020-5bc381f3f0

Comment 3 Ben Cotton 2020-08-27 01:11:56 UTC
Yesterday we reached the Code complete (100% code complete) deadline for Fedora 33 Changes. If your Change is complete, please set this tracking bug to ON_QA. If you need to defer this Change to Fedora 34, please let NEEDINFO me.

As a reminder, we are now in the Beta Freeze. If you need to land package updates, please propose it as a Freeze Exception at https://qa.fedoraproject.org/blockerbugs/propose_bug


Note You need to log in before you can comment on or make changes to this bug.