Skip to content

Release 0.2.3 now #38

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
Merged
merged 1 commit into from
Aug 2, 2017
Merged

Release 0.2.3 now #38

merged 1 commit into from
Aug 2, 2017

Conversation

thiemowmde
Copy link
Contributor

I think this is all we can do here, and we should tag what we did as an actual release.

@thiemowmde thiemowmde requested review from manicki and Ladsgroup August 2, 2017 14:30
manicki
manicki approved these changes Aug 2, 2017
View reviewed changes
Copy link
Contributor

@manicki manicki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not release a code which is used in production for (at least ?) a year as version 1.0.0 but sit on 0.x?

@Ladsgroup Ladsgroup merged commit 4a2f6ab into master Aug 2, 2017
@Ladsgroup Ladsgroup deleted the release023Now branch August 2, 2017 15:37
@thiemowmde
Copy link
Contributor Author

I feel there is just not enough that changed to justify a major version bump. This is all just maintenance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@manicki manicki manicki approved these changes

@Ladsgroup Ladsgroup Awaiting requested review from Ladsgroup

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@thiemowmde @manicki @Ladsgroup