[Bf-committers] Bcon4 for Blender 2.90

[Nathan 'jesterKing' Letwory via Bf-committers]

Hey all,

We're now in bcon4 for Blender 2.90 development cycle [1]. This
means only critical and carefully reviewed bug fixes are allowed
in the blender-v2.90-release branch.

We're currently on target for 2.90 release on August 26th [2].

As a reminder development for 2.91 in master is in bcon1 and
will last until September 16th [3].

In other news, the fifth 2.83 LTS maintenance release saw light
today.

/Nathan

[1] https://wiki.blender.org/wiki/Process/Release_Cycle
[2] https://developer.blender.org/project/view/110/
[3] https://developer.blender.org/project/view/117/

-- 

Nathan Letwory - nat...@blender.org - www.blender.org
Release & Infra
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender 2.90 bcon 3

[Nathan 'jesterKing' Letwory via Bf-committers]

Hi,

The blender-v2.90-release branch has been created according
the release cycle new stabilizing branch section [1].

Please do read over how to use the stabilizing branch [2]
to refresh on how to go about with fixes.

Also check the workboard with work still to do for 2.90. [3]

This means that master is now 2.91 bcon1. [4]

Cheers,

/Nathan


[1] https://wiki.blender.org/wiki/Process/Release_Cycle
[2] https://wiki.blender.org/wiki/Process/Using_Stabilizing_Branch
[3] https://developer.blender.org/project/board/110/
[4] https://developer.blender.org/project/board/117/



-- 

Nathan Letwory - nat...@blender.org - www.blender.org
Release & Infra
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender developer meeting notes 2020.07.13

[Nathan 'jesterKing' Letwory via Bf-committers]

Notes for the meeting of Monday, 13 July 2020. 11:00 CEST / UTC 09:00
on #blender-coders on blender.chat.

Please read the full notes on https://devtalk.blender.org/t/13-july-2020/14246

Announcements
=
* Bug Sprint Week [1] for the week 13-17 July 2020.
* Reminder to not share copyrighted material [2] as part of
discussions/design work.
* Kévin Dietrich starts working on Cycles API through a grant

Blender 2.83.2
==
* Released last week, with 15 fixes. This week more automation of
steps involved (Steam and Snap).

Blender 2.90

* Bcon3 currently planned for 22nd of July. Developers are urged to
ensure their work is in good shape. See the planning [3].
* Developers are reminded to update the wiki pages after commits, even
for experimental features [4]

/Nathan

[1] https://lists.blender.org/pipermail/bf-committers/2020-July/050617.html
[2] https://lists.blender.org/pipermail/bf-committers/2020-July/050616.html
[3] https://developer.blender.org/project/view/110/
[4] https://wiki.blender.org/wiki/Reference/Release_Notes/2.90
-- 

Nathan Letwory - nat...@blender.org - www.blender.org
Release & Stuff
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender developer meeting notes 2020.07.06

[Nathan 'jesterKing' Letwory via Bf-committers]

Hi all,

Here are the notes for meeting of Monday, 6 July 2020. 18:00 CEST /
UTC 16:00 in #blender-coders on blender.chat.

Read the complete report on: https://devtalk.blender.org/t/6-july-2020/14101

Announcements
=

* New demo file: Blender 2.83 splashscreen [1]
* Bug sprints announcement [2]
* Blender Conference 2020 cancelled [3]

GSoC first evaluations
=

* All students passed the first evaluations. All the best to the
students for the second period!

2.83 LTS

* Jeroen Bakker has been working on automation of the LTS release
process. Not fully done yet, so partly still manual work (updating
different distribution channels)
* 2.83.2 scheduled for Thursday 9 July, 2020
* Blender 2.83 LTS maintenance task [4] with current status

[1] https://www.blender.org/download/demo-files/
[2] https://code.blender.org/2020/07/bug-sprints/
[3] https://lists.blender.org/pipermail/bf-committers/2020-July/050610.html
[4] https://developer.blender.org/T77348

/Nathan


Nathan Letwory - nat...@blender.org - www.blender.org
Release & Stuff
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender 2.90 in bcon2

[Nathan 'jesterKing' Letwory via Bf-committers]

Hey all,

We're now in bcon2 for Blender 2.90. This means we're now
stabilizing and improving Blender in the main development
branch `master`. That means no new big features, especially
not unplanned ones.

If you got caught out by this move to bcon2 be sure to contact
Dalai Felinto.

Bcon2 is scheduled to last until July 22nd, when we move
to bcon3. That is also when we'll be creating the 2.90
release branch.

Best,

/Nathan


Nathan Letwory - nat...@blender.org - www.blender.org
Release & Infra
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] 2.83 LTS released!

[Nathan 'jesterKing' Letwory via Bf-committers]

Hey all,

Today we released 2.83! Yet another great looking version
of Blender ready for the world.

A huge thanks to all involved :)

This also means that we all can focus more on 2.90. All
work can go to master now, bcon1 for that is still on.

Soon there will be some more details on how the work for
2.83 LTS is going to be realised.

Happy 2.83-days!

/Nathan Letwory


Nathan Letwory - nat...@blender.org - www.blender.org
Release & Infra
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] bcon5 for 2.83

[Nathan 'jesterKing' Letwory via Bf-committers]

Hey,

I just wanted to let you all know that we are in the final stages of
release preparation for 2.83. We're in bcon5 for 2.83 now.

/Nathan Letwory


Nathan Letwory - nat...@blender.org - www.blender.org
Release & Infra
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Getting ready for 2.83 - no commits to 2.83 branch!

[Nathan 'jesterKing' Letwory via Bf-committers]

Hi all,

As we're getting ready for release of 2.83 please no longer commit
to the blender-v2.83-release branch! (Unless explicitly asked to by
me or Dalai).

Thanks,

/Nathan


Nathan Letwory - nat...@blender.org - www.blender.org
Release & Infra
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Heads-up for 2.83 bcon 3 today

[Nathan 'jesterKing' Letwory via Bf-committers]

Hey all,

A heads up that today we'll see the creation of the
stabilization branch for Blender 2.83 as we roll into
bcon 3. [1]

The following sha1's will be used to create the branches
of for submodules:

- Dev Tools (rBDT): 35dd27ded664
- Translations (rBT): c68481a509ea
- Add-ons (rBA): 6f49528c8364
- Add-ons Contrib (rBAC): 9468c406fb55

The final sha1 for Blender main repository will be
clear when I'm going to actually branch it, but at the
moment Campbell Barton landed several commits
just before this writing (and after checking with him
several more might still come). But somewhere HEAD
during this morning, right now that looks to be
the commit 5e05db3419ef.

I'll poke #blender-coders over at blender.chat when I'm
starting the process.

Please do read over how to use the stabilizing branch [2]
to refresh on how to go about with fixes.

Also check the workboard with work still to do for 2.83. [3]

Cheers,

/Nathan


[1] https://wiki.blender.org/wiki/Process/Release_Cycle
[2] https://wiki.blender.org/wiki/Process/Using_Stabilizing_Branch
[3] https://developer.blender.org/project/board/105/


Nathan Letwory - nat...@blender.org - www.blender.org
Release & Infra
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender developer meeting notes - 2020.4.14

[Nathan 'jesterKing' Letwory via Bf-committers]

On Tue, 14 Apr 2020 at 19:59, Dalai Felinto via Bf-committers
 wrote:
> * Workboard is still not updated (this was brought up last week’s
> meeting). Dalai Felinto will handle it next Monday if it is still not
> there by then.

That was a misunderstanding on my behalf. I have populated the
workboard with all current high-priority tasks.

I'd like to ask all module owners (and those who have such tasks
already assigned to them) to have a good look through the items in
the bcon3 column of the workboard [1].

Ideally we handle all the high-priority items, but if you think the
task isn't feasible for 2.83 you should retag with the 2.90 tag and
make a clear comment on why you'd reschedule.

In addition to these high-priority tasks it would be great if module
owners could look through other open tasks to see if there are
any that could still be reasonably fit into 2.83 and tag them as
such.

/Nathan


Nathan Letwory - nat...@blender.org - www.blender.org
Release & Infra
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Long Term Support and implications

[Nathan 'jesterKing' Letwory via Bf-committers]

Hey all,

I wrote over on devtalk a bit on this topic [1]. Before I
quickly summarize (copy) the main points I'd
like to ask any discussion on the topic be done in one
place, on the topic thread.

