Re: [openstack-dev] [python3-first] support in stable branches
Hello Doug, thanks for your explanation. I was a little bit confused by changes to stable branches with python3-first topic as I thought it has to do something with adding new test configuration for python3. But as you explained this is about moving zuul-related configuration, which is a part of python3-first goal (but it is not related to supporting python3 by projects IMHO :) ) Anyway, it is now clear to me and sorry for making this confusion. Best, Dariusz Krol On 09/28/2018 06:05 PM, Doug Hellmann wrote: > Dariusz Krol writes: > >> Hello, >> >> >> I'm specifically referring to branches mentioned in: >> https://github.com/openstack/goal-tools/blob/4125c31e74776a7dc6a15d2276ab51ff3e73cd16/goal_tools/python3_first/jobs.py#L54 > I'm still not entirely sure what you're saying is happening that you do > not expect to have happening, but I'll take a guess. > > The zuul migration portion of the goal work needs to move *all* of the > Zuul settings for a repo into the correct branch because after the > migration the job settings will no longer be in project-config at all > and so zuul won't know which jobs to run on the stable branches if we > haven't imported the settings. > > The migration script tries to figure out which jobs apply to which > branches of each repo by looking at the branch specifier settings in > project-config, and then it creates an import patch for each branch with > the relevant jobs. Subsequent steps in the script change the > documentation and release notes jobs and then add new python 3.6 testing > jobs. Those steps only apply to the master branch. > > So, if you have a patch importing a python 3 job setting to a stable > branch of a repo where you aren't expecting it (and it isn't supported), > that's most likely because project-config has no branch specifiers for > the job (meaning it should run on all branches). We did find several > cases where that was true because projects added jobs without branch > specifiers after the branches were created, and then back-ported no > patches to the stable branch. See > http://lists.openstack.org/pipermail/openstack-dev/2018-August/133594.html > for details. > > Doug > >> I hope this helps. >> >> >> Best, >> >> Dariusz Krol >> >> >> On 09/27/2018 06:04 PM, Ben Nemec wrote: >>> >>> On 9/27/18 10:36 AM, Doug Hellmann wrote: >>>> Dariusz Krol writes: >>>> >>>>> Hello Champions :) >>>>> >>>>> >>>>> I work on the Trove project and we are wondering if python3 should be >>>>> supported in previous releases as well? >>>>> >>>>> Actually this question was asked by Alan Pevec from the stable branch >>>>> maintainers list. >>>>> >>>>> I saw you added releases up to ocata to support python3 and there are >>>>> already changes on gerrit waiting to be merged but after reading [1] I >>>>> have my doubts about this. >>>> I'm not sure what you're referring to when you say "added releases up to >>>> ocata" here. Can you link to the patches that you have questions about? >>> Possibly the zuul migration patches for all the stable branches? If >>> so, those don't change the status of python 3 support on the stable >>> branches, they just split the zuul configuration to make it easier to >>> add new python 3 jobs on master without affecting the stable branches. >>> >>>>> Could you elaborate why it is necessary to support previous releases ? >>>>> >>>>> >>>>> Best, >>>>> >>>>> Dariusz Krol >>>>> >>>>> >>>>> [1] https://docs.openstack.org/project-team-guide/stable-branches.html >>>>> __ >>>>> >>>>> OpenStack Development Mailing List (not for usage questions) >>>>> Unsubscribe: >>>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>> __ >>>> >>>> OpenStack Development Mailing List (not for usage questions) >>>> Unsubscribe: >>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>> __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [python3-first] support in stable branches
Hello Doug, thanks for your explanation. I was a little bit confused by changes to stable branches with python3-first topic as I thought it has to do something with adding new test configuration for python3. But as you explained this is about moving zuul-related configuration, which is a part of python3-first goal (but it is not related to supporting python3 by projects IMHO :) ) Anyway, it is now clear to me and sorry for making this confusion. Best, Dariusz Krol On 9/28/18 6:05 PM, Doug Hellmann wrote: > Dariusz Krol writes: > >> Hello, >> >> >> I'm specifically referring to branches mentioned in: >> https://github.com/openstack/goal-tools/blob/4125c31e74776a7dc6a15d2276ab51ff3e73cd16/goal_tools/python3_first/jobs.py#L54 > I'm still not entirely sure what you're saying is happening that you do > not expect to have happening, but I'll take a guess. > > The zuul migration portion of the goal work needs to move *all* of the > Zuul settings for a repo into the correct branch because after the > migration the job settings will no longer be in project-config at all > and so zuul won't know which jobs to run on the stable branches if we > haven't imported the settings. > > The migration script tries to figure out which jobs apply to which > branches of each repo by looking at the branch specifier settings in > project-config, and then it creates an import patch for each branch with > the relevant jobs. Subsequent steps in the script change the > documentation and release notes jobs and then add new python 3.6 testing > jobs. Those steps only apply to the master branch. > > So, if you have a patch importing a python 3 job setting to a stable > branch of a repo where you aren't expecting it (and it isn't supported), > that's most likely because project-config has no branch specifiers for > the job (meaning it should run on all branches). We did find several > cases where that was true because projects added jobs without branch > specifiers after the branches were created, and then back-ported no > patches to the stable branch. See > http://lists.openstack.org/pipermail/openstack-dev/2018-August/133594.html > for details. > > Doug > >> I hope this helps. >> >> >> Best, >> >> Dariusz Krol >> >> >> On 09/27/2018 06:04 PM, Ben Nemec wrote: >>> >>> On 9/27/18 10:36 AM, Doug Hellmann wrote: >>>> Dariusz Krol writes: >>>> >>>>> Hello Champions :) >>>>> >>>>> >>>>> I work on the Trove project and we are wondering if python3 should be >>>>> supported in previous releases as well? >>>>> >>>>> Actually this question was asked by Alan Pevec from the stable branch >>>>> maintainers list. >>>>> >>>>> I saw you added releases up to ocata to support python3 and there are >>>>> already changes on gerrit waiting to be merged but after reading [1] I >>>>> have my doubts about this. >>>> I'm not sure what you're referring to when you say "added releases up to >>>> ocata" here. Can you link to the patches that you have questions about? >>> Possibly the zuul migration patches for all the stable branches? If >>> so, those don't change the status of python 3 support on the stable >>> branches, they just split the zuul configuration to make it easier to >>> add new python 3 jobs on master without affecting the stable branches. >>> >>>>> Could you elaborate why it is necessary to support previous releases ? >>>>> >>>>> >>>>> Best, >>>>> >>>>> Dariusz Krol >>>>> >>>>> >>>>> [1] https://docs.openstack.org/project-team-guide/stable-branches.html >>>>> __ >>>>> >>>>> OpenStack Development Mailing List (not for usage questions) >>>>> Unsubscribe: >>>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>> __ >>>> >>>> OpenStack Development Mailing List (not for usage questions) >>>> Unsubscribe: >>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>>> __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [python3-first] support in stable branches
Hello, I'm specifically referring to branches mentioned in: https://github.com/openstack/goal-tools/blob/4125c31e74776a7dc6a15d2276ab51ff3e73cd16/goal_tools/python3_first/jobs.py#L54 I hope this helps. Best, Dariusz Krol On 09/27/2018 06:04 PM, Ben Nemec wrote: > > > On 9/27/18 10:36 AM, Doug Hellmann wrote: >> Dariusz Krol writes: >> >>> Hello Champions :) >>> >>> >>> I work on the Trove project and we are wondering if python3 should be >>> supported in previous releases as well? >>> >>> Actually this question was asked by Alan Pevec from the stable branch >>> maintainers list. >>> >>> I saw you added releases up to ocata to support python3 and there are >>> already changes on gerrit waiting to be merged but after reading [1] I >>> have my doubts about this. >> >> I'm not sure what you're referring to when you say "added releases up to >> ocata" here. Can you link to the patches that you have questions about? > > Possibly the zuul migration patches for all the stable branches? If > so, those don't change the status of python 3 support on the stable > branches, they just split the zuul configuration to make it easier to > add new python 3 jobs on master without affecting the stable branches. > >> >>> Could you elaborate why it is necessary to support previous releases ? >>> >>> >>> Best, >>> >>> Dariusz Krol >>> >>> >>> [1] https://docs.openstack.org/project-team-guide/stable-branches.html >>> __ >>> >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> __ >> >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [python3-first] support in stable branches
Hello Champions :) I work on the Trove project and we are wondering if python3 should be supported in previous releases as well? Actually this question was asked by Alan Pevec from the stable branch maintainers list. I saw you added releases up to ocata to support python3 and there are already changes on gerrit waiting to be merged but after reading [1] I have my doubts about this. Could you elaborate why it is necessary to support previous releases ? Best, Dariusz Krol [1] https://docs.openstack.org/project-team-guide/stable-branches.html __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [trove] Considering the transfter of the project leadership
Hello Zhao Chao, after some internal discussion, I will do the nomination if you decided not to nominate yourself. Thanks for letting know you will be still available in the next release cycle. Regarding commits I would recommend to consider also https://review.openstack.org/#/c/586528/2 . Best, Dariusz Krol On 07/30/2018 03:26 AM, 赵超 wrote: > > Since the new folks are still so new - if this works for you - I would > recommend continuing on as the official PTL for one more release, > but with the > understanding that you would just be around to answer questions > and give advice > to help the new team get up to speed. That should hopefully be a > small time > commitment for you while still easing that transition. > > Then hopefully by the T release it would not be an issue at all > for someone > else to step up as the new PTL. Or even if things progress well, > you could step > down as PTL at some point during the Stein cycle if someone is > ready to take > over for you. > > > Sean, thanks a lot for these helpful suggestions. I thought about > doing it this way before writing this post, and this is also the > reason I asked the current active team members to nominate theselves. > > However, it's sad that the other active team members seems also busy > on other thing. So I think it may be better Dariusz and his team could > do more than us on the project in the next cycle. I believe they're > experience on the project , and all other experiences about the whole > OpenStack environment could be more familiar in the daily > pariticipation of the project. > > On the other hand, I can also understand the lack of time to be a > PTL since it requires probably a lot of time to coordinate all the > work. > > > Dariusz, no, the current team is really a small team, so in fact I > didn't need to do much coordination. The pain is that almost none of > the current active team member are not focusing Trove, so even thought > all of us want to do more progress in this cycle, we're not able to. > This also the reason all of us think it's great to have to team > focusing on the project could join. > > So, we don't have much time on the PTL election now, Dariusz, would > you please discuss with your team who will do the nomination. And then > we'll see if everything could work. We could also try to merge one the > trove-tempest-plugin patches(https://review.openstack.org/#/c/580763/ > could be merged first before we get the CI could test all the cases in > the repo, sadlly currently we cannot the other patches as they're > cannot be tested). > > However that patch is submitted by Krzysztof, though is authored by > Dariusz. I don't know whether this could count as an identifiied > commit when applying PTL nomination. > > And last, I want to repeat that, I'll still in the Trove delepoment > for quit a long time, so I will help the new PTL and new contributor > on everything I could. > > Thanks again for everyone who help me a lot in the last cycle, > especially Fan Zhang, zhanggang, wangyao, song.jian and Manoj Kumar. > > -- > To be free as in freedom. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] openstack-dev] [trove] Considering the transfter of the project leadership
Hi Sean, This is good point. It would be great to have some help especially to start. We have some experience with contributing to openstack and we are working with gerrit on daily basis so there is no problem with technical aspects. However, it takes some time for changes to be reviewed and merged and we would like to change it. On the other hand, I can also understand the lack of time to be a PTL since it requires probably a lot of time to coordinate all the work. Let’s wait for Chao Zhao to give his opinion on the topic :) Best, Dariusz Krol __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] openstack-dev] [trove] Considering the transfter of the project leadership
Hello All, as a member of Samsung R Center in Krakow, I would like to confirm that we are very interested in Trove development. We also notices that Trove project has a small team now and that community around Trove becomes smaller with each release which is a shame since it is a great project. That is why we would like to step up and help with development and leadership. We started our contribution with code reviews and we also submitted our first contributions to trove-tempest-plugin. We intend to increase our involvement in the community but we understand it need to take some time and help from community. I would like to thank current Trove team for warm welcome, and I'm really looking forward to the future collaboration with the community. Kind regards, Dariusz Krol On 07/25/2018 06:18 PM, 赵超 wrote: > cc to the Trove team members and guys from Samsung R Center in > Krakow, Poland privately, so anyone of them who are not reading the ML > could also be notified. > > On Thu, Jul 26, 2018 at 12:09 AM, 赵超 <mailto:zhaochao1...@gmail.com>> wrote: > > Hi All, > > Trove currently has a really small team, and all the active team > members are from China, we had some good discussions during the > Rocky online PTG meetings[1], and the goals were arranged and > priorited [2][3]. But it's sad that none of us could focus on the > project, and the number of patches and reviews fall a lot in this > cycle comparing Queens. > > [1] https://etherpad.openstack.org/p/trove-ptg-rocky > <https://etherpad.openstack.org/p/trove-ptg-rocky> > [2] > https://etherpad.openstack.org/p/trove-priorities-and-specs-tracking > <https://etherpad.openstack.org/p/trove-priorities-and-specs-tracking> > [3] > > https://docs.google.com/spreadsheets/d/1Jz6TnmRHnhbg6J_tSBXv-SvYIrG4NLh4nWejupxqdeg/edit#gid=0 > > <https://docs.google.com/spreadsheets/d/1Jz6TnmRHnhbg6J_tSBXv-SvYIrG4NLh4nWejupxqdeg/edit#gid=0> > > And for me, it's a really great chance to play as the PTL role of > Trove, and I learned a lot during this cycle(from Trove projects > to the CI infrastrues, and more). However in this cycle, I have > been with no bandwith to work on the project for months, and the > situation seems not be better in the forseeable future, so I think > it's better to transfter the leadership, and look for opportunites > for more anticipations in the project. > > A good news is recently a team from Samsung R Center in Krakow, > Poland joined us, they're building a product on OpenStack, have > done improvments on Trove(internally), and now interested in > contributing to the community, starting by migrating the > intergating tests to the tempest plugin. They're also willing and > ready to act as the PTL role. The only problem for their > nomination may be that none of them have a patched merged into the > Trove projects. There're some in the trove-tempest-plugin waiting > review, but according to the activities of the project, these > patches may need a long time to merge (and we're at Rocky > milestone-3, I think we could merge patches in the > trove-tempest-plugin, as they're all abouth testing). > > I also hope and welcome the other current active team members of > Trove could nominate themselves, in that way, we could get more > discussions about how we think about the direction of Trove. > > I'll stll be here, to help the migration of the integration tests, > CentOS guest images support, Cluster improvement and all other > goals we discussed before, and code review. > > Thanks. > > -- > To be free as in freedom. > > > > > -- > To be free as in freedom. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
