Release notes for v0.19

[Kunda1]

Taking such initiative is definitely much better, compared to just proposing automation.

There is probably a solution somewhere in the space between a simple RSS feed of the FreeCAD/FreeCAD commits being logged somewhere and full on machine learning AI cherrypicking commits worth mentioning. The idea to propose is it to get a conversation going and I don't consider that not taking initiative either. (Sorry, don't mean to sound snarky, just clarifying my position)

[triplus]

If we just focus on upstream commits the number (0.19_pre) currently is:

Code: Select all

260 commits to master since this release

And there are external modules, forums discussions, issue tracker ... Automation is therefore more suitable for Start page -> Activity purposes and things like that. Release notes on the other hand require more people oriented effort invested. Once somebody emerges and offers to produce a release video. Maybe at some point automation could start to make sense. That is on how to add an entry from Release notes to a Release video in a seamless way. But still, likely in foreseeable future people will do that and not AI.

[Joel_graff]

Added the bezier curve tool and Yorik's 3-point arc tool. Could use an image for the 3-piont arc tool. I added a placeholder for the time being until it shows up in one of my FreeCAD builds or something.

[NormandC]

Just a small comment about the Release notes page, the Additional Modules section should only list addons that are/have been actively developed during the 0.19 cycle. I know it's still early and the situation will evolve, but:

cadquery --> last commit December 29
Defeaturing wb --> last commit October 2018
Curves --> last commit March 7 (a few days before the 0.18 release)
Silk --> last commit Feb 2018 (full month before start of 0.19 development)
SQL --> ...

[easyw-fc]

Just a small comment about the Release notes page, the Additional Modules section should only list addons that are/have been actively developed during the 0.19 cycle. I know it's still early and the situation will evolve, but:

cadquery --> last commit December 29
Defeaturing wb --> last commit October 2018
Curves --> last commit March 7 (a few days before the 0.18 release)
Silk --> last commit Feb 2018 (full month before start of 0.19 development)
SQL --> ...

I think the Release notes page should mention WB that are full functional...
I don't see why we should remove i.e. Defeaturing WB only because its last commit was in October 2018, when this WB is still full functional even in Py3/Qt5 flavour.

[Joel_graff]

Just a small comment about the Release notes page, the Additional Modules section should only list addons that are/have been actively developed during the 0.19 cycle

I see the point. Still I'm reluctant to exclude a community workbench for a lack of development within a single release cycle, especially if the workbench is new - it's a bit of exposure for them. As it is, this isn't a decision I'd care to make until 0.19 is released - and maybe it can be done all at once with a preliminary discussion here?

It's also a simple matter to do it - I can easily comment out the code without actually removing it if it seems like it's just on hiatus and not abandoned. I suggest we also do the same for the core workbenches, too.

Which brings me to another thought: A master list of community workbenches (active or otherwise) might not be a terrible idea, either. If only because it serves as a record of what has come and gone for a future developer who might want to know if what they have in mind has already been done.

[NormandC]

FreeCAD's StartPage has a list of available external workbenches.

Release notes are about what's new, not about what's working.

Cadquery has existed for years.

The wiki already has a list too. External Workbenches

[Joel_graff]

The wiki already has a list too. External Workbenches

Yikes. Looks like that needs updating, too.

[easyw-fc]

FreeCAD's StartPage has a list of available external workbenches.

Release notes are about what's new, not about what's working.

Defeaturing WB is quite new and depends on OCC 7.3 which are also quite new ...

[Jee-Bee]

Defeaturing WB is quite new and depends on OCC 7.3 which are also quite new ...

but it cames during 0.18 cycle so it should be in 0.18 release notes.