With the LTS idea there are several things we have to
keep in mind as it will impact the way we work in
making Blender the best it can be.

  * A new LTS release each May, good for 2 years
  * In August 2021 we’ll be running no less than 3 concurrent
releases (2.83 LTS, 2.93 LTS, 3.0 non-LTS)
  * API needs to stay unbroken for 2 years in an LTS release
  * Triaging and bugfixing will need to be done against all current
releases (in 2021 that’d be 2.83 LTS, 2.93 LTS, 3.0 non-LTS)
  * Documentation needs to be properly branched, managed and
maintained with the three concurrent releases in mind
  * Find good release cadence for patch releases (maybe once a
month to keep big pile-up from happening).

Cheers,

/Nathan Letwory

[1] https://devtalk.blender.org/t/long-term-support-and-its-implications/12525
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Release cycle chedule for 2.90

[Nathan 'jesterKing' Letwory via Bf-committers]

Hi all,

With release branching for 2.83 coming up on April 15
and its release set on May 20 I am created the next
milestone project for 2.90 [1] with some dates. Following
the main release cycle phases [2] and the LTS post [3] from
Ton Roosendaal they currently look as follows:

Bcon1 April 15, 2020 (master)
Bcon2 June 10, 2020 (master)
Bcon3 July 8, 2020 (blender-v2.90-release)
Bcon4 August 5, 2020 (blender-v2.90-release)
Bcon5 August 12 20, 2020 (blender-v2.90-release)

I'd like to us to confirm these during the next developer
meeting on April 6. If you feel these dates are don't work
well for a reason please reply here with arguments.

Thanks,

/Nathan Letwory

[1] https://developer.blender.org/project/view/110/
[2] https://wiki.blender.org/wiki/Process/Release_Cycle
[3] https://code.blender.org/2020/02/release-planning-2020-2025/
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Proposal of a 2.82b release (for bug fixing)

[Nathan 'jesterKing' Letwory via Bf-committers]

Hi,

I'm hesitant to do a corrective 2.82b based on the commits presented here. The
GPencil edit mode crash commit bug report T74969 already mentions in its
description that it worked in 2.82a. The commit fixes in code that was heavily
refactored in `master` long after the 2.82 release branch was created.

Similarly fix for T74876. The code that is fixed in efdc93fcc692 did
not exist in
2.82a.

I don't see a need for a release unless we get clear reports and fixes for
2.82a specifically.

Thanks,

/Nathan Letwory
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Introducing myself and my GSOC Proposal/Application: Improve Compositor Performance

[Nathan 'jesterKing' Letwory via Bf-committers]

Hello Harald,

If you haven't already please visit our GSoC wiki page [1]. It bundles all
information relevant to the GSoC. There are links [2] to suggestions and
tips compiled by Google based on experience over the years.

Very last minute, so you'll have to be quick! Good luck with writing
and submitting your proposal.

Best regards,

/Nathan Letwory

[1] https://wiki.blender.org/wiki/GSoC
[2] https://wiki.blender.org/wiki/GSoC/Getting_Started#First_Steps


On Tue, 31 Mar 2020 at 00:08, Harald Reingruber via Bf-committers
 wrote:
>
>  Hi dear Blender Developer Community,
>
> I want to submit a proposal for the "Improve Compositor Performance"
> project idea of this year's Google Summer of Code.
>
> Right now, I am doing a sabbatical (since November 2019) and am enrolled at
> the Vienna University of Technology. Before that, I was working as a
> Software Developer for several years mostly on graphics related software
> (Ogre3D, Unity3D, Augmented Reality Apps, Medical Image Processing, etc.).
> I really like open-source software, was able to do some small contributions
> to projects like Emscripten, Ogre3D, and several JavaScript projects. I
> think the GSOC program is an awesome opportunity to work fulltime on Open
> Source Software, like yours.
>
> Due to the current pandemic situation, I hand to do re-organize and partly
> reschedule my Coding Tour I was already starting in the US for the next
> couple of weeks. This is the reason for my "last-minute" application.
> Fortunately, I am able to continue the tour online, here from Austria. Here
> is a link describing my tour
> ,
> in case you are curious.
> Anyway, even though I am behind schedule for my GSOC proposal I hope that I
> will be able to submit a successful application to you and show you that I
> am able to succeed in improving the Compositor Performance.
>
> The reason why I chose the "Improve Compositor Performance" project idea is
> because I am a huge fan of writing automated tests and profiling
> cpu/memory performance.
>
> Do you have any suggestions, tips and/or tricks for my proposal submission?
>
> Thanks in advance for your support,
> Harald
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Preparing for 2.83 bcon2

[Nathan 'jesterKing' Letwory via Bf-committers]

Hi all,

sorry for the confused messaging. We _are_ going to bcon2. I was just
too early with the branching messaging, which happened because I
misinterpreted the dev meeting notes.

So, bcon2 is there with exception of sequencer disk cache that
Sergey Sharybin and Richard Antalik still try to finalize.

Other than that it is bug fixing and stabilizing. The branching will
happen when we do move to bcon3 in April.

Happy improving and stabilizing!

/Nathan


On Wed, 18 Mar 2020 at 15:54, Nathan 'jesterKing' Letwory
 wrote:
>
> I meant obviously move to bcon3...
>
> /Nathan
>
> On Wed, 18 Mar 2020 at 15:38, Nathan 'jesterKing' Letwory
>  wrote:
> >
> > Hi all,
> >
> > Just a quick heads-up that I'll be creating the blender-v2.83-release
> > branch soon and make the necessary commits and pushes to have
> > us enter bcon2 for 2.83.
> >
> > I have pulled blender.git such that I'll be using efdc93fcc6923a735
> > from master, and I'll be using the respective masters for each
> > submodule as follows:
> >
> > 'release/datafiles/locale' commit 885c753570b09
> > 'release/scripts/addons' commit 6665bb9820c46
> > release/scripts/addons_contrib' commit 9468c406fb5
> > 'source/tools' commit 4a6f1706258439
> >
> > To prepare yourself for bcon2 please revisit the documentation
> > on how to work with the stabilization branch [1] & [2]
> >
> > I'll write on this list again when I've completed the motions.
> >
> > /Nathan
> >
> > [1] https://wiki.blender.org/wiki/Process/Using_Stabilizing_Branch
> > [2] https://wiki.blender.org/wiki/Process/Playbook_Merge_Handling
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Preparing for 2.83 bcon2

[Nathan 'jesterKing' Letwory via Bf-committers]

I meant obviously move to bcon3...

/Nathan

On Wed, 18 Mar 2020 at 15:38, Nathan 'jesterKing' Letwory
 wrote:
>
> Hi all,
>
> Just a quick heads-up that I'll be creating the blender-v2.83-release
> branch soon and make the necessary commits and pushes to have
> us enter bcon2 for 2.83.
>
> I have pulled blender.git such that I'll be using efdc93fcc6923a735
> from master, and I'll be using the respective masters for each
> submodule as follows:
>
> 'release/datafiles/locale' commit 885c753570b09
> 'release/scripts/addons' commit 6665bb9820c46
> release/scripts/addons_contrib' commit 9468c406fb5
> 'source/tools' commit 4a6f1706258439
>
> To prepare yourself for bcon2 please revisit the documentation
> on how to work with the stabilization branch [1] & [2]
>
> I'll write on this list again when I've completed the motions.
>
> /Nathan
>
> [1] https://wiki.blender.org/wiki/Process/Using_Stabilizing_Branch
> [2] https://wiki.blender.org/wiki/Process/Playbook_Merge_Handling
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Preparing for 2.83 bcon2

[Nathan 'jesterKing' Letwory via Bf-committers]

Hi all,

Just a quick heads-up that I'll be creating the blender-v2.83-release
branch soon and make the necessary commits and pushes to have
us enter bcon2 for 2.83.

I have pulled blender.git such that I'll be using efdc93fcc6923a735
from master, and I'll be using the respective masters for each
submodule as follows:

'release/datafiles/locale' commit 885c753570b09
'release/scripts/addons' commit 6665bb9820c46
release/scripts/addons_contrib' commit 9468c406fb5
'source/tools' commit 4a6f1706258439

To prepare yourself for bcon2 please revisit the documentation
on how to work with the stabilization branch [1] & [2]

I'll write on this list again when I've completed the motions.

/Nathan

