You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streampipes.apache.org by Dominik Riemer <do...@bytefabrik.ai> on 2022/11/26 18:01:21 UTC

Issue migration completed

Hi all,

the migration of our Jira issues to Github is completed.

All issues should be available here: https://github.com/apache/streampipes/issues

I hope that everything went well, in case there are any errors please feel free to reassign or modify these issues!

For the migration, we changed the notification settings to only send mails to issues@streampipes.apache.org, sorry for the email spam in case you are subscribed to this list πŸ˜‰

Thanks @Tim and Philipp for helping with the migration!

Cheers
Dominik


Re: Issue migration completed

Posted by Tim <bo...@posteo.de>.
Hi all,

@dominik, thanks a lot for your work, looks really great so far!

@florian, this is not yet in please. I'll write a how-to in the upcoming 
days.

Best
Tim

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/apache/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 
>> [issues@streampipes.apache.org](mailto:issues@streampipes.apache.org), 
>> 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>

AW: Issue migration completed

Posted by Philipp Zehnder <ph...@bytefabrik.ai>.
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 <bo...@posteo.de>
Datum: Montag, 28. November 2022 um 20:55
An: dev@streampipes.apache.org <de...@streampipes.apache.org>
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 <do...@bytefabrik.ai> 于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 <bo...@posteo.de>
>> Sent: Sunday, November 27, 2022 9:22 PM
>> To: dev@streampipes.apache.org
>> 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
>> >> [issues@streampipes.apache.org](mailto:issues@streampipes.apache.org)
>> >> , 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>
>>

Re: Issue migration completed

Posted by Florian Micklich <mi...@apache.org>.
Hi Tim,

thanks as well for the good documentation.

But I have a short question.
I want to create a subtask here [1]
but the option convert to issue does not appear like as described here [2]
Do I miss something? Is there also another option?

Greetings
Florian

[1] https://github.com/apache/streampipes/issues/795
[2] https://cwiki.apache.org/confluence/display/STREAMPIPES/Work+with+GitHub+issues?preview=/235835711/235835721/add-subtask.gif

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

Re: Issue migration completed

Posted by Tim <bo...@posteo.de>.
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 <do...@bytefabrik.ai> 于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 <bo...@posteo.de>
>> Sent: Sunday, November 27, 2022 9:22 PM
>> To: dev@streampipes.apache.org
>> 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
>> >> [issues@streampipes.apache.org](mailto:issues@streampipes.apache.org)
>> >> , 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>
>> 

Re: Issue migration completed

Posted by Xin Wang <da...@gmail.com>.
Thanks for the great work!

Dominik Riemer <do...@bytefabrik.ai> 于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 <bo...@posteo.de>
> Sent: Sunday, November 27, 2022 9:22 PM
> To: dev@streampipes.apache.org
> 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
> >> [issues@streampipes.apache.org](mailto:issues@streampipes.apache.org)
> >> , 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>
>


-- 
Thanks,
Xin

RE: Issue migration completed

Posted by Dominik Riemer <do...@bytefabrik.ai>.
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 <bo...@posteo.de> 
Sent: Sunday, November 27, 2022 9:22 PM
To: dev@streampipes.apache.org
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 
>> [issues@streampipes.apache.org](mailto:issues@streampipes.apache.org)
>> , 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>

Re: Issue migration completed

Posted by Tim <bo...@posteo.de>.
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/apache/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 
>> [issues@streampipes.apache.org](mailto:issues@streampipes.apache.org), 
>> 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>

Re: Issue migration completed

Posted by Florian Micklich <mi...@apache.org>.
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/apache/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 [issues@streampipes.apache.org](mailto:issues@streampipes.apache.org), 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>