Author Topic: Actually make "versioning" be meaningful.  (Read 6360 times)

Offline redbone

  • BeerSmith Brewer
  • ***
  • Posts: 47
Actually make "versioning" be meaningful.
« on: September 05, 2011, 07:52:20 AM »
Maybe I'm not doing something correctly, but the version number doesn't act like I would anticipate it to act.  In versioning, I would expect to be able to go backwards and see the previous version of the recipe in question.  Without this feature, the version number doesn't have much of a meaning.  Maybe this is already a plan for the future.

Offline BeerSmith

  • Brewer, Author, Patriot
  • BeerSmith Administrator
  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 5569
  • BeerSmith - take the guesswork out of brewing!
    • BeerSmith
Re: Actually make "versioning" be meaningful.
« Reply #1 on: September 07, 2011, 03:41:46 PM »
Hi,
  My original concept was to use the "Brew Log" to store "as brewed" copies.

  I'm working on an update now that will ask you if you want to "save as" the recipe to another name when you change the version now.

  I toyed with a "time machine" type feature that would autosave old versions and be able to move back in time, but it gets pretty complex and large pretty quick if you save every edit.  However a change to where you save a new copy only when the version number changes is an interesting idea I will certainly take a look at.

Brad
Get a free trial of BeerSmith 3 here

Offline noreasterbeer

  • BeerSmith Apprentice Brewer
  • **
  • Posts: 3
  • BeerSmith 2 Rocks!
Re: Actually make "versioning" be meaningful.
« Reply #2 on: September 21, 2011, 04:55:57 PM »
I would tend to agree with the gentleman that commented on versions.  version 1.0 is over written by version 1.1 - accordingly, both versions are exactly the same ..... unless I am missing something.
I often will use the same base recipe and make minor adjustments, than document my actual brew results under notes.  While one could argue, these are two different recipes, I might only make small adjustments and flip back and forth between the two in future brews. It would be great to have a running file under the 'master recipe' (Version 1.0) without renaming /save as , etc. and creating multiple names for basically the same recipe with modifications.  An archived 1.1, 1.2, 1.3 .... documenting each modification would be fantastic and helpful.

I also will take the base recipe and 'play' with hops and % grain to observe what it does to the base recipe on your profile. I might wish to save this for future, but limited intent actually brewing it - would be very helpful to achieve it as a version under the 'master recipe'(version 1.0) as version 1.1 to review results/ profile again in future.  Comments?
« Last Edit: September 22, 2011, 04:56:51 PM by noreasterbeer »

Offline BadCatBrewing

  • BeerSmith Apprentice Brewer
  • **
  • Posts: 3
  • BeerSmith 2 Rocks!
Re: Actually make "versioning" be meaningful.
« Reply #3 on: November 14, 2011, 05:59:01 AM »
I would also like versioning to keep track of the past recipe versions.
I do this now by keeping a set of base recipes in a "To Do" folder and saving recipes with a new name that includes the brew date to track actual brew ativity.
Versioning would steamline my recipe database.

Offline Jaguar10301

  • BeerSmith Apprentice Brewer
  • **
  • Posts: 11
  • BeerSmith 2 Rocks!
Re: Actually make "versioning" be meaningful.
« Reply #4 on: November 20, 2011, 09:15:02 AM »
see my current suggestion for the best and real solution to this whole issue.

Offline BeerSmith

  • Brewer, Author, Patriot
  • BeerSmith Administrator
  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 5569
  • BeerSmith - take the guesswork out of brewing!
    • BeerSmith
Re: Actually make "versioning" be meaningful.
« Reply #5 on: November 20, 2011, 08:36:19 PM »
In build 50+ I did include an option to "Save as" a recipe when you change the version number - that way you can either overwrite or keep the current version.

I like the idea of archiving old versions - but need to build a system specifically to do that in the program.

Brad
Get a free trial of BeerSmith 3 here

Offline grathan

  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 734
  • BeerSmith 2 Rocks!
Re: Actually make "versioning" be meaningful.
« Reply #6 on: March 24, 2013, 05:55:19 PM »
Is this still on the radar? I was trying to figure out what "recipe Version Number" actually does...

Ideally for me it would store a separate recipe file for each version that you could easy switch into view by scrolling in the recipe version number tab.

Offline grathan

  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 734
  • BeerSmith 2 Rocks!
Re: Actually make "versioning" be meaningful.
« Reply #7 on: April 30, 2013, 08:36:10 PM »
Hi,
  My original concept was to use the "Brew Log" to store "as brewed" copies.

  I'm working on an update now that will ask you if you want to "save as" the recipe to another name when you change the version now.

  I toyed with a "time machine" type feature that would autosave old versions and be able to move back in time, but it gets pretty complex and large pretty quick if you save every edit.  However a change to where you save a new copy only when the version number changes is an interesting idea I will certainly take a look at.

Brad

Hard drives are very large these days if you hadn't noticed. Even memory, I have more memory than my computer had hard drive space 15 years ago. I bet that computer could have run beersmith imho

Offline grathan

  • BeerSmith Grandmaster Brewer
  • *****
  • Posts: 734
  • BeerSmith 2 Rocks!
Re: Actually make "versioning" be meaningful.
« Reply #8 on: May 19, 2013, 03:15:01 PM »
Hi,
  My original concept was to use the "Brew Log" to store "as brewed" copies.

  I'm working on an update now that will ask you if you want to "save as" the recipe to another name when you change the version now.

  I toyed with a "time machine" type feature that would autosave old versions and be able to move back in time, but it gets pretty complex and large pretty quick if you save every edit.  However a change to where you save a new copy only when the version number changes is an interesting idea I will certainly take a look at.

Brad

Perhaps not save a new version every time a save is made, but when the user clicks forward on versioning they are prompted to"save as new version?" clicking yes will save the recipe as  the new version number scrolled forward to. clicking backward could load previous versions with changes new to that version (different from very previous one) highlighted.


Offline Toddegg

  • BeerSmith Apprentice Brewer
  • **
  • Posts: 10
  • BeerSmith 2 Rocks!
Re: Actually make "versioning" be meaningful.
« Reply #9 on: May 26, 2013, 10:10:29 PM »
+1 to Grathan's response.


Offline techmiller

  • BeerSmith Apprentice Brewer
  • **
  • Posts: 3
  • BeerSmith 2 Rocks!
Re: Actually make "versioning" be meaningful.
« Reply #10 on: August 17, 2013, 06:42:17 AM »
I second the +1 to Grathan

Hopefully this will be one of the updates this fall!