You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@hop.apache.org by Hans Van Akelyen <ha...@gmail.com> on 2022/11/29 10:50:45 UTC
Github Issues have been activated
Dear Users and developers,
As discussed in previous threads we will be moving to GitHub issues for
better inclusion and follow up of our work.
We will not be migrating the current Jira issues to GitHub. We will use
this opportunity to cleanup the existing issues, many of them have become
invalid.
The creation of tickets in Jira is still possible but will be suspended in
the near future. A new release version has been created on Jira called
“Migrated to GHI” we will attach tickets that have been moved over to this
release version and add a comment to the relevant GHI.
If you wish to help us, feel free to duplicate your issues from Jira in
Github issues and leave a comment with the link to the issue, then we will
close them up in Jira.
Our current release 2.2 will still be managed/reported using a Jira
release, all subsequent releases will be done solely via GitHub.
In the coming days all documentation will be updated to reflect the changed
process.
Cheers,
Hans
Re: Github Issues have been activated
Posted by Ricardo Gouvea <ri...@openin.com.br>.
Ok Hans, thanks for the information
Em ter., 29 de nov. de 2022 às 07:51, Hans Van Akelyen <
hans.van.akelyen@gmail.com> escreveu:
> Dear Users and developers,
>
> As discussed in previous threads we will be moving to GitHub issues for
> better inclusion and follow up of our work.
> We will not be migrating the current Jira issues to GitHub. We will use
> this opportunity to cleanup the existing issues, many of them have become
> invalid.
>
> The creation of tickets in Jira is still possible but will be suspended in
> the near future. A new release version has been created on Jira called
> “Migrated to GHI” we will attach tickets that have been moved over to this
> release version and add a comment to the relevant GHI.
>
> If you wish to help us, feel free to duplicate your issues from Jira in
> Github issues and leave a comment with the link to the issue, then we will
> close them up in Jira.
>
> Our current release 2.2 will still be managed/reported using a Jira
> release, all subsequent releases will be done solely via GitHub.
>
> In the coming days all documentation will be updated to reflect the changed
> process.
>
> Cheers,
> Hans
>
--
<https://www.openin.com.br>
Patrocinadora Oficial do
Pentaho Day 2019
Ricardo Gouvêa
CEO
ricardo@openin.com.br
Mobile: +55 11 9 9638-9238
Openin - Your Partner in Data
www.openin.com.br
[image: Openin no Linkedin] [image: Openin no Facebook]
<https://www.facebook.com/Openinbr/> [image: Openin no Instagram]
<https://www.instagram.com/openinbr/> [image: Openin no Twitter]
<https://twitter.com/OpeninBigData> [image: Openin no Youtube]
<https://www.youtube.com/openinbigdata>
Re: Github Issues have been activated
Posted by Ricardo Gouvea <ri...@openin.com.br>.
Ok Hans, thanks for the information
Em ter., 29 de nov. de 2022 às 07:51, Hans Van Akelyen <
hans.van.akelyen@gmail.com> escreveu:
> Dear Users and developers,
>
> As discussed in previous threads we will be moving to GitHub issues for
> better inclusion and follow up of our work.
> We will not be migrating the current Jira issues to GitHub. We will use
> this opportunity to cleanup the existing issues, many of them have become
> invalid.
>
> The creation of tickets in Jira is still possible but will be suspended in
> the near future. A new release version has been created on Jira called
> “Migrated to GHI” we will attach tickets that have been moved over to this
> release version and add a comment to the relevant GHI.
>
> If you wish to help us, feel free to duplicate your issues from Jira in
> Github issues and leave a comment with the link to the issue, then we will
> close them up in Jira.
>
> Our current release 2.2 will still be managed/reported using a Jira
> release, all subsequent releases will be done solely via GitHub.
>
> In the coming days all documentation will be updated to reflect the changed
> process.
>
> Cheers,
> Hans
>
--
<https://www.openin.com.br>
Patrocinadora Oficial do
Pentaho Day 2019
Ricardo Gouvêa
CEO
ricardo@openin.com.br
Mobile: +55 11 9 9638-9238
Openin - Your Partner in Data
www.openin.com.br
[image: Openin no Linkedin] [image: Openin no Facebook]
<https://www.facebook.com/Openinbr/> [image: Openin no Instagram]
<https://www.instagram.com/openinbr/> [image: Openin no Twitter]
<https://twitter.com/OpeninBigData> [image: Openin no Youtube]
<https://www.youtube.com/openinbigdata>
R: Github Issues have been activated
Posted by Sergio Ramazzina <se...@serasoft.it>.
Hi Hans,
thanks for the info.
Cheers
Sergio
**Sergio Ramazzina**
** _Senior Solution Architect_**
---
. |
| Via Milano, 78 - 20013 Magenta (MI)
Phone: +39 02 92979810
[sergio.ramazzina@serasoft.it](mailto:%7BE-mail%7D) -
[www.serasoft.it](https://www.serasoft.it)
Le informazioni trasmesse attraverso la presente e-mail ed i suoi allegati
sono diretti esclusivamente al destinatario e devono ritenersi riservati con
divieto di diffusione e di uso nei giudizi salva espressa autorizzazione; nel
caso di utilizzo senza espressa autorizzazione, verra effettuata denuncia al
competente Consiglio dell'Ordine per violazione dell'art. 28 del Codice
Deontologico. La diffusione e la comunicazione da parte di soggetto diverso
dal destinatario e vietata dall'art. 616 e ss. c.p. e dal d. l.vo n. 196/03.
Se la presente e-mail ed si suoi allegati fossero stati ricevuti per errore da
persona diversa dal destinatario siete pregati di distruggere tutto quanto
ricevuto e di informare il mittente con lo stesso mezzo.
\-----Messaggio originale-----
Da: Hans Van Akelyen <ha...@gmail.com>
Inviato: martedì 29 novembre 2022 11:51
A: users@hop.apache.org; dev@hop.apache.org
Oggetto: Github Issues have been activated
Dear Users and developers,
As discussed in previous threads we will be moving to GitHub issues for better
inclusion and follow up of our work.
We will not be migrating the current Jira issues to GitHub. We will use this
opportunity to cleanup the existing issues, many of them have become invalid.
The creation of tickets in Jira is still possible but will be suspended in the
near future. A new release version has been created on Jira called “Migrated
to GHI” we will attach tickets that have been moved over to this release
version and add a comment to the relevant GHI.
If you wish to help us, feel free to duplicate your issues from Jira in Github
issues and leave a comment with the link to the issue, then we will close them
up in Jira.
Our current release 2.2 will still be managed/reported using a Jira release,
all subsequent releases will be done solely via GitHub.
In the coming days all documentation will be updated to reflect the changed
process.
Cheers,
Hans