Code, DB, Git organization and releases

[jotak]

Hello there,

I have some general questions about the organization you have (or you plan to have) regarding open-source cooperation :

- How do you manage DB structure changes (for instance, let's say there's a new setting I need to implement and persist in DB) in relation with a GIT code commit? Is the DB structure stored on GIT?

- What is the testing / validation procedure, if I've developped a new feature that you're interested in? Are you going to test it on several devices, do you ask the community for help in testing each feature independantly?

- Releases : can we rely on GIT for future releases, or is it mandatory to run a full reinstall of the disk image at every release? Is there a way to keep personal configuration between releases (let's say for instance I've installed vim, customized my prompt and installed other softwares)

[Mte90]

+1

[Orion]

[Mte90]

Thanks, a documentation about the development workflow?
For example for create my pull request i've cloned the RuneUi repo, flashed the latest alpha in the raspberry.
i've edited the code in ssh on the raspberry, copied the file locally and placed in the RuneUI forked repo and finally do it the pull request.

A simple way for do it this? Like a script for use the repo on github for the ui is a simple solution for develop this part of the system.