What happens when there is an update?

[codegeek511]

If and or when you guys come out with another update of the app, and we have it on the newsstand, will we have to redo the customization etc. of the app?

[folletto]

That's correct. :)

In theory you will just have to change the settings and upload the images (and add the books if it's a Standalone app), but if you did any other customization then it's up to you to keep it updated on the new version.

[nin9creative]

Yes, if you make changes you will.

However if you save your local change codebase in a git or other source control mechanism, you might be
able to more easily handle the new Baker releases by dropping the new code overtop your changes and then
using a diff tool to merge the changes in.

You could also fork on github and make changes on your forked version and then later on pull in newer changes
from the Baker stream, etc...  However there are considerations related to if you want your stuff publically viewable
or not...

---

From: codegeek511 [email protected]
To: Simbul/baker [email protected]
Sent: Tuesday, November 12, 2013 6:47 PM
Subject: [baker] What happens when there is an update? (#1207)

If and or when you guys come out with another update of the app, and we have it on the newsstand, will we have to redo the customization etc. of the app?
—
Reply to this email directly or view it on GitHub.

[fcontreras]

You can also get a private GitHub repo, it will be easier to fork, merge new changes from the Baker repo and also keep yours.

[nin9creative]

Can you make a repo private from a public fork?

Regards,
Andrew

Sent from my iPhone

On Nov 17, 2013, at 2:42 PM, Francisco Contreras [email protected] wrote:

You can also get a private GitHub repo, it will be easier to fork, merge new changes from the Baker repo and also keep yours.

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

[fcontreras]

Ahg.. my bad.. use to be there though..

just check, said
Make this repository private
Make private
Public forks can't be made private. Please duplicate the repository or contact support.

Now you need to clone it.. :(

[folletto]

There's no need to get a GitHub repository. You can just do that anywhere with plain git. :)

[fcontreras]

Fork? you mean..

[benoitchantre]

@fcontreras There's no need to fork Baker, unless you want to propose your changes with a pull request or to collaborate with someone. When you download the project, you have already a local git repository.