Giter Club home page Giter Club logo

release's Introduction

Bootstrap Release Working Group

Release schedule

Release Status Initial Release Active LTS Start Maintenance LTS Start End-of-life
2.x End-of-life 2013-07-18 - - 2013-08-19
3.x End-of-life 2013-08-19 2014-11-01 2016-09-05 2019-07-24
4.x End-of-life 2018-01-18 2019-11-26 2021-11-01 2023-01-01
5.x Active LTS 2021-05-05 TBD TBD TBD

Warning: Dates may vary widely. We are actively working on strengthening timeline assurances.

Release plan

New releases of Bootstrap are made from the main branch to the Active major version. At times to be determined by the release working group, major versions will be frozen and transitioned to Long Term Support (LTS). A long term support branch will be forked from main, making way for semver-major changes to be made on main and a new Active major version to be prepared.

A version in Long Term Support should not have new features landed without a compelling reason. It may continue to receive:

  • Bug fixes
  • Security updates
  • Documentation updates

After a determined period of time, versions in Long Term Support will be deep-frozen and transition to Maintenance.

Versions in Maintenance should not have any changes landed, except for:

  • Critical bug fixes
  • Critical security updates
  • Important documentation updates

Unless a change is urgent, Maintenance releases are likely to be made with minimal frequency.

Upcoming release schedule

A rough schedule of releases has been included here for planning purposes.

Bootstrap 4

  • v4.5.3 in October 2020 (bug fixes and docs)
  • v4.6.0 in January 2021 (feature alignment with v5 and docs)
  • v4.6.1 in October 2021 (bug fixes and docs)
  • v4.6.2 in July 2022 (bug fixes and docs)

Bootstrap 5

  • v5.0.0-alpha2 in September 2020 (delayed due to team vacations)
  • v5.0.0-alpha3 in October 2020 (additional new features and breaking changes)
  • v5.0.0-beta1 in December 2020 (final instance of breaking changes)
  • v5.0.0-beta2 in January 2021 (beta features and bug fixes)
  • v5.0.0-beta3 in March 2021 (beta bug fixes)
  • v5.0.0 in May 2021 (stable release)
  • v5.1.0 in August 2021
  • v5.2.0 in July 2022 (beta in May 2022)
  • v5.3.0 in May 2023 (alphas in December 2022 and in March and April 2023)
  • v5.4.0 TBD

Bootstrap 6

TBD.

LTS team members

Releasers

Security

release's People

Contributors

alex-toucan avatar bardiharborow avatar julien-deramond avatar levure avatar martijncuppens avatar mdo avatar seniorhn avatar xhmikosr avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

release's Issues

Nav sidebar for mobile

Can you please add side bar nav for purely mobile sites like semanticui or material has!. Please add sidenav bar as a new feature in bootstrap 5

Long Term Support plan?

I've read your "Introducing our Long Term Support plan" blog aimed at "strengthening the stability [...] of releases".
The title look good but after reading the blog, it seem to me that a less Orwellian title would be "Reducing the support of releases from 5 years to 1 year" (with LTS included)
or "Reducing the support of releases from 15 months to 1 month" (without LTS included)

I'm filing this has a documentation bug to fix the title the blog, because I believe it is misleading. The second misleading thing in this post is the labelling of "development work" as "current" in the plots. If I read your graphic correctly, the plan is to have no overlap in the future between supported, released versions. If I read your graphic correctly and by any chance 5.0 is released later than planned, there might be no stable version at all as of February 2020.

I've no right to complain, this is free software, but this is still concerning.

Table is unclear for 4.x

The README.md table is unclear for the 4.x version. It is listed as LTS, but also has an end of life date in the past. Is it Active LTS or EOL?

3.x End-of-Life date not consistent

Hi,
when comparing the schedule.svg/schedule.json to the Release Schedule table in the Readme-File, Bootstrap 3 the End-of-Life is still set to "TBD" in the table, while it is declared as 1.4.2019 in the other files.
Thus, which of the two options is the correct one?

Clarification about the maintenance dates for LTS versions

The plan explains in the readme says that a LTS moves to maintenance mode (fixing only critical things) 6 months after the release and reaches end-of-life 6 months later (meaning 1 year after the release).
How does this interact with the release of the next major version ? AFAICT, there is no time-base schedule for the new active major version. If this version takes time to go out, it might actually give very little time to migrate from the LTS version (being the current release) to the new major version once this one goes out. Shouldn't the transition to maintenance mode take into account the release date of the next major version, to ensure that project can benefit from this 6 months maintenance window to perform their migration to the new major version ? In the current process, if releases 5.0 takes 5 months, projects only have 1 month of maintenance to migrate before the end-of-life.

A proposal could be to change the definition of the maintenance start to be "at the release of the new major version or 6 months after the LTS start, whatever happens last".
What do you think ?

Discoverability of EOL status

Right now it is difficult to tell when a version of bootstrap is EOL. If you go to the documentation page for Bootstrap 4 you won't see any notice of any kind that the library is EOL. And if you go on nuget or other package managers the packages aren't deprecated.

Would you consider adding some kind of notice to the documentation pages that say they are no longer supported, and also go in and deprecate unsupported packages so people will realize that what they are using is no longer receiving security and other updates?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.