![]() ![]() Weekly releases at the beginning or in the middle of the week are sufficient in my opinion. I think the Github-Flow is good and simple because it makes sense but not every merge to the main branch should be connected with a public release. For a website as well as the web-frontend it is not a problem as customers always use the latest website version anyway but for an app not so good. Sometimes there were also bad reviews so I think even one app release per day would be too much. So one release per week and actually customers complained why the app updated so often. We had weekly sprints with one release at the end. Normally this is not a problem, as not everyone goes through the new updates in the app stores, but I have the following experience from my time at Doodle: If we now create a new release as soon as we push to the main branch, even several times a day, we would have to push several new releases to the app stores.įrom an app customer perspective, this means updating the app several times a day. Release cycles of 1 to 3 weeks is normal. In todays dev teams, scrum or kanban is daily business. Key is here: Everything in master is deployable and should be deployed but what does that mean as an app developer?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |