You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Soon I will finish my work on rivus (as far as my thesis goes), and still have a lot of pending PRs, I summarized the properties of them hoping to ease the process/decision of acceptance/merging. @KSchoenleber
Fast ToDo:
Add labels like in urbs, so that Issues and PRs can be labelled. This would ease the sorting and handling of those. [urbs-labels]
Adding documentation/discussion labels where needed.
maintenance, bug, etc...
Define version milestones. (Now 0.1, which is the original. Alone BUGFIX for line_length() #13 should mean a version upgrade.) (See doc)
Pull Requests
As I restructured the project at the beginning, and that was already merged, the PRs mostly consist of self-maintained contributions. However, broader developments can rely on changes now pending in earlier pull-requests.
Soon I will finish my work on rivus (as far as my thesis goes), and still have a lot of pending PRs, I summarized the properties of them hoping to ease the process/decision of acceptance/merging.
@KSchoenleber
Fast ToDo:
Pull Requests
As I restructured the project at the beginning, and that was already merged, the PRs mostly consist of self-maintained contributions. However, broader developments can rely on changes now pending in earlier pull-requests.
Sub Packages
#self-contained
Core Changes
#maybe-self-contained
Merge conflicts can arise, as these operate on the same file. But in different places, so should be ok, or solvable with minimal time investment.
Broad Changes
#relying-on-others
The text was updated successfully, but these errors were encountered: