Bug 1899998 - Modular GNOME Keyring services
Summary: Modular GNOME Keyring services
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Daiki Ueno
QA Contact:
Depends On:
Blocks: F37Changes
TreeView+ depends on / blocked
Reported: 2020-11-20 15:01 UTC by Ben Cotton
Modified: 2022-02-10 16:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Type: ---

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gcr merge_requests 67 0 None None None 2021-02-17 15:40:22 UTC

Description Ben Cotton 2020-11-20 15:01:50 UTC
This is a tracking bug for Change: Modular GNOME Keyring services
For more details, see: https://fedoraproject.org/wiki/Changes/ModularGnomeKeyring

The monolithic daemon provided by GNOME Keyring will be split into dedicated sub-daemons, so that they can be consistently managed by systemd.

Comment 1 Ben Cotton 2021-02-10 21:58:00 UTC
We have reached the 'Code Complete (testable)' milestone in the Fedora 34 release cycle. If your Change is in a testable state, please set the status to MODIFIED. If this Change will not be ready for Fedora 34, please set the version to rawhide.

The 100% code complete deadline is Tue 2021-02-23.

Comment 2 Ben Cotton 2021-02-16 15:52:00 UTC
Reminder: The change complete (100% complete) deadline for Fedora 34 changes is Tuesday 23 February. At that point, changes should be 100% code complete, along with supporting documentation where appropriate. Please indicate this by setting the tracker bug for your change to ON_QA.

Comment 3 Daiki Ueno 2021-02-17 15:23:05 UTC
I'm afraid this change most likely will not be complete by the Fedora 34 deadline. Although the relevant changes are likely to be included as part of the GNOME 40 update, the actual enablement of the feature (e.g., systemd preset, default user configuration such as envvars) would need more discussion among other DEs. Can we retarget it to Fedora 35?

The upstream discussion is ongoing at: https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/67

Comment 4 Ben Cotton 2021-02-17 15:40:23 UTC
(In reply to Daiki Ueno from comment #3)
>  Can we retarget it to Fedora 35?

Will do! I'll update the trackers. You don't need to re-submit the proposal.

Comment 5 Ben Cotton 2021-08-10 12:32:47 UTC
Today is the "Code complete (testable)" deadline in the Fedora Linux 35 release schedule:

If this Change is complete enough to be tested, please indicate this by setting this bug to the MODIFIED status. (If it is 100% complete, you can set it to ON_QA).

If you wish to defer this Change to Fedora Linux 36, please needinfo bcotton@redhat.com.

Comment 6 Daiki Ueno 2021-08-10 12:39:21 UTC
Sorry, I haven't had time to move this forward in this cycle as well; could you defer it to Fedora Linux 36?

Comment 7 Ben Cotton 2021-08-10 17:05:01 UTC

Comment 8 Ben Cotton 2022-02-08 21:07:58 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 36 development cycle.
Changing version to 36.

Comment 9 Ben Cotton 2022-02-08 21:15:06 UTC
Today we reached the Code Complete (testable) milestone in the F36 schedule: https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html

All code for this change should be complete enough for testing. You can indicate this by setting the bug status to MODIFIED. (If the code is fully complete, you can go ahead and set it to ON_QA.)

If you need to defer this Change to F37, please needinfo bcotton.

Comment 10 Daiki Ueno 2022-02-10 15:59:30 UTC
Sorry, we have to defer this to the next release again. Could you move it?

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