rzybek
> >
> > wt., 9 lut 2021 o 12:51 Grzegorz Grzybek
> napisał(a):
> >
> >> Hello
> >>
> >> I'd like to let you know that I've migrated these projects from OPS4J
> Jira
> >> to Github:
> >> - PAX TRANSX:
> >>
> https://g
Hello
>
> I'd like to let you know that I've migrated these projects from OPS4J Jira
> to Github:
> - PAX TRANSX:
> https://github.com/ops4j/org.ops4j.pax.transx/issues?q=is%3Aissue+is%3Aall
> - PAX JMS:
> https://github.com/ops4j/org.ops4j.pax.jms/issues?q=is%3Aiss
Hello
I'd like to let you know that I've migrated these projects from OPS4J Jira
to Github:
- PAX TRANSX:
https://github.com/ops4j/org.ops4j.pax.transx/issues?q=is%3Aissue+is%3Aall
- PAX JMS:
https://github.com/ops4j/org.ops4j.pax.jms/issues?q=is%3Aissue+is%3Aall
- PAX JDBC:
https://github.com
ps4j.tools/tree/master/jira2github>
> [3]: https://github.com/grgrzybek/test2github/issues
> <https://github.com/grgrzybek/test2github/issues>
> [4]: https://gist.github.com/jonmagic/5282384165e0f86ef105
> <https://gist.github.com/jonmagic/5282384165e0f86ef105>
> [5]:
>
thub>
[3]: https://github.com/grgrzybek/test2github/issues
<https://github.com/grgrzybek/test2github/issues>
[4]: https://gist.github.com/jonmagic/5282384165e0f86ef105
<https://gist.github.com/jonmagic/5282384165e0f86ef105>
[5]:
https://spring.io/blog/2019/01/15/spring-framework-s-
ng.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues
--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
---
You received this message because you are subscribed to the Google Groups
"OPS4J" group.
To unsubscribe from this group and s
On Monday, April 27, 2020 9:15:16 AM CEST 'Achim Nierbeck' via OPS4J wrote:
> Hi,
>
> in the past we needed to do a "lock-down" on self-registration for the Jira
> Instance due to tremendous amount of spam in Jira Issues and on the
> confluence pages.
> This increases the burden for people to
+1 to change to github. We need some rules though to be able to mark issues
as fixed in a certain release.
(I think it can be done with tags on the issues).
Christian
Am Mo., 27. Apr. 2020 um 09:15 Uhr schrieb 'Achim Nierbeck' via OPS4J <
ops4j@googlegroups.com>:
> Hi,
>
> in the past we needed
It make sense to use Github for all.
+1
regards,
*François Papon*
*papon...@gmail.com *
Le lun. 27 avr. 2020 à 10:12, 'Christoph Läubrich' via OPS4J <
ops4j@googlegroups.com> a écrit :
> +1 from me as we essentilally haven't used the real power of jira over
> the past years and it was a
+1 from me as we essentilally haven't used the real power of jira over
the past years and it was a little bit brittle to register for two services
Am 27.04.20 um 09:57 schrieb Grzegorz Grzybek:
+1 - especially for commit-issue references!
--
--
--
OPS4J - http://www.ops4j.org
+1 - especially for commit-issue references!
But how about Atlassian ↔ Ops4J agreement? (was there any?)
regards
Grzegorz Grzybek
pon., 27 kwi 2020 o 09:36 Jean-Baptiste Onofré <
jeanbaptiste.ono...@gmail.com> napisał(a):
> +1 to use github tools.
>
> Regards
> JB
>
> On Mon, Apr 27, 2020 at
+1 to use github tools.
Regards
JB
On Mon, Apr 27, 2020 at 9:15 AM 'Achim Nierbeck' via OPS4J <
ops4j@googlegroups.com> wrote:
> Hi,
>
> in the past we needed to do a "lock-down" on self-registration for the
> Jira Instance due to tremendous amount of spam in Jira Issues and on the
> confluence
Hi,
in the past we needed to do a "lock-down" on self-registration for the Jira
Instance due to tremendous amount of spam in Jira Issues and on the
confluence pages.
This increases the burden for people to file new Issues :(
How about changing to github completely for issues and documentation?
13 matches
Mail list logo