[#505] - Establish git workflow for release/deploy
- Closed
- 30 Oct 2015
- Medium
- Build: master
- # 505
It's going to be impractical to always depend on someone to synchronize the live website with the git repository master branch or to automate deployments to the live environment. Prior to officially tagging a 1.0.0 stable release, we should establish a workflow with regards to how patches will be merged between tags (releases), how architectural changes will be handled (files will work OK when checking out git tags or revisions, but database schema updates will need some thinking), and how languages will be managed for releases. Any other concerns should be addressed within this issue too.
| Labels |
Added:
reoccurring
|
||
| Labels |
Removed:
reoccurring
|
||
| Labels |
Added:
question
requirement
|
||
| Labels |
Added:
v1.0
|
||
I can't imagine how to manage SQL changes
The simplest thing would be that we have a folder with SQL files for each version there are changes in, somewhat similar to the CMS. So we tag 1.0.0 and 1.0.1 has a database change, then we'd have something like etc/updates/1.0.1.sql and that would have whatever queries are needed to alter the database. It doesn't need to be incorporated into any deploy script, but it surely would make running updates easier if we had a process where only tagged versions were deployed.
Sounds like solution.
and how languages will be managed for releases
Is it possible to update them on Transifex automatically?
About SQL or DB versioning, since I've started to work with Rails recently, I think we can implement a db migration module (or maybe there is already a similar solution like dbv ) which mangaes a db scheme file to log the whole db generate file(just like the sql file in /etc currently.
And everytime a change should be versioned to get every developer's working copy of JTracker working under the correct version of db and make deploy easier.
This never caught priority anyway.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-10-30 18:15:54 |
| Closed_By | ⇒ | mbabker |
I can't imagine how to manage SQL changes
Do you think we need to sync so often? Now when people have started to use new tracker we are having a little more job with fixing bugs and implementing hot features. But I do not think that it will continue forever ;)