[1] https://wiki.blender.org/wiki/Process/Using_Stabilizing_Branch
[2] https://wiki.blender.org/wiki/Process/Playbook_Merge_Handling
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] 2.82a release motions starting morning of March 12, 2020

[Nathan 'jesterKing' Letwory via Bf-committers]

Hi all,

looks like we have all the commits in that we want. Unless I
hear sounds to the contrary I'll be bumping the version and
tagging the blender-v2.82-release branch for 2.82a and
initiate builds on buildbot for release.

Cheers,

/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender developer meeting notes - 2020.3.9

[Nathan 'jesterKing' Letwory via Bf-committers]

Hi again,

I pushed 8 more commits that were designated today [1]. If we can please
have at least the devs who are involved with the fixes have a test
build of current blender-v2.82-release and see to it their fixes made
it in properly.

Any additional testing by anyone is very much appreciated. Report on
the task page [1] would be best, but blender.chat or in reply to this
message will work too.

/Nathan

[1] https://developer.blender.org/T74274#888482

On Mon, 9 Mar 2020 at 22:12, Nathan 'jesterKing' Letwory
 wrote:
>
> Hi,
>
> I have cherry-picked and fixed up the proposed changes as currently
> stands in T74274 . If people could please do a test build on their
> own boxes of the blender-v2.82-release branch that'd be very much
> appreciated. `make test` came up clean on my MacOS machine.
>
> /Nathan
>
> On Mon, 9 Mar 2020 at 12:40, Dalai Felinto via Bf-committers
>  wrote:
> > 2.82a
> > 
> > * Release date is still this Thursday, March 12th.
> > * Nathan Letwory will handle release management for 2.82a.
> > * Developers, be sure any intended fix to be backported is mentioned in 
> > T74274
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender developer meeting notes - 2020.3.9

[Nathan 'jesterKing' Letwory via Bf-committers]

Hi,

I have cherry-picked and fixed up the proposed changes as currently
stands in T74274 . If people could please do a test build on their
own boxes of the blender-v2.82-release branch that'd be very much
appreciated. `make test` came up clean on my MacOS machine.

/Nathan

On Mon, 9 Mar 2020 at 12:40, Dalai Felinto via Bf-committers
 wrote:
> 2.82a
> 
> * Release date is still this Thursday, March 12th.
> * Nathan Letwory will handle release management for 2.82a.
> * Developers, be sure any intended fix to be backported is mentioned in T74274
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender 2.82 BCon4 in effect from now 2020.02.06

[Nathan 'jesterKing' Letwory]

Hi all,

>From this moment on we're in BCon4 in the 2.82 release cycle.

As a refresher read the Release Cycles [1] page on our wiki. With
BCon4 in place the blender-v2.82-release branches are now
open for CRITICAL fixes (mainly crashes) only.

Any cleaning up and non-critical fixes should now go into master
for 2.83.

If you find a critical bug in 2.82 make sure to poke me in the very
least. Together with module owners we will decide whether the
issue is urgent enough to still require a fix in blender-v2.82-release.
This holds for both the main repository blender.git as all submodules,
with the exception for the localization submodule which is expected
to roll out an update sometime coming Monday.

Besides that focus for 2.82 is now on finishing up documentation,
release notes and get ready for final release. BCon5 is scheduled
for 2020.02.13.

I'll roll submodules to their respective heads on blender-v2.82-release
right after this message is sent.

That's all folks,

/Nathan Letwory

[1] https://wiki.blender.org/wiki/Process/Release_Cycle#2.8x_Release_Cycle
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Reminder: moving to 2.82 work to bcon4 on 2020.02.06

[Nathan 'jesterKing' Letwory]

Hi all,

Just a reminder to you all that it looks like we're set to move
2.82 to bcon4 tomorrow.

We'll move to bcon4 at the end of the dutch work day. Sometime
between 15:00-1800 CET.

At this time of writing the workboard for 2.82 [1] is empty barring
documentation tasks. This means that essentially we're ready
for 2.82, so when you still are planning to commit fixes to 2.82
make sure you are ready to handle any potential fall-out. If fixes
aren't especially important for 2.82 then please already prefer to
commit those to master.

As a reminder for bcon4: I'd appreciate it very much that no further
commits go to blender-v2.82-release branches, unless specifically
agreed with me, Dalai Felinto and module owners.

If there are bugs reported that are absolute show-stoppers for
2.82 contact me as soon as possible. We'll figure out what to
do. Once in bcon4 any other improvement or quick fix really should
go in master.

If you think I have missed anything important for 2.82 please don't
hesitate to reply with such concerns.

Best regards,

/Nathan Letwory

[1] https://developer.blender.org/project/board/89/
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Developer meeting 13 January 2020 - notes

[Nathan 'jesterKing' Letwory]

Notes for meeting of Monday, 13 January 2020. 10:00 CET / UTC 9:00
in #blender-coders on blender.chat.

Blender 2.82


* As part of maintenance ensure 2.81 and 2.81a are properly
  tagged. After that the old 2.81 stabilizing branch can be
  dropped.
* Linux archive name will be simplified to
  `blender-$version$-linux64.tar.gz`, dropping the modifiers
  `glibc217` and  `x86_64`.
* Sergey Sharybin will see to it Mantaflow gets fixed by Sebastián
  Barschkis.

Blender 2.83


* Antonio Vazquez is working on Grease Pencil refactor. As part of
  this is refactor of area related to datablock evaluation for
  modifiers. He requests help from Sergey Sharybin on this.
* LANPR will be after 2.83.

Other
=

* Dalai Felinto would like to move the morning meeting from 10:00
  CET to 11:00 CET. Monday morning meetings will from 27th January
  on be on 11:00 CET (10:00 UTC).

Next meeting is on Monday, 20 January 2020 in #blender-coders on
blender.chat [1].

The full notes and changes is on devtalk [2]



[1] https://blender.chat/channel/blender-coders
[2] https://devtalk.blender.org/t/13-january-2020/11190
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Entering 2.82 bcon3

[Nathan 'jesterKing' Letwory]

Hey all,

The stabilizing branch blender-v2.82-release has been created
and pushed. For 2.82 we have now entered bcon3 [1].

Please remember to review the stabilizing usage steps to refresh
your memory on the proper approach [2]. As a friendly reminder,
speed is not important, careful and thoughtful committing is.

