Distinction between Assembly3 vs. 'Link branch' tickets

[luzpaz]

The reason i ask is that there a several things going on:

• There are 2 repos: https://github.com/realthunder/FreeCAD/issues (Link branch) and https://github.com/realthunder/FreeCAD_assembly3 (A3)
• A3 is now in the Addon Manager
• There are open tickets and PRs in https://github.com/realthunder/FreeCAD (for both A3 and Link)
• There are open tickets and PRs in https://github.com/realthunder/FreeCAD_assembly3 (for both A3 and Link)

I think a repo admin has the ability to move tickets between repos (if they have admin privs in each).

Edit: realthunder has given me privileges to move tickets between the 2 repos. Any assistance to identify preexisting or newly posted ticket in either repos by the community is appreciated

[bambukouk]

Great idea 👍
Most of the people (especially on main forum) seem to be confused and equate Assembly 3 with Link branch (wrong 👎 )

It is not helped by refusal of forum mods to create Link branch sub-forum and insisting on dumping anything remotely related to link branch into Assembly sub-forum.

Link branch is released in FreeCAD_assembly3 and not in FreeCAD link branch

Most of us who have been around for a while manage OK, but to anybody coming fresh to it, it must be confusing...?

[luzpaz]

Yea.. I know it was a necessity to do it like this initially for @realthunder...but we're entering a new era and it may be useful to make a distinction. If people want to open tickets we can make a ticket template that explains this distinction and orient the users what repo to post in for either A3 or Link branch. Thoughts?

[bambukouk]

It is indeed useful to make distinction, but...
Ticket template it's a bit like "about FreeCAD" info requested to be included in every help question 👎
It has about 20% success rate
Regardless how big a font and how red it is, most of the people will ignore it ...

The only 100% solution is vetting and filtering by some moderator?
this is just my opinion (yes, I know everybody has an opinion on interweb..)

[luzpaz]

@bambukouk it works a lot of the time in FreeCAD/FreeCAD so I'd say it's worth a shot. Train you userbase and they will eventually self-organize.

[bambukouk]

Bottom line is - I totally agree with you about the need for distinction.
Let's get on with it and we can sort out details later 👍

[luzpaz]

No we just need to wait for the boss to weigh in 😉

[luzpaz]

@realthunder ping

[realthunder]

I just tried transferring one of my own issue. It works find, but I didn't get any email notification. Looks like we need manually notified the author?

[realthunder]

@luzpaz Do you have permission to move issue between this and FreeCAD Link branch?

[luzpaz]

Will start doing this in the next few days 😉

[YosypC]

I've been wondering why there was a Linkstage3 AND an assembly3, AND why people often submit LS3 issues in the assembly3 Issue page, AND Linkstage3 releases are pushed in this GitHub instead of the LS3's.
I've followed the mass and began posting here too, but I guess it needs to change. Very confusing for newcomers.

[luzpaz]

In progress

[kevenwyld]

Link branch is released in FreeCAD_assembly3 and not in FreeCAD link branch

In my opinion this is the root of most of the confusion. Link branch installer/packages are released here in this repo and not realthunder/FreeCAD . Is there a plan to change that? Or is that even possible to change?

A3 is now in the Addon Manager

While this is true, the link branch appimage seems to still be bundled with it. So thinkgs are quite mixed together between these two repos and should probably be untangled further than just moving issues over. In fact moving the issues away from the releases might make things even more confusing in the interim.

Also is the A3 addon the same as the one bundled with the link branch or is it lagging behind because it is built separately?

[luzpaz]

Indeed. We're slowly teasing apart the issue. There are so many posts/link/social-media mentions that point to A3 release page for Link branch builds. But it's realthunder's call in the end.

[ceremcem]

@luzpaz I didn't wery well understand the desired workflow. Are you suggesting we should open Assembly3_WB related issues here and LinkStage3 (FreeCAD itself) issues in the realthunder/FreeCAD repo?

If that's the case, I see a slight problem here. A single bug might be related both with LinkStage3 and Assembly3_WB or even with another WB (like SheetMetal, remember realthunder's commit to SheetMetal for that WB to work with LinkStage3); it would be hard to determine where to open the issue.

I think we should have opened every issue in Assembly3_WB issue tracker, no matter what it is related to.

[luzpaz]

The point is to start disentangling A3 from Link branch since A3 can run independently from Addon Manager in master. So yes, it's a bit messy but it's a start

[bob-u]

What's confusing to me is this:

Do Link branch releases have all Assembly 3 patches? Or, if I wanted to use the most up-to-date branch, which one should I choose?

Regarding the topic, for the new comer like me (someone who have not used FreeCAD for a while) is that Link branch is called FreeCAD.