search

frc-frecon / frecon

An API for building scouting apps for FRC competitions
MIT License
3 stars 0 forks source link

Start Versioning? #27

Closed rye closed 10 years ago

rye commented 10 years ago

Having multiple different levels of functionality assigned to version 0.0.0 is getting very confusing. Even if we're just incrementing the counter in the lib/frecon/base/version.rb file (and not deploying), that's okay with me.

For the record, what's the reason that we aren't incrementing the version? When can we start?

Sammidysam commented 10 years ago

I'd say the version we have at CAGE should ideally be able to be 0.1.0, as long as all initial features are covered. I think the main thing left to be done before then would be the Robot model for pre-scouting.

rye commented 10 years ago

Since we have more than just a modicum of code, can I go ahead and create a 0.0.1 release?

Sammidysam commented 10 years ago

Initial release is conventionally 0.1.0, though. I can do it on Saturday or something.

On Oct 14, 2014, at 11:13 AM, Kristofer Rye notifications@github.com wrote:

Since we have more than just a modicum of code, can I go ahead and create a 0.0.1 release?

— Reply to this email directly or view it on GitHub.

rye commented 10 years ago

I'll do it on Friday night (maybe at midnight) since I have Thursday through Monday off on break.

rye commented 10 years ago

Once I do, I will update the dependency within WeBCa to be ~> 0.1. @vmai / @tigerh, you'll probably want to be running the most up-to-date versions of everything, right? Would it be better for me to release on Friday morning so that you have time to update the hardware during the day?

EDITed multiple times to fix and add stuff.

Sammidysam commented 10 years ago

Friday sounds good to me. I'll be at a Robotics meeting on Thursday so I should be able to make the Robot model then, which'll make the Friday release a good initial release. Also you should look at the gem-release gem since it may look nice.

On Oct 14, 2014, at 1:24 PM, Kristofer Rye notifications@github.com wrote:

Once I do, I will update the dependency within WeBCa to be ~> 0.1. @vmai/@tigerh, you'll probably want to be running the most up-to-date versions of everything, right? Would it be better for me to release on Friday morning so that you have time to update the hardware during the

— Reply to this email directly or view it on GitHub.

rye commented 10 years ago

It looks like the Robot model has been added successfully. We'll need to test it out on WeBCa, but any issues can be resolved.

Tomorrow morning, whenever I wake up, I'll first check for objections, and then I'll set the version to 0.1.0.

From there, minor fixes and tweaks will be increments of the patch number, major fixes and tweaks will be increments of the minor version number, and backwards-incompatible, massive changes will be increments of the major version number. We do not need to be anal about sticking to a set versioning system, but it'd be good to keep the version numbers well-selected.

Sammidysam commented 10 years ago

Sounds good. I have a commit that I failed to push because I lost internet right before the Robotics meeting ended, but I can push it this evening and it can be a patch update or part of one in the future.

On Oct 16, 2014, at 11:25 PM, Kristofer Rye notifications@github.com wrote:

It looks like the Robot model has been added successfully. We'll need to test it out on WeBCa, but any issues can be resolved.

Tomorrow morning, whenever I wake up, I'll first check for objections, and then I'll set the version to 0.1.0.

From there, minor fixes and tweaks will be increments of the patch number, major fixes and tweaks will be increments of the minor version number, and backwards-incompatible, massive changes will be increments of the major version number. We do not need to be anal about sticking to a set versioning system, but it'd be good to keep the version numbers well-selected.

— Reply to this email directly or view it on GitHub.

rye commented 10 years ago

I have started the versioning with v0.1.0. Closing this issue.