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?
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