Re: Renaming Existing kibble Repo to kibble-old
Hello, Thank you Sharan for the info. :) Have a nice day! Thanks Michał > On 13 Feb 2021, at 15:52, Sharan Foga wrote: > > Hi All > > No worries. I've just responded to a comment from Gavin about the rename. He > has asked why we just don't delete everything and do a push. I've told him > that we said that we would pick and choose what to bring over from the old > into the new - so still need to old code available. We also have some > existing and working user installs on the code we have now. > > I'll be tracking the Jira ticket and everyone please feel free to monitor it > too. > > Thanks > Sharan > >> On 2021/02/10 01:14:59, Tomasz Urbaszek wrote: >> Thanks Sharan for opening the jira ticket! >> >> I had quite few things on my head in last few weeks but once the >> ticket is resolved I'm happy to configure pre-commits and Github >> Actions to assure that we build new Kibble using best practices 👍 >> >> Best wishes, >> Tomek >> >>> On Tue, 9 Feb 2021 at 21:36, Michał Słowikowski >>> wrote: >>> >>> Hi Sharan, >>> >>> Thank you. :) >>> >>> We could move with Kibble somehow. >>> I think we should move our action points from our latest and the only one >>> call to GitHub issues. >>> Break more complex tasks into smaller and easier. >>> >>> Right know we have branch 2.0 made by Tomek. >>> >>> Should we cherry-pick something to that branch Sorry but I did have >>> opportunity to take a look at 2.0 branch :( >>> >>> Best >>> Michal >>> >>> On 9 Feb 2021, at 21:19, Sharan Foga wrote: Hi All Infra jira ticket created https://issues.apache.org/jira/browse/INFRA-21411 Thanks Sharan > On 2021/02/09 20:11:45, Sharan Foga wrote: > OK I will file one and post the details here so people can track it. > > Thanks > Sharan > >> On 2021/02/09 20:08:59, Daniel Gruno wrote: >> On 09/02/2021 21.07, Sharan Foga wrote: >>> Hi Tomek >>> >>> I am separating this out as a new thread as I think it got lost in the >>> previous discussion. So has anything happened regarding this? >>> >>> I took a quick look and I don't have access to the repo settings to do >>> the rename so maybe it is something we need to ask infra to do as the >>> apache organisation owner. >> >> yeah, renames require a jira ticket, I believe. Feel free to file one :) >> >>> >>> Thanks >>> Sharan >>> >>> >>> - >>> >>> >>> From: Tomasz Urbaszek >>> Subject: Re: [Meeting Notes] Kibble Dev Call - 7 Jan 2021 >>> Date: 2021/01/16 11:30:56 >>> List: dev@kibble.apache.org >>> >>> Hi folks, >>> >>> I created a 2.0 branch in apache/kibble (just for sanity sake if we >>> would >>> like to reuse some code) and I restored the main branch to some commit >>> before breaking the refactor. >>> >>> Can someone of you rename apache/kibble -> apache/kibble-old and then >>> create apache/kibble repo (as discussed earlier)? I don't have the >>> right to >>> rename repo. >>> >>> Cheers, >>> Tomek >>> >> >> > >>
Re: Renaming Existing kibble Repo to kibble-old
Hi All No worries. I've just responded to a comment from Gavin about the rename. He has asked why we just don't delete everything and do a push. I've told him that we said that we would pick and choose what to bring over from the old into the new - so still need to old code available. We also have some existing and working user installs on the code we have now. I'll be tracking the Jira ticket and everyone please feel free to monitor it too. Thanks Sharan On 2021/02/10 01:14:59, Tomasz Urbaszek wrote: > Thanks Sharan for opening the jira ticket! > > I had quite few things on my head in last few weeks but once the > ticket is resolved I'm happy to configure pre-commits and Github > Actions to assure that we build new Kibble using best practices 👍 > > Best wishes, > Tomek > > On Tue, 9 Feb 2021 at 21:36, Michał Słowikowski > wrote: > > > > Hi Sharan, > > > > Thank you. :) > > > > We could move with Kibble somehow. > > I think we should move our action points from our latest and the only one > > call to GitHub issues. > > Break more complex tasks into smaller and easier. > > > > Right know we have branch 2.0 made by Tomek. > > > > Should we cherry-pick something to that branch Sorry but I did have > > opportunity to take a look at 2.0 branch :( > > > > Best > > Michal > > > > > > > On 9 Feb 2021, at 21:19, Sharan Foga wrote: > > > > > > Hi All > > > > > > Infra jira ticket created > > > https://issues.apache.org/jira/browse/INFRA-21411 > > > > > > Thanks > > > Sharan > > > > > >> On 2021/02/09 20:11:45, Sharan Foga wrote: > > >> OK I will file one and post the details here so people can track it. > > >> > > >> Thanks > > >> Sharan > > >> > > >>> On 2021/02/09 20:08:59, Daniel Gruno wrote: > > >>> On 09/02/2021 21.07, Sharan Foga wrote: > > Hi Tomek > > > > I am separating this out as a new thread as I think it got lost in the > > previous discussion. So has anything happened regarding this? > > > > I took a quick look and I don't have access to the repo settings to do > > the rename so maybe it is something we need to ask infra to do as the > > apache organisation owner. > > >>> > > >>> yeah, renames require a jira ticket, I believe. Feel free to file one :) > > >>> > > > > Thanks > > Sharan > > > > > > - > > > > > > From: Tomasz Urbaszek > > Subject: Re: [Meeting Notes] Kibble Dev Call - 7 Jan 2021 > > Date: 2021/01/16 11:30:56 > > List: dev@kibble.apache.org > > > > Hi folks, > > > > I created a 2.0 branch in apache/kibble (just for sanity sake if we > > would > > like to reuse some code) and I restored the main branch to some commit > > before breaking the refactor. > > > > Can someone of you rename apache/kibble -> apache/kibble-old and then > > create apache/kibble repo (as discussed earlier)? I don't have the > > right to > > rename repo. > > > > Cheers, > > Tomek > > > > >>> > > >>> > > >> >
