Gltf-blender-io: 2.82 release

Created on 25 Nov 2019  路  8Comments  路  Source: KhronosGroup/glTF-Blender-IO

Milestones (from https://developer.blender.org/project/view/89/)

Phase | Description | Start Date | Branch
-- | -- | -- | --
Bcon1 | New features and changes | October 10, 2019 | master
Bcon2 | Improve and stabilize | December 12, 2019 | master
Bcon3 | Bug fixing only | January 9, 2020 | blender-v2.82-release
Bcon4 | Prepare release | February 6, 2020 | blender-v2.82-release
Bcon5 | Release | February 13, 2020 | blender-v2.82-release

At Bcon3

  • [x] Creation of blender-v2.82-release of the addon
  • [x] Bump master to version 1.2
  • [x] Create a 2.83 milestone in github, and rename 2.83+ to 2.84+

Before Bcon4 (--> End of January)

Just before release ( --> First days of Feb. )

  • [x] Check link to documentation in addon code

After release

  • Remove of 2.79 support, Cf #745 for all tasks
task

Most helpful comment

@donmccurdy @emackey @scurest Blender will enter bcon4 tonight. That means that only really critical bugfix (in Blender code source) will be accepted to be merged, after validation of blender project leaders.
So ... for glTF, addon, please do not push any commits for now, except if a really really annoying bug is found (In that case, we should validate the PR with blender project team).

Next week, after the release, we need to remove 2.79 support. See #745
After that, we can go back with classical way of working as we used to do.

All 8 comments

@donmccurdy @emackey @scurest Blender will enter bcon4 tonight. That means that only really critical bugfix (in Blender code source) will be accepted to be merged, after validation of blender project leaders.
So ... for glTF, addon, please do not push any commits for now, except if a really really annoying bug is found (In that case, we should validate the PR with blender project team).

Next week, after the release, we need to remove 2.79 support. See #745
After that, we can go back with classical way of working as we used to do.

2.82 is out. Can we get this done?

Yes, we can close that now.
I will perform 2.79 removal actions during this week

The readme needs to be updated.

I'll update the README.

This link needs to be updated too

link

Yes I've been trying. GitHub is giving a lot of 500 errors today. https://www.githubstatus.com/

Thanks for keeping your eye on it though!

Ah, it took it.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Quinten123 picture Quinten123  路  4Comments

KannebTo picture KannebTo  路  3Comments

spiraloid picture spiraloid  路  5Comments

scurest picture scurest  路  4Comments

capnm picture capnm  路  5Comments