twbs / release Goto Github PK

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?

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.

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

Hi @bardiharborow,

From my previous issue ticket - twbs/bootstrap#29184. I found another page about EOL for 4.x. Can you update on this page as well?

URL: https://github.com/twbs/release/blob/master/schedule.json

Second question, shouldn't each Bootstrap 'family' version (4.x, 5.x, 6.x, etc.) have at least three year life span before EOL?

Thanks,
Kazeem

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?

Version: 4
Stage: LTS
Date: 14 February 2019

Version: 5
Stage: Active
Date: 24 July 2019

Approval:

• @bardiharborow
• @XhmikosR
• @Johann-S
• @mdo

Version: 4
Stage: LTS
Date: v4.4 release date

Notes: Several features were planned from v4.4, which were missed in the planning for #2. We're proposing to backtrack slightly to sneak them in under the wire.

Approval:

• @bardiharborow
• @XhmikosR
• @Johann-S
• @mdo

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 ?

Version: 3
Stage: EOL
Date: 24 July 2019

Approval:

• @bardiharborow
• @XhmikosR
• @Johann-S
• @mdo
• @MartijnCuppens

v5.0.0 in February 2021 (stable release)

Under readme.md, v5 stable was supposed to be released last month. Just wondering if there's an update or any ETA on this?

Has an enlightening text been published on the delays regarding the November and December updates?

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?

Please make spacing responsive