Do check the project page [3] and its workboard for determining
what work to do. If you are unsure you can ask Dalai Felinto
(@dfelinto in #blender-coders on blender.chat).

With bcon3 for 2.82 this means we now have our master branch
in bcon1, open for new work and features.

Cheers,

/Nathan

[1] https://wiki.blender.org/wiki/Process/Release_Cycle#2.8x_Release_Cycle
[2] https://wiki.blender.org/wiki/Process/Using_Stabilizing_Branch
[3] https://developer.blender.org/project/profile/89/
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Slight delay in moving to bcon3, and freezing master for a while.

[Nathan 'jesterKing' Letwory]

Hey all,

I am ready for it all, but it appears that our git server isn't. All commits
are lined up. I can't push the blender-v2.82-release branch just yet.

I need intervention magic by Sergey Sharybin. Once he has pressed
the right buttons I'll be able to push the branches and complete the
move to bcon3.

Until then, please no pushing to master in blender.git. Sometime during
Friday morning all will be fine and dandy again.

Thanks for understanding!

Best regards,

/Nathan Letwory
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender developer meeting notes - 2019.12.30

[Nathan 'jesterKing' Letwory]

Notes for meeting of Monday, 30 December 2019. 10:00 CET /
9:00 UTC on #blender-coders on blender.chat.

Full post at devtalk [1]

Blender 2.82


* Currently Tracker Curfew [2] is in effect: focused effort on
  bringing open bugs count down
* Stabilizing branch to be created on 9th of January

Blender 2.83


* On 9th of January stabilizing branch for 2.82, at which point
  master will be effectively open for 2.83 work

Next meeting on Monday, 6 January 2020, 18:00 CET / 17:00 UTC in
#blender-coders on blender.chat.

Happy new year!

/Nathan Letwory


[1] https://devtalk.blender.org/t/30-december-2019/11068
[2] https://code.blender.org/2019/12/tracker-curfew/
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Tracker curfew to start on Monday

[Nathan 'jesterKing' Letwory]

Hi Aaron,

This is a good question. How to ensure these todos and know
issues stay updated. Essentially this is part of what module
owners should manage: for each release cycle go over the
known issues and todos for their module. Update descriptions
where necessary, thus ensuring they stay relevant.

When module owners start planning work they should take
these into account as well. When an old issue (known issue
or todo) is moved to be handled for a release cycle it then
can be set to be bug again.

That should cover screening and revisiting old issues, at
the same time ensuring they stay up-to-date.

/Nathan

On Sat, 21 Dec 2019 at 03:47, Aaron Carlisle  wrote:
>
> Hi,
>
> One question that I have is how will known bugs and issues be documented
> well?
> In the past, there has been a list of todos on the old wiki which often
> became quickly out of date.
> These have since been copied and pasted to
> https://developer.blender.org/project/board/53/ (in the wiki column)
> these tasks are just collecting dust there also.
>
> What needs to happen is a way that these issues can be documented well and
> stay up to date.
> In the process of these old todos need to be screened and integrated into
> this new method of logging reports.
>
> Thanks,
>
> Aaron Carlisle
>
> On Fri, Dec 20, 2019 at 11:15 AM Dalai Felinto  wrote:
>
> > Hi,
> >
> > On Monday, Blender begins a tracker curfew.
> > Please check the teaser video: https://www.youtube.com/watch?v=HDE2ARiN1a0
> >
> > A more complete document will follow suit, but the gist is: from now on the
> > Blender Foundation is going to adhere to a strict definition of what a bug
> > is.
> >
> > * It is only a bug if the code was intended to work and it fails, or when a
> > an issue used to work and it fails.
> > * It is only a bug if the module is in active maintenance. Otherwise it
> > might be registered as known issue.
> > * If a bug fix takes more than a day, it is not a bug, it is a development
> > task (if parts of the module plans) or a feature request (which we don’t
> > support at the moment).
> > * If a bug won’t be worked on for the upcoming 6 months, it is not a bug,
> > it is a known issue that needs to be documented.
> >
> > The developers under contract will dedicate 2 full-days a week to work in
> > the tracker to re-triage issues, fix bugs and patch review.
> >
> > Some stats following this definition. From a universe of 2,042 open reports
> > Blender has:
> >   * 631 untriaged reports.
> >   * 37 confirmed high priority bugs.
> >   * 1,367 reports that may be either a bug or a known issue
> >
> > In the end the tracker curfew is to bring confirmed bugs down to a
> > manageable number (~200). There is a similar goal for patch review, but I
> > will leave this for the official code.blender.org post next week.
> >
> > Have a great weekend,
> > Dalai
> > ___
> > Bf-committers mailing list
> > Bf-committers@blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
> >
>
>
> --
> Aaron Carlisle
>
> Project administrator for the Blender 3D Documentation Project
> Email: carlisle@gmail.com
> Website: https://blendify.github.io
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Developer meeting notes 16 December 2019

[Nathan 'jesterKing' Letwory]

Hi all,

Sorry, I typoed. Next meeting of course at 18:00 CET, not 16:00 CET
(23 December 2019).

/Nathan



On Mon, 16 Dec 2019 at 13:47, Nathan 'jesterKing' Letwory
 wrote:
>
> Notes for meeting of Monday, 16 December 2019.
>
> Next meeting on Monday, 23 December 2019, 16:00 CET / 17:00 UTC.
>
> 2.82 status
> ===
>
> * Mantaflow will land today 16 December 2019.
> * Bcon 2 will be in effect after Mantaflow lands. Dalai Felinto
>   will notify bf-committers and update necessary pages to reflect
>   new status.
> * In Bcon2 note that `master` branch is open for fixes and agreed
>   improvements only. New work is to be conducted in feature
>   branches.
> * Bcon2 will last until 9 January 2020.
>
> Other issues
> 
>
> * Jeroen Bakker requests comments for T72007 [1] - `Design: EEVEE
>   Compositing` task
> * Jeroen Bakker will work with Sebastian Parborg on LANPR patch
>   review.
> * Dalai Felinto will post list of people to contact for issues
>   with dev or infra for duration of the holiday season.
>
> See devtalk thread [2] for full notes and changes.
>
> Cheers,
>
> /Nathan Letwory
>
> [1] https://developer.blender.org/T72007
> [2] https://devtalk.blender.org/t/16-december-2019/10860
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Developer meeting notes 16 December 2019

[Nathan 'jesterKing' Letwory]

Notes for meeting of Monday, 16 December 2019.

Next meeting on Monday, 23 December 2019, 16:00 CET / 17:00 UTC.

2.82 status
===

* Mantaflow will land today 16 December 2019.
* Bcon 2 will be in effect after Mantaflow lands. Dalai Felinto
  will notify bf-committers and update necessary pages to reflect
  new status.
* In Bcon2 note that `master` branch is open for fixes and agreed
  improvements only. New work is to be conducted in feature
  branches.
* Bcon2 will last until 9 January 2020.

Other issues


* Jeroen Bakker requests comments for T72007 [1] - `Design: EEVEE
  Compositing` task
* Jeroen Bakker will work with Sebastian Parborg on LANPR patch
  review.
* Dalai Felinto will post list of people to contact for issues
  with dev or infra for duration of the holiday season.

See devtalk thread [2] for full notes and changes.

Cheers,

/Nathan Letwory

[1] https://developer.blender.org/T72007
[2] https://devtalk.blender.org/t/16-december-2019/10860
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Meeting notes 2 December 2019

[Nathan 'jesterKing' Letwory]

Here are the belated notes for the 2 December 2019 meeting.

Full notes can be read at [1]

Blender 2.81a
=

- Mac issue is solved
- 'a' on Wednesday
- Clément Foucault is working on another important issue T71576
[2]
- Weight paint selection fix (T71213 / f1ac64921b49)
- Fix in rigify T71678#818622

Blender 2.82


- Planning: e-mail from Dalai Felinto [3]
- Philipp is 100% bugtracker
- Seb P. cloth patches + LANPR
- LANPR needs extra reviewers
- USD exporter maaaybe?

Other topics


- Clément Foucault has a solution for thick lines on macOS. He
wants to keep it low profile for now for some reason.
- Static override proposal from Alexander Gavrilov T72062 [4]
- Alexander Gavrlov have patches for review by both developers and
rggers:
  * D6264 and D6297 are small and need review from Campbell Barton
and Sybren Stüvel correspondingly
  * D3837 and D4994 are the bigger old ones, for Campbell Barton
and Bastien Montagne to look into, but at less priority, since
they are old anyway.
  * D3837 needs testing and feedback from riggers - so far I've
got some 'may be useful' feedback based on the description
from Demeter Dzadik and Ivan Cappiello, but no actual real
world testing feedback

Next meeting is 9 December 2019, 18:00 CET / 17:00 UTC in
#blender-coders at blender.chat

[1] https://devtalk.blender.org/t/2-december-2019/10662
[2] https://developer.blender.org/T71576
[3]
https://lists.blender.org/pipermail/bf-committers/2019-November/050344.html
[4] https://developer.blender.org/T72062
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender Developer Meeting Notes 18 November 2019

[Nathan 'jesterKing' Letwory]

Notes for meeting of Monday, 18 November 10:00 CET / 9:00 UTC on
#blender-coders on blender.chat.

Blender 2.81


* Remaining non-showstopper bugs moved from 2.81 to 2.82
  workboard.
* Note to all devs: no commits to blender-v2.81-release branch,
  unless for a scheduled critical bug.
* Landing of splash, tagging and Ahoy on Wednesday November 20th.
  Release will happen later in the afternoon.
* Windows builds will be created on the buildbot, including
  signing. MacOS builds will be signed still out-of-buildbot.

Blender 2.82


* Proposals and patches for new features should be submitted and
  handled by December 12th, 2019.
* MantaFlow and LANPR are in good shape, but need still help to
  get through the review process so that patches can land.
* Undo speed-up (re-)using depsgraph progressing.
* Library overrides get improvements.
* Assets may get some partial patches applied.
* GPencil improvements.
* Sculpting improvements.
* Integrate rest of buildbot release building features
  (codesigning, notarization).

Changes And New Features


Blender 2.81


* A dozen fixes.

Blender 2.82


* Add TBB allocator support on Windows. (Ray Molenkamp)
* GPencil MultiStroke Modifier that creates multiple strokes
  around original stroke. (Yiming Wu, Antonio Vazquez)

Have a good week!

/Nathan Letwory
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Postpone Bcon5

[Nathan 'jesterKing' Letwory]

Oops, forgot the link:

[1] https://developer.blender.org/project/board/88/

On Wed, 13 Nov 2019 at 07:19, Nathan 'jesterKing' Letwory
 wrote:
>
> Hi,
>
> There are a few showstopper issues that need some extra
> attentions. There is a new track on the workboard for 2.81
> called Show Stoppers [1].
>
> We'll recheck the status of the tracker on Monday 18th
> during the Developer Meeting in #blender-coders on
> blender.chat . This means that Bcon4 will extend to at least
> the Monday.
>
> Best regards,
> /Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Postpone Bcon5

[Nathan 'jesterKing' Letwory]

Hi,

There are a few showstopper issues that need some extra
attentions. There is a new track on the workboard for 2.81
called Show Stoppers [1].

We'll recheck the status of the tracker on Monday 18th
during the Developer Meeting in #blender-coders on
blender.chat . This means that Bcon4 will extend to at least
the Monday.

Best regards,
/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Screenshots for release log 2.81

[Nathan 'jesterKing' Letwory]

Hey all,

We're getting close to release. Could we please
see some good screenshots added to the release notes [1]
to at least the sections 'Sculpt & Retopology',
'Viewport : Look Development', 'User Interface : Outliner',
'User Interface : Filebrowser', 'More Features'? An  hour or two
today or tomorrow to put in these screenshots to show of our
new features would be very much appreciated. These will likely
end up also on the release log on blender.org .

Cheers,

/Nathan

[1] https://wiki.blender.org/wiki/Reference/Release_Notes/2.81
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender 2.81 release cycle - continuing as planned.

[Nathan 'jesterKing' Letwory]

Hey all,

As mentioned in the meeting notes [1]  I aired the idea
that maybe we could bump the release date with a week.

After some discussion with Dalai Felinto we think the best
way is to stick to the dates we already agreed on.

There are still some 10 bugs on the workboard in the bugs
track [2], but not all of them look like they are an absolute
must. Therefor we'd like to keep the current tasks on the
track, but reschedule them if they don't get handled by the
end of the week. Priority should be given to those that
prevent users from working at all - if a workaround exists
then it may be worth rescheduling to 2.82. In doubt ask
Dalai Felinto or me.

Best regards,

/Nathan Letwory

[1] https://lists.blender.org/pipermail/bf-committers/2019-November/050285.html
[2] https://developer.blender.org/project/board/88/
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Developer meeting notes November 4, 2019

[Nathan 'jesterKing' Letwory]

Hey all,

Here are the developer meeting notes for Monday, November 4th 2019,
at 10:00 CET / 09:00 UTC in #blender-coders.

The full post is at

https://devtalk.blender.org/t/4-november-2019/10265

Let me know if I missed anything.

Announcements
=

* Embark Studios joins [1] the Blender Foundation Development Fund
  [2] as gold level sponsor.

Blender 2.81


* At beginning of meeting still 15 issues on the bcon3:bugs track
  of the workboard [3] for 2.81. With release coming in closer
  developers are asked to pay attention to it.
* Nathan Letwory aired the idea to maybe bump the release date a
  week, but will be discussing this with Dalai Felinto still and
  write the bf-committers list about it.
* Module owners specifically are asked to check if the current
  items on the bugs track are absolutely necessary for 2.81.
* Philipp Oeser checks if Dynamic Paint issue T62882 can be
  postponed.

Blender 2.82


* With the main focus being on 2.81 release there were no items
  raised during the dev meeting.
New Features and Changes


Blender 2.81


* Keymap: Use Ctrl-F2 for batch rename
  (Campbell Barton).
* UI: Add icon for drawing space key (Campbell Barton).
* UI: Add old hotkeys to set start and end in timeline to the
  Blender 27x keymap (Philipp Oeser).
* UV Editor: Add missing options to proportional editing falloff
  in uv editor (Germano Cavalcante).
* UI: Toggle between play and pause icons in preview rendering
  (Philipp Oeser).
* Cycles: Get OptiX devices (Brecht Van Lommel).
* GPencil: Show selection in Stroke Mode for single points
  (Antonio Vazquez).
* Paint: Option to disable antialiasing (Pablo Dobarro).
* VSE: Show Seconds available in View menu (Campbell Barton).

master
--

* UI: Hovering over UI elements now more consistent and further
  reaching (Harley Acheson).
* Keymap: Maps bundled with Blender can no longer be deleted by
  the user (Sebastion Parborg).
* VSE: Use all selected strips for Select Side operator (Alessio
  Monti di Sopra, Campbell Barton).
* VSE: Set frame range added to Strips operator (Alessio Monti di
  Sopra, Richard Antalik).
* Solidify Modifier: support non-manifold input (Henrik Dick,
  Campbell Barton).

Best Regards,

/Nathan Letwory

[1] https://medium.com/embarkstudios/a-love-letter-to-blender-e54167c22193
[2] https://fund.blender.org
[3] https://developer.blender.org/project/board/88/
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Documentation for manual 2.81

[Nathan 'jesterKing' Letwory]

Hey all,

I'd like to ask all who have worked on new features or
big changes for 2.81 to take some time to ensure these
are properly documented in also the manual. Please have
a look at

https://developer.blender.org/T70624

to see if there is still a need - if you have already managed
your part then I'd be happy if you updated the task accordingly.

If anyone has contributions to any of these sections, or the
manual in general, I'd like to invite you to participate.

Regards,

/Nathan Letwory
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Dev meeting notes, 21 October 2019

[Nathan 'jesterKing' Letwory]

Here are the notes for the (short) meeting of 21 October 2019
10:00 CEST (08:00 UTC).

Blender 2.81


Bugfixing & Documentation
-

* Reminder to focus on bugs listed on the Blender 2.81 workboard
  [1].
  * If current todo list is empty, or not sure what to work on,
please pick something from the workboard list. Confer with
Module Owners if you're unsure about working on a fix for that
module.
* Sebastian Paborg says T66142 [2] might not make it for 2.81 due
  to hacky nature of proposed fix.
* Developers are asked to check their new features or changes for
  Blender 2.81 are properly documented. Apart from the necessary
  documentation for the Blender 2.81 release list [3] also ensure
  user-end documentation is written for the manual. Please confer
  with the documentation team in #docs on blender.chat, or poke
  Nathan Letwory on either blender.chat PM or vial e-mail
  (nat...@blender.org).

Blender 2.82 / master
=

* Not much activity expected due to upcoming Blender Conference.

Announcements
=

* Developers in studio are preparing for Blender Conference this
  week.

See https://devtalk.blender.org/t/21-october-2019/10060 for the
weekly progress reports.

Cheers,

/Nathan Letwory

[1] https://developer.blender.org/project/board/88/
[2] https://developer.blender.org/T66142
[3] https://wiki.blender.org/wiki/Reference/Release_Notes/2.81
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Committing fixes for releases in stabilizing branch.

[Nathan 'jesterKing' Letwory]

On Mon, 14 Oct 2019 at 11:24, Campbell Barton  wrote:
> On Mon, 2019-10-14 at 11:15 +0300, Nathan 'jesterKing' Letwory wrote:
> Some fixed change behavior, were it's disputable weather we would want
> such changes in a release - its not just a question of fix/broken
> state.

If a fix is unclear then this should be addressed indeed. That is what this work
is for.

> Again, there is still no justification for this change.
> Who wanted this? Why?

The motive here is to separate out stabilizing work from the work done
on new features in master. This has been discussed since August.

> Currently the branch fails to merge into master.
> Who is responsible for tracking down & poking people to merge their
> work?

Whoever notices such a case should feel free to notify the author whose
commits fail to merge, failing that poke Brecht, Dalai or me to ensure it
gets handled.

/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Committing fixes for releases in stabilizing branch.

[Nathan 'jesterKing' Letwory]

On Mon, 14 Oct 2019 at 07:37, Campbell Barton  wrote:
> > What kind of backfire are you talking about?
>
> A fix that needs to be removed from the stable branch
> (typically because it causes unforeseen problems).

Naturally the goal is to have fixes that actual fix something. A fix that causes
problems isn't really a proper fix. Reverting sounds like a good
approach there, then
apply a proper fix. But we'll have to deal with such things on a case
by case basis.

/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Committing fixes for releases in stabilizing branch.

[Nathan 'jesterKing' Letwory]

On Mon, 14 Oct 2019 at 03:39, Campbell Barton  wrote:
> - How to handle fixes that are first made to master,
>   and later on we find should be applies to the stable branch
>   (merge? cherry pick?).

To make merging process as clean as possible I would say revert in master,
apply to stable, merge down to master.


> - How to handle fixes that backfire
>   (eg, a fix we make in the stable branch, then cause issues,
>   then we want to remove from the stable branch but keep in master).

What kind of backfire are you talking about?

> - How strict are we on merging immediately after committing
>   to the
> stable branch?
>   So far there has been some accumulation of multiple commits
>   to the stable branch which then get merged.
>
>   Is it discouraged to push multiple fix commits,
>   then a merge afterwards?

Since the assumption is a commit per fix it'd be ideal to merge down to
master once the fix is in stable.

/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Committing fixes for releases in stabilizing branch.

[Nathan 'jesterKing' Letwory]

Hey all,

Soon the stabilizing branches will be created. While not much will
change, but there are a couple of things to keep in mind.

Any bug fix planned for the upcoming release should go to the
corresponding branch (e.g. `blender-v2.81-release`), followed by a
merge to `master`.

Take your time to verify your fixes are correct and the commits look
good (as per usual).

More detailed guidelines can be found on the wiki at:
https://wiki.blender.org/wiki/Process/Using_Stabilizing_Branch

There will be a message to this list once the stabilizing branches
have been created.

Cheers,

/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Developer meeting notes September 23, 2019.

[Nathan 'jesterKing' Letwory]

Meeting notes for developer meeting in #blender-coders on
blender.chat. September 23, 2019. 10:00 CEST (08:00 UTC).

Let me know if anything is missing in either #blender-coders
or on devtalk.blender.org

https://devtalk.blender.org/t/23-september-2019/9635

Road to 2.81


Continued work on improving and stabilizing until October 10th.

* Triaging playbook [1] has been helpful already for some cases.
  Users who want to know how to report bugs can look up the
  process explained in this video [2]
* Rigify has had a rather large rewrite [3], so Alexander Gavrilov
  hopes for intensified testing by users


New Features and Changes


Only smaller changes this week as we shift our focus to polishing
new features and stabilizing. About 90 bugs were fixed last week.

* Eevee and viewport optimization for drawing many objects and
  instances, by batching draw calls. (Clément Foucault)
* File Browser: preference to open in new window or fullscreen,
  and various user interface tweaks. (Julian Eisel)
* Render: the render display choice is now a preference, rather
  than a scene settings. (Julian Eisel)
* Sequencer: new operators to easily create f-curves to fade video
  and auto strips in and out. (Nathan Lovato)
* Sculpting:
  * Pose brush now draws an origin preview. (Pablo Dobarro)
  * Split brush settings for original normal and plane. (Pablo
Dobarro)
  * Icons for the new sculpting tools. (William Reynish)
* Python API:
  * New `Quaternion.toswingtwist` to decompose a rotation into
swing and twist components. (Alexander Gavrilov)
  * New `ImBuf.filepath` to access the file path of an image
buffer. (Colin Basnett)


Projects under development
==

Current timeline for 2.82 can be viewed on the milestone project
page [4]

* Mantaflow is being worked on with 2.82 in mind (Sebastián
  Barschkis, Bastien Montagne)
* Pablo Dobarro wants an initial design for multilayer/channel
  painting. He will create a design task for that

/Nathan

[1] https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook
[2] https://www.youtube.com/watch?v=JTD0OJq_rF4
[3] https://wiki.blender.org/wiki/Reference/Release_Notes/2.81/Add-ons#Rigify
[4] https://developer.blender.org/project/view/89/
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] BF coordination meeting 2019.09.02 notes

