Contrib.social

Use only version field in change records, remove branch field

Open on Drupal.org →
Created on 13 June 2024, 16 days ago
Updated 26 June 2024, 2 days ago

Problem/Motivation

'
Core may now have change records records that will be for 10.4.z and 11.1.z but not 11.0.z. The current two fields of branch and version do not handle this well.

If we put 10.4 in the version field as the lowest version a change is in, there's no indication that the change isn't in 11.0.

Steps to reproduce

Proposed resolution

Hide the branch field.
Make the version field multi-valued and change the version field description to "Enter the versions this change was first applied in."
If the field can't be multi-valued then change the version field description to "Enter the versions this change was first applied in. Example, "10.4.0, 11.1.0"

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Version

3.0

Component

User interface

Created by

🇳🇿New Zealand quietone New Zealand

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @quietone
  • Comment 16 days ago →
    🇳🇿New Zealand quietone New Zealand

    As I wrote this I was thinking it would be nice to have a new field, 'not in version', to allow entry of the version where the change was not introduced. The field does not have to be multi-valued and it should only display when there is data in it. In the example from the issue summary we would display something like

    version: '10.4.0, 11.1.0'
not in version: '11.0.0'
  • Comment 2 days ago →
    🇺🇸United States drumm NY, US

    I see no reason why “Introduced in version” can’t be multi-valued. We’ll need to update the Views showing both fields regardless, which should be straightforward.

    We should hold off on adding new fields until after Drupal.org is migrated off of Drupal 7.

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024