hahaha!!! excuse me, I'm thinking in the flink project when read the last email, I do not know why.
*Hector Miuler Malpica Gallegos <http://www.miuler.com>* El jue, 2 jun 2022 a la(s) 18:04, Danny McCormick (dannymccorm...@google.com) escribió: > Thanks for calling that out Hector - the migration will only migrate > issues from the Beam project (that one is from the Flink project), so I > don't think it should be an issue. > > Thanks, > Danny > > On Thu, Jun 2, 2022 at 6:38 PM Hector Miuler Malpica Gallegos < > miu...@gmail.com> wrote: > >> This migration includes the issues of the component `Kubernetes Operator` >> ? like this issue FLINK-27820 >> <https://issues.apache.org/jira/browse/FLINK-27820> ? this issues >> correspond to the repository >> https://github.com/apache/flink-kubernetes-operator, keep it in mind. >> >> >> *Hector Miuler Malpica Gallegos <http://www.miuler.com>* >> >> >> >> El jue, 2 jun 2022 a la(s) 12:33, Danny McCormick ( >> dannymccorm...@google.com) escribió: >> >>> Given the consensus here, I updated the tool to do this. This means that >>> we won't update the JIRAs to be read-only until after the migration is >>> complete. I'll rerun the tool if any extra jiras come in during the >>> intervening period. The tool will also still write the mapping to the file >>> in case there are unforeseen issues so that we can backfill if needed. >>> >>> Thanks for the suggestion and followup Brian, Ahmet, and Alexey. >>> >>> On Thu, Jun 2, 2022 at 12:16 PM Alexey Romanenko < >>> aromanenko....@gmail.com> wrote: >>> >>>> +1 That would be very helpful for mapping! >>>> >>>> On 2 Jun 2022, at 17:48, Ahmet Altay <al...@google.com> wrote: >>>> >>>> Is it possible to add comments on the JIRAs with a link to the new >>>> corresponding github issue? >>>> >>>> On Thu, Jun 2, 2022 at 8:47 AM Danny McCormick < >>>> dannymccorm...@google.com> wrote: >>>> >>>>> Thanks for the feedback, I agree it would be good to keep that option >>>>> open - I updated the tool to write those to a file when we create an >>>>> issue. >>>>> I'll share that after the migration. >>>>> >>>>> Thanks, >>>>> Danny >>>>> >>>>> On Wed, Jun 1, 2022 at 7:03 PM Brian Hulette <bhule...@google.com> >>>>> wrote: >>>>> >>>>>> Thanks Danny. Regarding links to GitHub issues, if we could at least >>>>>> save off a record of jira <-> issue mappings we could look at adding the >>>>>> links later. I think it would be nice to have those links so that anyone >>>>>> landing in a jira through a search or an old link can quickly find the >>>>>> current ticket, but I don't think that needs to block the migration. >>>>>> >>>>>> On Wed, Jun 1, 2022 at 7:05 AM Danny McCormick < >>>>>> dannymccorm...@google.com> wrote: >>>>>> >>>>>>> Hey Brian, >>>>>>> >>>>>>> 1. Right now, the plan is to (1) turn on the issues tab, (2) make >>>>>>> the JIRA read only, (3) run the migration tool. Since the migration tool >>>>>>> won't be run until after Jiras are read only, there shouldn't be issues >>>>>>> with making sure everything gets captured. >>>>>>> 2. That current ordering does mean it's difficult to add a link to >>>>>>> the newly created Issue, and I hadn't built in that feature. With that >>>>>>> said, I will ask Infra if they're able to put up a banner redirecting >>>>>>> people to GitHub for the Beam project - that should hopefully minimize >>>>>>> some >>>>>>> of the issues - and I'll also look into updating the tool to do that in >>>>>>> case the banner isn't doable. I'm also planning on doing a few passes to >>>>>>> update our docs and code comments from Jiras to issues once the >>>>>>> migration >>>>>>> is done. >>>>>>> >>>>>>> Thanks, >>>>>>> Danny >>>>>>> >>>>>>> On Tue, May 31, 2022 at 8:09 PM Brian Hulette <bhule...@google.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Thanks Danny, it's great to see this happening! >>>>>>>> >>>>>>>> A couple of questions: >>>>>>>> - Is there something we can do to remind people creating a jira >>>>>>>> that they should create a bug instead (e.g. a template)? If not I >>>>>>>> suppose >>>>>>>> we can just re-run the migration tool a few times up until jira >>>>>>>> creation is >>>>>>>> disabled to make sure everything is captured. >>>>>>>> - Will your migration tooling comment on the original jira with a >>>>>>>> link to the new issue in GitHub? >>>>>>>> >>>>>>>> Brian >>>>>>>> >>>>>>>> On Tue, May 31, 2022 at 9:57 AM Robert Bradshaw < >>>>>>>> rober...@google.com> wrote: >>>>>>>> >>>>>>>>> Thanks for finally making this happen. >>>>>>>>> >>>>>>>>> On Tue, May 31, 2022 at 7:18 AM Sachin Agarwal < >>>>>>>>> sachi...@google.com> wrote: >>>>>>>>> > >>>>>>>>> > Thank you Danny! This will help us a lot, especially with new >>>>>>>>> contributors. Thanks so much! >>>>>>>>> > >>>>>>>>> > On Tue, May 31, 2022 at 4:10 AM Danny McCormick < >>>>>>>>> dannymccorm...@google.com> wrote: >>>>>>>>> >> >>>>>>>>> >> Hey folks, this is a reminder that we will be migrating from >>>>>>>>> Jira to GitHub Issues this Friday (6/4). A few key details to keep in >>>>>>>>> mind: >>>>>>>>> >> >>>>>>>>> >> 1. All active Jiras will get automatically migrated and >>>>>>>>> assigned over the course of the weekend. >>>>>>>>> >> 2. Starting Friday (once the the Issues tab is open), please >>>>>>>>> stop creating Jiras and start creating Issues instead. You should also >>>>>>>>> reference issues in your PRs and commits instead of Jiras. The Jira >>>>>>>>> creation flow will eventually be disabled. >>>>>>>>> >> 3. If you encounter any issues that can't be resolved by >>>>>>>>> looking at the doc updates, please let me know and/or follow up in >>>>>>>>> this >>>>>>>>> thread. >>>>>>>>> >> >>>>>>>>> >> I'm looking forward to seeing how Issues can minimize friction >>>>>>>>> for new contributors and I'm hopeful that this will be a smooth >>>>>>>>> transition. >>>>>>>>> If you have any last minute concerns let me know. For more context, >>>>>>>>> see the >>>>>>>>> original thread on this topic. >>>>>>>>> >> >>>>>>>>> >> Thanks, >>>>>>>>> >> Danny >>>>>>>>> >>>>>>>> >>>>
