GitHub Repositories
12 views
Skip to first unread message
Dominic König
Mar 7, 2025, 4:12:19 AMMar 7
to Eden ASP
Hello everyone--
there has been some confusion about which GitHub repository to use.
There are currently two GitHub repositories for Eden ASP.
This one:
https://github.com/sahana/eden-asp
...is the "stable", where I publish occasional snapshot releases. Those
releases will have release notes (change log), and will go through some
testing before publishing, and may contain advice how to upgrade/migrate from
a previous version.
It contains several branches:
"master" - is the latest release (currently 5.6)
"v4" - is the latest version of the 4.* series
"v5" - is the latest version of the 5.* series
"dev" - is the latest version of the upcoming (as-yet unpublished) release
This repository is maintenance-only, i.e. I will accept bug fixes and backports
for the *current* version of Eden ASP, or the latest release of *previous*
series respectively (i.e. master branch, or v4), but not new feature sets,
experimental code or breaking changes.
It is also possible to file bug reports there, as far as they concern a release
branch (i.e. not for the "dev" branch) - in order to get support for them.
---
This repository:
https://github.com/nursix/eden-asp
...is currently the main focus of development (i.e. trunk), and publishes
ongoing changes and developments as they happen, including untested,
incomplete and experimental code. This is the place to send pull requests for
*future* versions of Eden ASP.
This is also the place to report and investigate issues and discuss feature
proposals with regard to the current development version (i.e. not for
releases, those should be posted to sahana/eden).
---
Meaning:
If you are working on a deployment and require a stable version as basis for
your application template, then sahana/eden is the right place.
However, if you want to contribute to the project, collaborate on new
features, or work the latest code - then you would work with nursix/eden.
As for issues, there is some overlap between the two - but the rule of the
thumb is that you should report issues to the repo you cloned.
---
Hope this clarifies matters.
Dominic
there has been some confusion about which GitHub repository to use.
There are currently two GitHub repositories for Eden ASP.
This one:
https://github.com/sahana/eden-asp
...is the "stable", where I publish occasional snapshot releases. Those
releases will have release notes (change log), and will go through some
testing before publishing, and may contain advice how to upgrade/migrate from
a previous version.
It contains several branches:
"master" - is the latest release (currently 5.6)
"v4" - is the latest version of the 4.* series
"v5" - is the latest version of the 5.* series
"dev" - is the latest version of the upcoming (as-yet unpublished) release
This repository is maintenance-only, i.e. I will accept bug fixes and backports
for the *current* version of Eden ASP, or the latest release of *previous*
series respectively (i.e. master branch, or v4), but not new feature sets,
experimental code or breaking changes.
It is also possible to file bug reports there, as far as they concern a release
branch (i.e. not for the "dev" branch) - in order to get support for them.
---
This repository:
https://github.com/nursix/eden-asp
...is currently the main focus of development (i.e. trunk), and publishes
ongoing changes and developments as they happen, including untested,
incomplete and experimental code. This is the place to send pull requests for
*future* versions of Eden ASP.
This is also the place to report and investigate issues and discuss feature
proposals with regard to the current development version (i.e. not for
releases, those should be posted to sahana/eden).
---
Meaning:
If you are working on a deployment and require a stable version as basis for
your application template, then sahana/eden is the right place.
However, if you want to contribute to the project, collaborate on new
features, or work the latest code - then you would work with nursix/eden.
As for issues, there is some overlap between the two - but the rule of the
thumb is that you should report issues to the repo you cloned.
---
Hope this clarifies matters.
Dominic
Reply all
Reply to author
Forward
0 new messages