Support » Plugin: Gutenberg » Gutenberg 7.9

  • Resolved Anonymous User 14934761

    (@anonymized-14934761)


    Why is Gutenberg 7.9 delayed?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Joen A.

    (@joen)

    Every once in a while, life gets in the way. In this case, I imagine focus was on releasing 5.4. Given world affairs doing both a plugin and a core release in late march seems impressive to me.

    Stay tuned!

    Anonymous User 14934761

    (@anonymized-14934761)

    Of course, the reason why I asked was because I saw 7.9 and 8.0 in GitHub as been worked on, while 7.9 getting new tickets there despite having all the tickets closed. So I was wondering why no freeze and release. I like the changes in 7.9 and I am just giving Gutenberg a new try, so that is why I am asking and I prefer to use the newest versions as I saw some things being better than what I see in 7.8.

    Plugin Author Joen A.

    (@joen)

    Tickets in milestones in Github are sometimes shuffled around as priorities shift and move, and the goal definitely is to release the plugin on a regular cadence with what’s stable and ready to go each week.

    Anonymous User 14934761

    (@anonymized-14934761)

    That’s good, I really do think that shifting resources into Gutenberg is more important than scrapping most of the tickets in WordPress. I guess it is always the case that if you have N amount of resources you should allocate most of them on what moves things faster.

    I really didn’t liked Gutenberg in the beginning and I really hated it, yet so much time passed I really hope for the day when most of the plugins are gone and what is displayed on the site is primarly based on blocks which can be easily inserted.

    I was wondering if you need to close all these before a release is made as they are in the “closed” tab as a ticket, but still have some steps inside which are not finished?

    Screenshot:

    https://i.ibb.co/FWhjPzW/Screen-Shot-2020-04-15-at-9-59-26.png

    Plugin Author Joen A.

    (@joen)

    > I was wondering if you need to close all these before a release is made as they are in the “closed” tab as a ticket, but still have some steps inside which are not finished?

    What goes into a release vs. what doesn’t is not always cut and dry. When features are finished and ready to land, they go in. But sometimes bugs are discovered that make them need more time in the oven. Releases should not necessarily be held up based on that.

    I would recommend you follow https://github.com/WordPress/gutenberg/releases for hints at the status of a release.

    Anonymous User 14934761

    (@anonymized-14934761)

    Yeah, it is sure not always a perfect state when released and I guess that is why installing Gutenberg is for the more like a beta quality.

    But before a release do you have to finish all the “steps” inside a ticket?

    Plugin Author Joen A.

    (@joen)

    In general the goal is to complete tickets that are attached to a milestone in Github, yes. But as noted, it does happen that things are shuffled around.

    Anonymous User 14934761

    (@anonymized-14934761)

    I see, thanks!

    Keep safe!

    Plugin Author Joen A.

    (@joen)

    Same to you!

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.