Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Next steps on the road to version 0.10.x #259

Closed
14 of 17 tasks
Shinigami92 opened this issue Aug 23, 2018 · 3 comments
Closed
14 of 17 tasks

Next steps on the road to version 0.10.x #259

Shinigami92 opened this issue Aug 23, 2018 · 3 comments
Labels
bot:stale Issue marked as stale because there was no activity

Comments

@Shinigami92
Copy link
Contributor

Shinigami92 commented Aug 23, 2018 •
edited
Loading

This is not a feature or bug issue

I'd like to suggest / list some TODOs and changes before we can provide a new tag

I think the next version should be 0.10.0 instead of 1.0.0 because we do not want to make any changes for a release but for a new clean, automated, and improved project.

Pull Request

CleanUp and Improvements

After making all these changes, we can set the version to 0.10.0, tag it and maybe release it.

Then we should focus on implementing and bringing together the current open pull requests that are waiting the last 1-3 years ^^
And from then on, we can increment the version from 0.10.0 to 0.10.1+ or 0.11.x+
thedaviddias pushed a commit that referenced this issue Aug 27, 2018
@thedaviddias
docs: package author and contributors (#270)
14fd3aa 
**Partially fixes**: #259 

- [x] Check the commit's or even all commits' message styles matches our requested structure.
- [x] Check your code additions will fail neither code linting checks nor unit test.

#### Short description of what this resolves:

Give the main contributor some credits

#### Proposed changes:

- Added main contributors to the package.json

👍 Thank you!
@olore olore mentioned this issue Sep 3, 2018
Merged
thedaviddias pushed a commit that referenced this issue Sep 3, 2018
@thedaviddias
docs: package author and contributors (#270)
fb52ad7 
**Partially fixes**: #259 

- [x] Check the commit's or even all commits' message styles matches our requested structure.
- [x] Check your code additions will fail neither code linting checks nor unit test.

#### Short description of what this resolves:

Give the main contributor some credits

#### Proposed changes:

- Added main contributors to the package.json

👍 Thank you!
thedaviddias pushed a commit that referenced this issue Sep 3, 2018
@thedaviddias
docs: package author and contributors (#270)
0136067 
**Partially fixes**: #259 

- [x] Check the commit's or even all commits' message styles matches our requested structure.
- [x] Check your code additions will fail neither code linting checks nor unit test.

#### Short description of what this resolves:

Give the main contributor some credits

#### Proposed changes:

- Added main contributors to the package.json

👍 Thank you!
@stale
Copy link

stale bot commented May 14, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the bot:stale Issue marked as stale because there was no activity label May 14, 2020
@Shinigami92
Copy link
Contributor Author

We may close this issue when #388 is merged

@stale stale bot removed the bot:stale Issue marked as stale because there was no activity label May 17, 2020
@stale
Copy link

stale bot commented Jul 16, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the bot:stale Issue marked as stale because there was no activity label Jul 16, 2020
@stale stale bot closed this as completed Jul 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bot:stale Issue marked as stale because there was no activity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thedaviddias @Shinigami92