Hi Tim, tanks a lot for putting so much effort into the new issue structure and the awesome documentation. The result is amazing and I'm really looking forward to working with the new issue system.
Cheers, Philipp Von: Tim <[email protected]> Datum: Montag, 28. November 2022 um 20:55 An: [email protected] <[email protected]> Betreff: Re: Issue migration completed Hi all, you can now find an initial version of the "how to GitHub issues page" in confluence [1]. In case you miss anything, feel free to adapt or ask for help if you not directly find the corresponding feature in GitHub. Best Tim [1] https://cwiki.apache.org/confluence/display/STREAMPIPES/Work+with+GitHub+issues Am 28.11.2022 07:53 schrieb Xin Wang: > Thanks for the great work! > > Dominik Riemer <[email protected]> 于2022年11月28日周一 06:08写道： > >> Hi Tim, >> >> I had a look at the new templates and they are absolutely awesome! >> Very >> welcoming and convenient for new users and I also like the links to >> the >> discussion page... >> >> Cheers >> Dominik >> >> >> -----Original Message----- >> From: Tim <[email protected]> >> Sent: Sunday, November 27, 2022 9:22 PM >> To: [email protected] >> Subject: Re: Issue migration completed >> >> Hi all, >> >> I have familiarized myself a bit with GitHub Issues and prepared some >> aspects for our future work with it: >> >> 1) Labels >> During the migration from Jira to Github, we already put some thought >> into >> the labels we want to use from now on. >> A list of all labels and their description can be found here [1]. >> What are your thoughts? Are you already missing any? If not, we can >> just >> start with the current selection and expand it step by step if needed. >> >> 2) Release planning/versions >> From what I've seen so far, GitHub milestones are good for >> managing/scheduling our releases, just like we did with JIRA. >> So I mapped the upcoming releases that were already in JIRA to Github, >> see >> [2]. >> Can you link that? Do you think we can work this way? >> >> 3) Issue templates >> Github offers to possibility to provide so called "issue template" >> that >> allows to provide custom forms that simplifies the process for >> external >> people to create issues about StreamPipes. Therefore, I've created a >> pull >> request [3]. >> You can see how it would like when visiting my private fork of >> StreamPipes >> and click on "new issue" [4]. >> How do you like it? Would you like to change anything? Is there >> something >> missing? >> I'm happy to discuss changes within the PR. >> >> Do you miss anything for working with GitHub issues (besides the "how >> to" >> manual already mentioned before)? >> >> Best >> Tim >> >> [1] https://github.com/apache/streampipes/labels >> [2] https://github.com/apache/streampipes/milestones >> [3] https://github.com/apache/streampipes/pull/807 >> [4] >> https://github.com/bossenti/incubator-streampipes/issues/new/choose >> >> Am 26.11.2022 19:45 schrieb Florian Micklich: >> > Thank you all for the work. >> > 1307 Emails in my github folder :-P >> > >> > Is there a howto "create a ticket" and some basic infos somewhere? >> > e.g. how to create a subticket, version number, assign to, basic >> > community rules for creating an issue. >> > I come totally from the jira world and this info would be for everyone >> > good. >> > >> > >> > Greetings >> > Florian >> > >> > >> > >> > >> > >> > Am Samstag, dem 26.11.2022 um 18:01 +0000 schrieb Dominik Riemer: >> >> Hi all,<br> >> >> >> >> the migration of our Jira issues to Github is completed.<br> >> >> >> >> All issues should be available here: >> >> [https://github.com/apache/streampipes/issues](https://github.com/apa >> >> che/streampipes/issues)<br> >> >> >> >> I hope that everything went well, in case there are any errors please >> >> feel free to reassign or modify these issues!<br> >> >> >> >> For the migration, we changed the notification settings to only send >> >> mails to >> >> [[email protected]](mailto:[email protected]) >> >> , sorry for the email spam in case you are subscribed to this list >> >> 😉<br> >> >> >> >> Thanks @Tim and Philipp for helping with the migration!<br> >> >> >> >> Cheers<br> >> >> Dominik<br> >>
