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.

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

Software versioning #20

Open
heborras opened this issue Mar 25, 2018 · 1 comment
Open

Software versioning #20

heborras opened this issue Mar 25, 2018 · 1 comment

Comments

@heborras
Copy link
Contributor

Hi,
while I was going through the issues, labelling them. I noticed that it would be nice to sort out the issues by priority. Since packaging #16 is already a goal, I would propose to do a sort of software versioning for the releases. With this we can have version milestones and version issues. This would in turn highlight what has priority and give us a sort of schedule to work towards. Also planning for the future as in #19 becomes easier.

However I have little experience with setting up a versioning/release system. Additionally I have little time until I finish my thesis. So it would probably be a good idea to think this over together.

@lukicdarkoo and @pingud98 what are your thoughts on implementing software versioning?

Cheers,
Hendrik

@lukicdarkoo
Copy link

I think it is a great idea! It would help users easily find a stable version.

We can also set up some CI service to publish Python/Debian/RPM package every time a new tag is created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants