Internationalization backport?

Django Internals Mentorship
1

Hi,

I have done some looking around on the Django documentation regarding backporting and it seems like new features are not typically backported. In my particular case, I was looking to backport the recent addition of Haitian Creole to version 5.2, as we are using the Arches (GH archesproject/arches) platform to catalog elements of Haitian cultural heritage. I have created a fork of 5.2 which patches in the linked fix and am using that in our implementation. Of course, it would be ideal to upstream the language support if possible, especially since Django 6.0 was only just released (congrats!).

All this to say, I wanted to confirm that I was reading the policy correctly, and that I should not create a ticket and PR to backport the addition of Haitian Creole to 5.2.

Thanks for your time!

2

Hi @yshng, welcome! :waving_hand:

You’re right that this won’t be backported, but the good news is that having worked on Arches recently, it should be ready for Django 6.0. We can chat more on the arches forum :smiley:

1 Like
3

Hi @jacobtylerwalls! That’s great news! Thanks for the confirmation, and see you on the Arches forums :slight_smile:

1 Like