[Nathan 'jesterKing' Letwory]

On Tue, 17 Sep 2019 at 13:28, Sybren A. Stüvel  wrote:
>
> On 02-09-19 21:40, Nathan 'jesterKing' Letwory wrote:
> > * Feedback handling of bi-weekly meeting.
>
> 'bi-weekly' is an ambigious term [1]. Shall we use 'twice-a-week' or
> 'fortnightly' instead?

I've always understood it as once every two weeks, but I'm fine
with fortnightly. Probably up to Dalai, since it is his project :)

/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender developer meeting notes - 2019.09.02

[Nathan 'jesterKing' Letwory]

Notes for developer meeting 9 September 2019. Let me know
if anything is missing.

ANNOUNCEMENTS

* Buildbot now supports building arbitrary branches. Developers
  can use this to test their branch builds and passes tests on all
  platforms, and to make the branch available to users for testing.
  docs [1] (Brecht Van Lommel)

NEW FEATURES AND CHANGES

* Eevee
  Soft shadows were redesigned and are now enabled with the
  "Use Soft Shadow" option in the render properties Shadow
  panel. This will progressively smooth shadows, in combination
  with a more conventional shadow filtering method (PCF). Exponential
  and Variance Shadow Mapping methods were removed.
  details [2] (Clément Foucault)

  This improves shadow accuracy, makes light and shadow setup
  simpler, and improves performance for soft shadows.

  Bump mapping was changed to give more accurate results closer to
  Cycles. In particular it makes bump mapping with procedural textures
  work much better than before, at the cost of some performance.

