14:14:52 <andreykurilin> #startmeeting Rally
14:14:53 <openstack> Meeting started Mon Mar 27 14:14:52 2017 UTC and is due to finish in 60 minutes.  The chair is andreykurilin. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:14:54 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:14:56 <openstack> The meeting name has been set to 'rally'
14:15:15 <andreykurilin> hi everyone!
14:15:24 <chenhb_> hi
14:15:25 <rallydev-bot2> [From Gitter] tohin : hi
14:15:31 <rallydev-bot2> [From Gitter] astarove : hi
14:15:34 <rallydev-bot2> [From Gitter] shihai1991 : hi
14:16:08 <andreykurilin> #topic Branches in Rally
14:16:27 <andreykurilin> We do not have any branches except "master" branch
14:16:40 <andreykurilin> In general, it is ok
14:18:07 <andreykurilin> but sometimes, we discover critical bug in latest release, but cannot do a new one, since new serias of patches start merging and master branch becomes in a not-finished state
14:18:40 <andreykurilin> for example, we start merging changes in API, which are backward incompatible. Such changes should be released in one version to reduce pain
14:18:50 <andreykurilin> and now we cannot release new version of Rally
14:19:34 <rallydev-bot2> [From Gitter] astarove : well, we can use two branches^ master or release and development. In this case all critical changes can be fixed on release branch
14:19:44 <rallydev-bot2> [From Gitter] astarove : [edit] well, we can use two branches: master or release and development. In this case all critical changes can be fixed on release branch
14:20:02 <andreykurilin> yes, we will have several branches now
14:20:35 <rallydev-bot2> [From Gitter] astarove : so we will develop new features on DEV branch and merge tested patches on RELEASE branch
14:20:39 <andreykurilin> master branch will still be our main branch
14:20:40 <rallydev-bot2> [From Gitter] shihai1991 : But we need human to maintain two branches.
14:21:10 <chenhb_> we can create development branch for new,feature
14:21:38 <andreykurilin> let's leave master branch for active development and latest release will occure from it
14:22:19 <rallydev-bot2> [From Gitter] astarove : also I propose to create stand-alone branches for each critical fix to make sure what master branch is always in good condition
14:22:26 <andreykurilin> and create additional branch each time when we release new rally version. For example, after releasing 0.9.0, we should create stable/0.9 branch
14:22:55 <andreykurilin> First, fixes will be merged to master branch and than they will be backported to stable/x.y branch
14:23:33 <andreykurilin> it will allow to deliver 0.9.1 with bug-fixes only
14:24:16 <andreykurilin> astarove: each critical fix should land to master branch asap without additional branches :)
14:25:13 <rallydev-bot2> [From Gitter] astarove : i hope what there is just one critical issue or less on release, so you're right :)
14:25:19 <andreykurilin> shihai1991: maintaining two branches will not take much himan-resources, since we will have only one main branch and all fixes will be accepted via it (merge to master branch as a first step, that backport to stable branch)
14:25:54 <rallydev-bot2> [From Gitter] shihai1991 : ok, it's fine to me.
14:26:27 <andreykurilin> astarove: yes, there should not be two much critical bug-fixes
14:26:32 <andreykurilin> *too much
14:27:06 <andreykurilin> for 0.9.0 we have one critical bug fix. `rally verify rerun` is totally broken now.
14:27:25 <chenhb_> we need to change install_rally.sh for stable branch
14:27:56 <andreykurilin> chenhb_: What do you mean? A new flag to download a latest stable branch?
14:28:21 <chenhb_> yes
14:29:14 <andreykurilin> chenhb_: I think we can add flag to download latest tag
14:29:28 <andreykurilin> stable branches should not have unreleased thing
14:29:41 <rallydev-bot2> [From Gitter] tohin : we have --branch option in rally_install.sh
14:29:56 <rallydev-bot2> [From Gitter] tohin : with default to "master"
14:30:03 <chenhb_> greate
14:30:44 <chenhb_> we can use --branch
14:30:59 <andreykurilin> So I hope that I'll find the way how to create new branches via openstack/releases repo and will create a first our branch
14:31:18 <andreykurilin> hope it will happen soon
14:32:03 <andreykurilin> There is only one open question - should we support the only last major release or two last major releases?
14:32:19 <andreykurilin> I prefer to only support only the last
14:32:58 <rallydev-bot2> [From Gitter] astarove : it's easy but...
14:33:06 <rallydev-bot2> [From Gitter] tohin : I think the last one is enought
14:33:29 <rallydev-bot2> [From Gitter] tohin : [edit] I think the last one is enough
14:33:40 <chenhb_> agree
14:33:49 <rallydev-bot2> [From Gitter] shihai1991 : +1
14:33:57 <andreykurilin> cool :)
14:34:07 <andreykurilin> it is less painful
14:34:17 <rallydev-bot2> [From Gitter] astarove : users should have some time to adopt new functionality
14:34:39 <andreykurilin> #topic i18n support in Rally
14:35:10 <andreykurilin> ok, we start using oslo.i18n library long time ago
14:35:30 <andreykurilin> Also, we made a rule to use `_()` things everywhere
14:35:45 <andreykurilin> But translations were not even enabled for our project :(
14:36:20 <andreykurilin> even more, it looks like some of things should not be translated anymore - https://review.openstack.org/#/c/447886/
14:37:11 <andreykurilin> I need a volunteer who can spend some time for investigation of howto enable translation for Rally project
14:38:02 <andreykurilin> ok, I'll add it as a task to our trello board...
14:38:24 <andreykurilin> #topic Open discussions
14:38:30 <andreykurilin> any topics to discuss?
14:39:58 <andreykurilin> okay
14:40:00 <rallydev-bot2> [From Gitter] shihai1991 : no topic from my side.
14:40:08 <andreykurilin> thanks for participation!
14:40:10 <andreykurilin> bye
14:40:15 <andreykurilin> #endmeeting