Associate releases about poggit HOT 12 CLOSED

Yep for only associating own plugins.
Parent plugin + children plugins = one package. It doesn't make sense to add your plugin into others' package, or to have multiple "main" plugins in the same package.

from poggit.

Should be replaced by a Plugin Lists mechanism

from poggit.

I can't see much difference between an "optional dependency", whatever that is exactly... and an "associate release", except that maybe the latter would be reserved for plugins from the same author. So do we need a separate section for this, or could we add a third category such as "Associated Plugin" to Required/Optional?

from poggit.

Associated releases are actually packages of plugins. Dependencies are just "You can use them together" "It's an add-on", but association is stronger -- "You SHOULD use them together". Therefore there should be a zip download for associated projects while this is not needed for normal dependencies.

from poggit.

In simple words, "Foo depends on Bar" vs "Foo is an associate of Bar":

from poggit.

Got it :-)

from poggit.

"Foo is not listed in /pi. Only Bar is listed in /pi"
How do you suggest we manage an associated Foo's release status? It should presumably be >=approved to qualify as an associated plugin, and yet we don't want it in /pi; a new 'parent_releaseId' column in releases?

from poggit.

Yeah, that's a good way.

from poggit.

Do we allow multiple parents? I've started with only one... and I'm assuming users can only associate their own plugins.

from poggit.

Yet. Also, a parent release must not be the child of another.

from poggit.

Yep*

from poggit.

Was that a 'yep' for multiple parents too? I'm hoping not...

from poggit.