[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

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

[Harald Reingruber via Bf-committers]

 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] Proposal of a 2.82b release (for bug fixing)

[mano-wii via Bf-committers]

After the release of 2.82, I came across some crash reports.
And with each new fix the idea of a new release sounded even more important.
For example, from my side I fixed these crashes:
* Fixed T74969: Crash in gpencil edit mode (1f949121cd3f 
(http://developer.blender.org/rB1f949121cd3f))
* Fixed T74876: Crash when snapping to faces (efdc93fcc692 
(http://developer.blender.org/rBefdc93fcc692))
And there were also these other fixes:
* Fixed T74604: A.N.T Landscape Erode function reports error 
(10bd3fb4cb18 (http://developer.blender.org/rB10bd3fb4cb18))

* Fixed missing text input on Windows with certain keyboard layouts 
(1b1c683f7479 (http://developer.blender.org/rB1b1c683f7479))
* Fixed possible endless loop in Auto Merge & Split (765c82e92d67 
(http://developer.blender.org/rB765c82e92d67))
* Fixed T70126: Can't snap between objects with Rigid Body 
(3be7d74cba7f (http://developer.blender.org/rB3be7d74cba7f))
Since the release of blender 2.83 is scheduled for May 20, it seems fair to 
make a new release for bug fixing.
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender developer meeting notes - 2020.3.30

[Dalai Felinto via Bf-committers]

Hi all,

Here are the notes from today's developer meeting. Next meeting is
Monday, 4 April 11:00 CEST / 9:00 UTC, in #blender-coders on
blender.chat.

For the complete report read it on:
https://devtalk.blender.org/t/30-march-2020/12349

Announcements
=
* Google Summer of Code students deadline is March 31st, don’t miss
the deadline.
* blender.chat server will be updated Monday (march 30th) night.

Communication

* Dalai Felinto suggests “threaded discussions” to be brought back to
blender.chat with the update. It helps 1:1 discussions to happen in
the public open channels.
* Also he will try to post on #blender-coders 14 more often the
outcome of the talk with the other developers (e.g., a compilation of
the daily report of activity by the developers).
* As a rule of thumb all the developers are heavily encouraged to use
the open channels as much as possible (as oppose to private messages).

Other

* Germano Calvalcante insists a 2.82b release would be beneficial. He
will post on bf-committers about that.

Thank you,
-Dalai-

Dalai Felinto - da...@blender.org - www.blender.org
Blender Development Coordinator
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Upgrading wiki software

[Danny McGrath via Bf-committers]

Hi,

The upgrade should be done and appears to be working. Let me know if
anything unusual happens.

Thanks!

On Mon, Mar 30, 2020 at 10:35 AM Danny McGrath  wrote:

> Hi,
>
> Just a heads up that I will be attempting to do a minor upgrade of the
> Wiki shortly. I need to clean up a few other things first, but when I start
> the downtime should hopefully be short.
>
>
> --
> Cheers,
> Danny
>
> -
> Danny McGrath - d...@blender.org - www.blender.org
> System Administrator at Blender
> GPG key: 0x696871CA
>


-- 
Cheers,
Danny

-
Danny McGrath - d...@blender.org - www.blender.org
System Administrator at Blender
GPG key: 0x696871CA
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Upgrading wiki software

[Danny McGrath via Bf-committers]

Hi,

Just a heads up that I will be attempting to do a minor upgrade of the Wiki
shortly. I need to clean up a few other things first, but when I start the
downtime should hopefully be short.


-- 
Cheers,
Danny

-
Danny McGrath - d...@blender.org - www.blender.org
System Administrator at Blender
GPG key: 0x696871CA
___
Bf-committers mailing list
Bf-committers@blender.org
https://lists.blender.org/mailman/listinfo/bf-committers