search

nim-lang / fusion

Fusion is for now an idea about how to grow Nim's ecosystem without the pain points of more traditional approaches.
MIT License
128 stars 16 forks source link

Releases #1

Closed wltsmrz closed 4 years ago

wltsmrz commented 4 years ago

Do you have an idea about how fusion releases will work, if it's composed of many submodules that are updated independently? I'm guessing the submodules are independently versioned and that "fusion" is a nimble-installable module.

ksandvik commented 4 years ago

Will this also imply that all the modules are downloaded and updated instead of piece-meal?

Araq commented 4 years ago

There are no git submodules, there is only code that works well with Nim 1.0 and upcoming releases.

wltsmrz commented 4 years ago

I was just wondering, if fusion is ultimately the embodiment of the nim distribution idea, how/when each component module is updated. Maybe it would help to do a series of questions:

(1) Will fusion be an independently-installable nim module? (actually I think the readme answers this in the affirmative) (2) Will fusion be shipped with nim by default, or a special release of nim e.g. nim-v1.3-fusion.tgz? (3) Will fusion contain third party modules that are tested against v1.0 through v1.n? (4) When third party module releases new version, at what point do consumers of fusion receive update?

Araq commented 4 years ago

(1) Yes. (2) Shipped by default. (3) No, if you want something to be in fusion, you must create PRs against this repo with source code. The idea is to create a collaborative environment, we all ensure the code keeps compiling and is well documented, but development is a community effort. (4) Not applicable.

Fusion is not the "Nim distribution" idea, it's trimmed down to what we think is maintainable for our current team. Of course, the team can grow or shrink, but we manage it just like Nim's stdlib.

wltsmrz commented 4 years ago

Aha, thanks for clarifying