Re: Migration of OPS4J projects from Jira to Github
Grzegorz- Nice work! I think having the projects on GitHub will reduce efforts of the core contributors and will make it more accessible for new contributors as well. -Matt Pavlovich > On Feb 9, 2021, at 7:44 AM, Grzegorz Grzybek wrote: > > Hello > > Thanks to Jürgen Schmid, I was able to set up "ops4j-issues" GitHub account > with my current gmail address. I'll continue (if there are no objections) > with the migration using this account. > > kind regards > Grzegorz Grzybek > > 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://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/ops4j/org.ops4j.pax.jdbc/issues?q=is%3Aissue+is%3Aall >> >> These issues are taken into account: >> - Jira components, statuses, resolutions, issue types and labels are >> converted to Github labels >> - Jira versions are converted to Github milestones >> - The Jira fields that couldn't be mapped, are added below "---" line in >> the body of the GitHub issue (like vote/watch count, affected versions, >> fixed versions and attachments) >> - Attachment links still point to Jira, but inline images are properly >> displayed >> - Jira issues received "famous last comments" pointing to relevant Github >> issues >> - Jira screen schemes were migrated to a scheme, were you can't create >> new issue >> - HTML is converted to GitHub flavored markdown >> - all @xxx values (like @Service or @param) occurrences are properly >> quoted in backticks to prevent unnecessary GitHub mentions >> >> One remaining thing to do, which is almost ready is the conversion of Jira >> issue references to GitHub issue references - but I want to do proper cross >> references between Pax projects at GitHub - not only within single project. >> >> I was inspired by >> https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues >> blog post which made me aware of few things. >> >> *The biggest problem I see is that all the comments and all the issues are >> created by me... Even if the creation dates are preserved, I simply can't >> (and don't want to) get proper Jira - GitHub user mapping.* >> >> In case of Spring migration, they created special GitHub user, but I can't >> create another one using my gmail address. And I don't want to create weird >> fake addresses. >> >> You can check quite raw tools at >> https://github.com/ops4j/org.ops4j.tools/blob/master/jira2github/data/readme.adoc >> >> Before I proceed with "bigger" projects like Pax Logging or Pax Web, I'd >> appreciate your feedback. >> >> kind regards >> Grzegorz Grzybek >>
Re: Coming releases
Thanks for the update JB! Let me know if there is anything I can assist with. -Matt > On Feb 8, 2021, at 10:55 PM, Jean-Baptiste Onofre wrote: > > Hi everyone, > > Just a quick update about the release schedule: > > - Apache Karaf Decanter 2.7.0 will be on vote tonight or tomorrow morning. > I’m preparing the latest PR (adding HDFS and S3 appenders). > - Apache Karaf 4.3.1 and 4.2.11 should be on vote during next week end. I’m > doing the Jira triage right now. > > I will keep you posted soon ! > > Thanks, > Regards > JB > >> Le 24 janv. 2021 à 17:44, Jean-Baptiste Onofre a écrit : >> >> Hi guys, >> >> I was busy with ActiveMQ 5.16.1 release. >> >> So, new update about coming releases and some teasing ;) >> >> 1. I’m working on Decanter 2.7.0 release, I should be able to submit to vote >> by the end of the week >> 2. In the meantime, I’m preparing 4.3.1. Vote time target is in about 10 days >> >> About Karaf 5, I did good progress and I’m preparing a complete README.md in >> the repo as base for discussion. >> I will sync with François this week but I don’t want to hold the >> presentation for too long. >> >> Stay tuned ! >> >> Regards >> JB >> >>> Le 4 janv. 2021 à 06:08, Jean-Baptiste Onofre a écrit : >>> >>> Hi guys, >>> >>> Just to let you know that I have some delay for these releases, especially >>> 4.3.1. I did good progress but need some more days. >>> >>> I hope to submit these releases to vote by the end of the week/beginning of >>> next week. >>> >>> Regards >>> JB >>> Le 15 déc. 2020 à 14:40, Jean-Baptiste Onofre a écrit : Hi guys, As you have probably seen, Apache Karaf Decanter 2.6.0 is in vote. Now, I’m focus on Karaf 4.2.11 and 4.3.1 releases. I’m working on Pax Web releases now and then I will move forward on these releases preparation. Stay tuned ! Regards JB >>> >> >
Re: Migration of OPS4J projects from Jira to Github
Hello Thanks to Jürgen Schmid, I was able to set up "ops4j-issues" GitHub account with my current gmail address. I'll continue (if there are no objections) with the migration using this account. kind regards Grzegorz Grzybek 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://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/ops4j/org.ops4j.pax.jdbc/issues?q=is%3Aissue+is%3Aall > > These issues are taken into account: > - Jira components, statuses, resolutions, issue types and labels are > converted to Github labels > - Jira versions are converted to Github milestones > - The Jira fields that couldn't be mapped, are added below "---" line in > the body of the GitHub issue (like vote/watch count, affected versions, > fixed versions and attachments) > - Attachment links still point to Jira, but inline images are properly > displayed > - Jira issues received "famous last comments" pointing to relevant Github > issues > - Jira screen schemes were migrated to a scheme, were you can't create > new issue > - HTML is converted to GitHub flavored markdown > - all @xxx values (like @Service or @param) occurrences are properly > quoted in backticks to prevent unnecessary GitHub mentions > > One remaining thing to do, which is almost ready is the conversion of Jira > issue references to GitHub issue references - but I want to do proper cross > references between Pax projects at GitHub - not only within single project. > > I was inspired by > https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues > blog post which made me aware of few things. > > *The biggest problem I see is that all the comments and all the issues are > created by me... Even if the creation dates are preserved, I simply can't > (and don't want to) get proper Jira - GitHub user mapping.* > > In case of Spring migration, they created special GitHub user, but I can't > create another one using my gmail address. And I don't want to create weird > fake addresses. > > You can check quite raw tools at > https://github.com/ops4j/org.ops4j.tools/blob/master/jira2github/data/readme.adoc > > Before I proceed with "bigger" projects like Pax Logging or Pax Web, I'd > appreciate your feedback. > > kind regards > Grzegorz Grzybek >
Migration of OPS4J projects from Jira to Github
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/ops4j/org.ops4j.pax.jdbc/issues?q=is%3Aissue+is%3Aall These issues are taken into account: - Jira components, statuses, resolutions, issue types and labels are converted to Github labels - Jira versions are converted to Github milestones - The Jira fields that couldn't be mapped, are added below "---" line in the body of the GitHub issue (like vote/watch count, affected versions, fixed versions and attachments) - Attachment links still point to Jira, but inline images are properly displayed - Jira issues received "famous last comments" pointing to relevant Github issues - Jira screen schemes were migrated to a scheme, were you can't create new issue - HTML is converted to GitHub flavored markdown - all @xxx values (like @Service or @param) occurrences are properly quoted in backticks to prevent unnecessary GitHub mentions One remaining thing to do, which is almost ready is the conversion of Jira issue references to GitHub issue references - but I want to do proper cross references between Pax projects at GitHub - not only within single project. I was inspired by https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues blog post which made me aware of few things. *The biggest problem I see is that all the comments and all the issues are created by me... Even if the creation dates are preserved, I simply can't (and don't want to) get proper Jira - GitHub user mapping.* In case of Spring migration, they created special GitHub user, but I can't create another one using my gmail address. And I don't want to create weird fake addresses. You can check quite raw tools at https://github.com/ops4j/org.ops4j.tools/blob/master/jira2github/data/readme.adoc Before I proceed with "bigger" projects like Pax Logging or Pax Web, I'd appreciate your feedback. kind regards Grzegorz Grzybek