* Cycles
  Reduced shadow terminator artifacts for bump mapping with diffuse
  BSDFs. (Lukas Stockner, Stefan Werner)

* Shaders
  New shader nodes for Cycles & Eevee. (Omar Ahmad)
  * Noise Texture node: support 1D, 2D, and 4D noise.
  * Mapping node: location, rotation and scale are now node inputs that
can be linked to other nodes.

* Viewport
  Viewport shading changes to support look development with
  Cycles. (Jeroen Bakker)
  * Rendered mode now has option to use HDRI studio lights instead of
scene lights and world, for both Cycles and Eevee. This mode can
now be used for look development.
  * LookDev mode was renamed to Material Preview. This mode will be
aimed at interactive texturing and fast preview with Eevee.
  * HDRI studio light strength can now be controlled in the shading popover.

* File Browser
  The file Browser was redesigned. details [3] (Julian Eisel, Brian
Meisenheimer,
  William Reynish, Harley Acheson, Andrzej Ambroz)
  * File Browser as floating window with more standard layout
  * Popovers for view and filter options
  * Importer/exporter options in panels in the sidebar
  * Vertical list view with interactive column header
  * New and updated icons
  * More consistent and powerful mouse and keyboard shortcuts, including
range select with shift click and extend select with ctrl click.

* Rigging
  * Armatures: bone inherit scale options. details [4] (Alexander Gavrilov)
* Full: inherit all effects of scale, like with enabled Inherit Scale.
* Fix Shear: removes shear from the final inherited transformation.
* Average: inherit uniform scale that represents the parent volume.
* None: completely remove scale and shear.
* None (Legacy): previous behavior for backwards compatibility.
  * Constraints: better mixing modes for Copy Rotation and
Copy Transform (Alexander Gavrilov)
* Replace: Replace the original transformation with copied
* Add: Add euler component values together
* Before Original: Apply copied transformation before original, as if the
  constraint target is a parent
* After Original: Apply copied transformation after original, as if the
  constraint target is a child
  * Drivers: support decomposing rotation into swing followed by twist.
details [5] (_Alexander Gavrilov_)
  * Python API: constraints can now be reordered with `move()` on objects
and bones. (Alexander Gavrilov)

* Other
  * Image objects option to only show in side views (Campbell Barton)
  * Grease Pencil (Antonio Vazquez, Charlie Jolly)
* Convert to strokes support for poly curves
* Viewport option to fade unselected objects.
* Improved guides display, with new Isometric option
  * User Interface
* Dimension is now available in the object properties. (William Reynish)
* Select tool was renamed to Tweak tool. (William Reynish)
* Paint mode shortcuts: D for draw brush, B for blur brush.
(William Reynish_)
* Viewport navigation buttons are now positioned vertically.
  * Batch rename now supports regular expression groups. (Jun Mizutani,
Campbell Barton)

## Projects Under Development
* (2.81) GPencil patches up for review still D5688 [6], D5707 [7] (Antonioya,
  Brecht Van Lommel)
* (2.81) potential UV patches (Sebastian Parborg, Phil Gosh,
  Brecht Van Lommel)
* (2.81) potential DNA defaults patch - D4500 [8] (Campbell Barton,
  Brecht Van Lommel)
* add-ons
  * Clean-up of add-ons repository: T63750 [9] (Brendon Murphy)
  * X3D IO moved to community support, no longer maintained by
core team
  * in short: no maintainer = no entry.
  * Speak up if there is an issue for you with this, see previous
