Upgrade boostrap #9337
-
|
Hi, I just see that the static CSS is still using Bootstrap 3.4.1 as we can see on this file : Can we expect an upgrade to a newer version, as bootstrap said on her website that this version is in end of life ? Maybe an upgrade to V5 ? I don't know. Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
|
Is there anything specifically broken on the current DRF usage of Bootstrap? Unless this is the case, I would lean towards not touching anything... #9270 |
Beta Was this translation helpful? Give feedback.
-
I don’t know if it’s a problem, but today, when one wants to modify or extend HTML files coming from Django REST Framework, one finds oneself having to use quite old Bootstrap classes, and I don’t understand why we should be limited to that and not update it. Since this version is quite old, the risks of the emergence of vulnerabilities are greater. |
Beta Was this translation helpful? Give feedback.
-
|
so ? |
Beta Was this translation helpful? Give feedback.
-
|
... From #7411 this looks to be a seriously involved change... 
I think that's less risky than some much smaller PRs that effect the Python codebase, since lots of it is just changes in CSS class names, etc. But, still. Anyways, questions...
|
Beta Was this translation helpful? Give feedback.
-
|
Your concern about the current version we're using is valid; however, it's important to recognize the substantial improvements that have been made from Bootstrap 3 to Bootstrap 5. The latest version offers a more modern approach to design and usability. It introduces new features and optimizations that enhance both the speed and responsiveness of web projects. Additionally, Bootstrap 5 comes with improved accessibility features and drops support for older, less secure browsers, which is crucial for maintaining the security and efficiency of our site. Upgrading to Bootstrap 5 not only future-proofs our work but also significantly improves the user experience with cleaner, more efficient code, and a range of new components and utilities that are not available in Bootstrap 3. Considering the advantages outlined, it’s clear that they outweigh the potential challenges we might face during the update process. Bootstrap 5’s modern features, enhanced security measures, and improved accessibility support present a compelling case for transition. Importantly, we must also acknowledge that Bootstrap has officially announced the end-of-life status for our current version. This means that continuing with the outdated version not only hinders our access to new functionalities and optimizations but also exposes us to security vulnerabilities due to the lack of future patches or support. Given these factors, transitioning to Bootstrap 5 becomes not just an opportunity for improvement but a necessary step to ensure the longevity and security of our project. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
I don't see a compelling reason to justify the migration effort/risk. Only "potential" issues. Granted, it's deprecated, but I would still be in the "if ain't broke, don't fix it" camp. |
Beta Was this translation helpful? Give feedback.
-
|
So let's use Something deprecated nice ! Modern, secure, alive, updated, nice. |
Beta Was this translation helpful? Give feedback.
It probably is okay for us to accept some amount of upgrade changes, we just need a really high quality bar before accepting them.Edit: It's unclear to me to what extent we should consider allowing upgrade changes, given that they also introduce friction and risk. If we are going to do so, then we need a really high quality bar before accepting them....
From #7411 this looks to be a seriously involved change...
I think that's less risky than some much smaller PRs that effect the Python codebase, since lots of it is just changes in CSS class names, etc. But, still.
Anyways, questions...