Idea: Provide code names for major Backdrop releases

This isn't a critical thing but I thought it be fun if each Bd release would have a unique name along with the version number similar to how Ubuntu does it - Ubuntu 5.04 (Hoary Hedgehog) - Ubuntu 4.10 (Warty Warthog) - Ubuntu 5.10 (Breezy Badger)

So maybe we can have: Bd 1.3 (Polished Dragon)

no?

GitHub Link:

https://github.com/backdrop/backdrop-issues/issues/1458

GitHub Issue #:

1458

Log in or register to post comments

Recent topics

Importing the staged config throws an error: another field with the same name already exists

Posted 2 days 3 hours ago by Francis Greaves (themetman) in How-To and Troubleshooting

Comments Enhanced

Posted 1 week 3 days ago by (izmeez) in How-To and Troubleshooting

Why not add a Github star?

Posted 1 week 5 days ago by (izmeez) in How-To and Troubleshooting

Recent comments

@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...

Posted 1 day 20 hours ago by Francis Greaves (themetman) on:

Importing the staged config throws an error: another field with the same name already exists

Thanks, I have to go out now, I will try later on and report back

Posted 2 days 2 hours ago by Francis Greaves (themetman) on:

Importing the staged config throws an error: another field with the same name already exists

Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....

Posted 2 days 2 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:

Importing the staged config throws an error: another field with the same name already exists