bullet item
* T60094 [10] fix and review (_Brecht Van Lommel, Sergey Sharybin_)

NEXT MEETING

Next meeting Next online meeting is on Monday, 16 September
18:00 CEST / 16:00 UTC. It will be on #blender-coders on blender.chat [11]

Cheers,

/Nathan Letwory

WEEKLY PROGRESS REPORTS
* Bastien 

[Bf-committers] BF coordination meeting 2019.09.02 notes

[Nathan 'jesterKing' Letwory]

Hi all,

Here short notes from the development coordination
meeting held on 2nd of September, 2019.

Quick overview of week work:

Nathan

* Phabricator patch D5656
* CI investigaton (Jenkins vs Buildbo) - best to continue
with buildbot, since we have know-how for that already

Brecht

Lots of patch reviews, work continuing.
* Cycles
* UDIM
* Sculpting branch patches

Dalai

* Feedback handling of bi-weekly meeting. Most happy,
  some questioned the use. Figure out how well can scale.
  Write text as proposal, i.e. keep open for participation.
* Grease pencil meeting / project datablock, proposal to come
  from Grease pencil team

Topics

* Release cycle / agenda more public and prominent (visible to
  users, not only developers). Pablo and Francesco were also
  thinking about that, to be worked together.
* BCons description need to better reflect our current cycle (we
  downsized our 5 bcon cycle to a 3 cycle, but need more work).
* Mentorship program started:
  + https://developer.blender.org/T69399
  + https://developer.blender.org/T69403

Follow ups

* Ask Sergey to review Phabricator patch [Nathan]
* Reply to infrastructure internal email about
  buildbot and BlenderID + Phabricator) [Nathan]
* Update Bcon page [Brecht]
* Book the next round of biweekly [Dalai]
* Review OpenXR GSoC [Dalai (1st pass) + Sergey/Brecht]
* Status of remaining GSoC [Dalai]

/Nathan

p.s. I hope the formatting is better than previous mail that
  was sent through Android app (don't do that anymore).
p.s2 Some things have already been handled and changed,
  like the bcon descriptions on the release cycle page at
  https://wiki.blender.org/wiki/Process/Release_Cycle increased
  back to 4 from 3.
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Developer meeting notes - 2019.08.26

[Nathan 'jesterKing' Letwory]

Hi all,

Here are the notes for the developer meeting of 26 August 2019. With
questions please ask either on the mailing-list bf-committers, in
#blender-coders on blender.chat or directly at nat...@blender.org .

The next meeting is 2 September 2019 in #blender-coders on blender.chat
at 18:00 CEST (16:00 UTC).

Announcements
---

* Release date for 2.81 is currently set to 14 November 2019
  * Cut-off date (major changes and features in by) 13 September 2019
  * Stabilizing branch creation 1 October 2019
* master branch will be open from then on, i.o.w. no freeze while 2.81
  is being stabilized

Projects
---
* Quadriflow integration, cloth patches (Sebastian Paborg)
* Cycles patch review continued (Brecht Van Lommel)

New Features and Changes
---

* Transform: new snapping options to snap to the center of edges,
  and perpendicular to edges. (Germano Cavalcante)
* Transform: new option to transform object origins in object mode,
  found in the pivot popover. (Campbell Barton)
* Viewport: side views now show the grid units again in the top
  left corner. (Germano Cavalcante)
* Outliner: range select with shift+click now also supports extending
  the selection with ctrl+shift+click. (Nathan Craddock)
* Grease Pencil: improved reproject operator, that does not suffer from
  stairstepping artifacts. (Lukas W, Antonio Vazquez)
* New shaders for Cycles and Eevee. (Omar Ahmad)
  * Volume Info node, for convenient access to Color, Density, Flame,
and Temperature attributes of smoke domains.
  * White Noise node, producing a random number based on input values.
  * Vector Math node: new operations, and show number of inputs depending
on the operation.
  * Object Info node now has the object color.
* User Interface: improved layout and text for save/close dialog. (Harley
Acheson, Yevgeny Makarov)
* Python API: support for displaying node sockets with square and
  diamond shapes, using the new `NodeSocket.display_shape` property.
  (Charlie Jolly)

Other Projects
-

* Workflow improvement patches started by Brecht (Nathan Letwory)

Weekly reports
--

For the links to the weekly reports please refer to the devtalk
meeting notes for this meeting at
https://devtalk.blender.org/t/26-august-2019/9051

A phenomenal week to everybody!

/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender developers meeting notes - 2019-08-19

[Nathan 'jesterKing' Letwory]

On Mon, 19 Aug 2019 at 20:48, Dalai Felinto  wrote:
> * 2.81 release dates and new branch system proposed on bf-committers
> [1] (Nathan Letwory)
>   * Meeting agrees on waiting a few more days for feedback before a
> firm decision.

When will this final decision be made? Wednesday? Thursday? Any specific
issue that needs to be cleared up?

/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] BF coordination meeting notes - 2019.08.19

[Nathan 'jesterKing' Letwory]

Hi all,


Here are the notes for our private weekly meeting concerning

the development coordination.


If you have any topics to discuss for next meeting please

be in touch with me or Dalai via mail or on blender.chat


Participants: Brecht Van Lommel, Dalai Felinto, Nathan Letwory

August 19th, 2019.


Topics

--


* Onboarding

   + regular devs should try to give possibility to update proposed patch

   + devs can contact Nathan if they don’t have time to manage closely

  patch review process for code by new devs (i.e. may require lots

  of going back and forth between contributor and dev)

   + tricky to find a good balance between guiding and being able to

  do own work


Phabricator "project" for coordination projects

-

* Added to "Platforms, Builds & Tests" - T66306


Priorities for development infrastructure



* Improve Phabricator ( see i.e. https://developer.blender.org/D5521 )

   (Nathan)

* Check with Campbell (and later with Sergey - bottleneckers) on what

   is taking their time away

* Buildbot management

   + Automate release builds and codesign

   + Automate run tests


Development priority

-


* Dalai & Brecht go over Modules to check

   roadmaps & priorities

* Dalai email bf-committers to remind people

   to work in tracker


Phabricator projects




* workboard support should list subprojects (Nathan)


Brecht's time

-


* things are going in the right direction, but takes time to free

   up even more


Bi-weekly meetings

---


* strict time limit. If issues remain unsolved handle outside meeting

   (or extra meeting if need be)

* start this week, Wednesday and Thursday

* work with external animators: through public channels

* animation module owner Sybren - responsible for organizing

   flesh out animation module page



Nathan’s week

---


* contact with localisation team wrt Weblate

* onboarding / review policy

* Crashpad integration (server-side)


Brecht's week

--


* lots of code review


Dalai's week

---


* code review (among others outliner gsoc branch)

* module/project proposal

* meetings with different devs and users


Follow-up

---


* phabricator improvements (Nathan)

   + D5521

   + workboard subproject listings

   + automate builds and tests for patches

*  modules cleanup/roadmaps (Dalai) - on hold until

   phabricator patching complete


/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Release cycle 2.81: dates and branch proposal

[Nathan 'jesterKing' Letwory]

Hi Brian,

Thank you for your input. The Python API and add-ons were indeed not
specifically mentioned.

In the proposal I glossed over submodules, but the idea is to create
in each submodule corresponding 2.81 branches for stabilizing. That
will also ensure we can keep master and the release branches clearly
separated. That in itself is separate from the Python API issue.

I think it would be good if we could come to a good policy of not breaking
the API between major releases - a bigger timespan than 3 months would
probably be beneficial for the add-on ecosystem, allowing add-on devs to
build longer on a stable platform.

There will always be the possibility of major issues going somehow
unnoticed especially with new API. For that we could be more alert during
(technical) design and patch review when the Python API is touched. Bumping
the Python version can be considered part of the API we provide, so it
indeed
makes sense to take care about the proper planning of that as part of
scheduled breakage.

These are good poings to bring up also during the dev meeting this coming
Monday 2019.09.19 (starting at 16:00 UTC).

Finally the version scheme, I personally think moving to a semver scheme
would be useful for a wide array of installing (on a number of OSes) and
the add-on ecosystem as you noted.

I hadn't thought of that since the summer, but lets see what the consensus
is regarding the version scheme. Having the dot added on the technical/code
side, and keeping the one without the second dot in the common tongue
might be worth considering, if not even completely move to it - currently
no strong opinion on that.

Thanks again,

/Nathan

On Thu, Aug 15, 2019, 16:27 Brian Savery  wrote:

> First of all, Kudos for the 2.80 release, and I think the move to higher
> frequency smaller releases with 2.81 is great.
>
> One thing that I have not seen discussed with this release cycle change is
> the python api and addons.
>
> Currently, as things stand, a user would have to reinstall all addons with
> each new release between 2.80 and 2.81, which is fine with older release
> cadence, but becomes slightly more burdensome with quarterly-ish releases.
>
> Furthermore, what about api compatibility and python compatibility between
> releases?  Has there been a discussion about that?  As an addon developer,
> I feel the 2.80 release was a bit late breaking some apis (especially for
> render engines) and would prefer not to see that repeated with each 2.XX
> release.  Us addon developers would prefer to no have to put out a version
> for each quarterly release if possible (but this might be selfish a bit on
> our part).
>
> This is all further complicated if an addon uses c extensions that need to
> be compiled against a certain python version, and that python version
> changes between Blender versions.  Overall, this might be one more vote
> towards moving to a version scheme like 2.8.1 where api and python version
> is stable across minor versions.
>
> Anyway like I said I haven't seen this point brought up.  If there's a
> discussion somewhere I could contribute to, please point me there!
>
> Brian
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Release cycle 2.81: dates and branch proposal

[Nathan 'jesterKing' Letwory]

Hi all,

it has been brought up already a few times, but this post
is to make it a clear proposal. Any feedback and comments
should be made prior to the next dev meeting of
2019.08.19. That is the day we settle on the final dates and
release process for 2.81.

 START PROPOSAL -

Proposed release date is 2019.11.14

SCHEDULE

* 2019.09.13: CUT-OFF for major work (features, overhauls, etc)
   This means for module owners to reflect on the feasibility
   of big patches to receive ample review and time to address
   potential issues in two months. If you are unsure be in touch
   with Brecht, Dalai or myself.
* 2019.10.01: BRANCH 2.81 for stabilizing.
* 2019.11.14 RELEASE of 2.81.

HANDLING TASKS/BUG REPORTS

In addition to major tasks everyone involved is asked to reflect on
the open tasks and 2.81.

A 2.81 milestone has been created for the BF Blender project.
Anything that should go in 2.81 should be tagged with the milestone.
The idea is that with some regularity all items tagged with the
milestone will be reviewed to see if it fits in the 2.81 targets.

Items may or may not be retagged for a later release depending in
factors as severity and available dev power. Together with the module
owners the amount of work should look achievable. Work can
be added or removed as necessary.

COMMITTING

This includes corresponding branches in submodules to make it
easy to keep all modules in sync. From here on any commits that
fix issues for release should be directly made in the 2.81 branch.
Any work that accidentally gets committed to these branches can
be backed out and instead applied to master.

This may cause some confusion, but shouldn't be a big change to
learn. We'd have 6 weeks time of getting the hang of this, I'm sure
that together we can pull this off.

DOCUMENTATION / TRANSLATION

The writers will have around six weeks time for getting the manual
updated. Webpage content can be also prepared.

The idea of the stabilizing branch is that there _should_ be minimal
changes, barring any important GUI/workflow changing fixes that
simply have to be made to produce a releasable product.

TESTING OF BUILDS

We target to get the buildbot system adjusted to build also from the
stabilizing branch. Feedback on the 2.81 product will be done using
these 2.81 buildbot builds. There won't be separate RC releases.

MASTER

While stabilizing work is conducted in the 2.81 branch master can
stay open for continued work on anything post-2.82. In other words
we won't be locking master after 2019.10.01. Devs that don't get
2.81 items assigned should feel free to continue work.


 END PROPOSAL 

Please provide comments and feedback prior to the upcoming
dev meeting of 2019.08.19. The final schedule will be locked at
that meeting.

Cheers,

/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Release cycle idea

[Nathan 'jesterKing' Letwory]

; want a repeat of this.
>
>  A blender:released-in field is useful information. But it needs to
> solve a problem to be worth the bookkeeping overhead, and it's not
> clear to me what that problem is. Auto-generating bugfix lists from
> this can be convenient, but it also requires discipline to tag
> everything correctly and retitle bug reports, whereas "git log" is a
> list that is automatically complete. Triaging bugs and keeping tasks
> on developer.blender.org up to date is a lot of work already. We have
> to be careful when adding even more things to maintain there.
>
>
>
>
>
>
>
>
> On Mon, Aug 12, 2019 at 12:35 AM Nathan 'jesterKing' Letwory
>  wrote:
> >
> > Hi,
> >
> > I've typed my thoughts on the release cycle over at
> >
> > https://wiki.blender.org/wiki/User:JesterKing/ReleaseCycleNotes
> >
> > (also contains a pretty picture) but here in short the high-lights:
> >
> > * if we go for a release just with Blender Conference (24th of October)
> > * we could do a three week stabilizing:
> >   RC dates could be
> >   - 30th September (cut-off date - 2.81 stabilizing branch created, RC1)
> >   - 7th (RC2), 14th (RC3), 21th (RC4) October
> >   - After RC4 there should be no show-stoppers, meaning the RC4
> > could be rereleased as official 2.81 (proper tagging in repos)
> > * blender:release-target custom field for Maniphests in use during
> >week 33
> > * weeks 33-39 (2019.08.12-2019.09.29) time to work on new stuff
> >and improving existing
> >
> > After 2.81 (Blender Conference) we could settle into 3-month cycle
> > that would allow for targetting releases around SIGGRAPH and
> > Blender Conference.
> >
> > Nothing has been set in stone regarding dates, but this week I want
> > to implement at least the basic custom field for maniphests. There
> > should be no changes to how we all type code in the coming weeks.
> >
> > Have a good week!
> >
> > /Nathan
> > ___
> > Bf-committers mailing list
> > Bf-committers@blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Developer meeting notes - 2019.08.12

[Nathan 'jesterKing' Letwory]

Hi,

Here are the dev meeting notes. Meeting was held at 08:00 UTC in
#blender-coders on blender.chat.

The next meeting is 2019.08.19 at 16:00 UTC in #blender-coders
on blender.chat.

# Announcements

* Ryan Inch added as add-on developer to maintain
   sculpt/paint brush menus.

# New Features and Changes

* Grease Pencil: new modes for the Simplify modifier. Merge merges
  all vertices below a given distance, and Sample resamples the stroke
  with a specified distance between sample points. Resampling is
  also available as an operator.  (Antonio Vazquez, Yiming Wu)
* Menus and panels layout and organization improvements in the text,
  console, info and sequencer editors, as well as sculpt and grease
  pencil modes. (Campbell Barton, William Reynish, Peter Fog,
  Matias Mendiola)
* Nodes: display vector socket values expanded. (Omar Ahmad)

# Projects

* Constrained Delaunay Triangulation routines were added, to be used
  later for improved booleans. (Howard Trickey)
* Release cycle (Nathan Letwory)
* Revive air pressure patch for cloth(Sebastian Parborg)
* Discuss with 2016 UV Tools dev about getting packing code
  in 2.80 (_Sebastian Parborg_)

# GSoC
* Outliner ready for final review and landing in master
* LANPR is going to be prepared for review as well

# Weekly progress reports

Please see the list at the devtalk link

https://devtalk.blender.org/t/12-august-2019/8747

/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Release cycle idea

[Nathan 'jesterKing' Letwory]

Hi,

I've typed my thoughts on the release cycle over at

https://wiki.blender.org/wiki/User:JesterKing/ReleaseCycleNotes

(also contains a pretty picture) but here in short the high-lights:

* if we go for a release just with Blender Conference (24th of October)
* we could do a three week stabilizing:
  RC dates could be
  - 30th September (cut-off date - 2.81 stabilizing branch created, RC1)
  - 7th (RC2), 14th (RC3), 21th (RC4) October
  - After RC4 there should be no show-stoppers, meaning the RC4
could be rereleased as official 2.81 (proper tagging in repos)
* blender:release-target custom field for Maniphests in use during
   week 33
* weeks 33-39 (2019.08.12-2019.09.29) time to work on new stuff
   and improving existing

After 2.81 (Blender Conference) we could settle into 3-month cycle
that would allow for targetting releases around SIGGRAPH and
Blender Conference.

Nothing has been set in stone regarding dates, but this week I want
to implement at least the basic custom field for maniphests. There
should be no changes to how we all type code in the coming weeks.

Have a good week!

/Nathan
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers