Re: OPS4J projects migration from OPS4J (cloud) Jira to GitHub issues
Thanks! > On Feb 25, 2021, at 3:41 AM, Grzegorz Grzybek wrote: > > Hello > > I'm proud to announce that I've just finished the migration of OPS4J Jira > issues to GitHub. We were discussing this ~half a year ago. > > For each Jira issue I've migrated: > - description and comments preserving html (converted to markdown), > creation dates and authors (although not pointing to GH users, which is > obvious) > - Jira statuses, issue types, components and labels as GitHub labels > - Jira fix versions as GitHub milestones with due date and closed status > - Images > - Attachments > - Jira inter-project references as real GitHub references - cross project! > (i.e., PAXWEB issues referencing PAXLOGGING issues are changed to working > GitHub issue references between org.ops4j.pax.web to org.ops4j.pax.logging > projects) > > These projects were fully migrated: > - TOOLS = ops4j/org.ops4j.tools > - PAXJMS = ops4j/org.ops4j.pax.jms > - PAXTRANSX = ops4j/org.ops4j.pax.transx > - PAXJDBC = ops4j/org.ops4j.pax.jdbc > - PAXTIPI = ops4j/org.ops4j.pax.tipi > - PAXLOGGING = ops4j/org.ops4j.pax.logging > - PAXEXAM = ops4j/org.ops4j.pax.exam2 > - PAXURL = ops4j/org.ops4j.pax.url > - PAXTB = ops4j/org.ops4j.pax.tinybundles > - BASE = ops4j/org.ops4j.base > - PAXSB = ops4j/org.ops4j.pax.swissbox > - PAXCDI = ops4j/org.ops4j.pax.cdi > - PAXRUNNER = ops4j/org.ops4j.pax.runner > - PAXSCANNER = ops4j/org.ops4j.pax.scanner > - PAXCONSTRUCT = ops4j/org.ops4j.pax.construct > - PAXSHIRO = ops4j/org.ops4j.pax.shiro > - PAXWEB = ops4j/org.ops4j.pax.web > > These GitHub projects have not their issues migrated from Jira to GitHub > (usually they're inactive, or I simply didn't work on them before), though > if you like, I may migrate them: > - ops4j/exam-eclipse > - ops4j/git-helpers > - ops4j/ops4j.github.io > - ops4j/ops4j-infra > - ops4j/org.ops4j.dadl > - ops4j/org.ops4j.mpjp > - ops4j/org.ops4j.orient > - ops4j/org.ops4j.pax.ace-maven-plugin > - ops4j/org.ops4j.pax.carrot > - ops4j/org.ops4j.pax.clapper > - ops4j/org.ops4j.pax.confman > - ops4j/org.ops4j.pax.exam1 > - ops4j/org.ops4j.pax.jmx > - ops4j/org.ops4j.pax.jpa > - ops4j/org.ops4j.pax.monitoradmin > - ops4j/org.ops4j.pax.remote > - ops4j/org.ops4j.pax.useradmin > - ops4j/org.ops4j.pax.vaadin > - ops4j/org.ops4j.pax.warp > - ops4j/org.ops4j.pax.wicket > - ops4j/org.ops4j.ramler > - ops4j/org.ops4j.resources > - ops4j/org.ops4j.xvisitor > - ops4j/pax-repository > - ops4j/peaberry > > Kind regards and I invite you to contribute to OPS4J projects at GitHub ;) > Grzegorz Grzybek
Re: OPS4J projects migration from OPS4J (cloud) Jira to GitHub issues
Hi, Thank you very much Grzegorz for all the great work! regards, François fpa...@apache.org Le 25/02/2021 à 10:41, Grzegorz Grzybek a écrit : > Hello > > I'm proud to announce that I've just finished the migration of OPS4J Jira > issues to GitHub. We were discussing this ~half a year ago. > > For each Jira issue I've migrated: > - description and comments preserving html (converted to markdown), > creation dates and authors (although not pointing to GH users, which is > obvious) > - Jira statuses, issue types, components and labels as GitHub labels > - Jira fix versions as GitHub milestones with due date and closed status > - Images > - Attachments > - Jira inter-project references as real GitHub references - cross project! > (i.e., PAXWEB issues referencing PAXLOGGING issues are changed to working > GitHub issue references between org.ops4j.pax.web to org.ops4j.pax.logging > projects) > > These projects were fully migrated: > - TOOLS = ops4j/org.ops4j.tools > - PAXJMS = ops4j/org.ops4j.pax.jms > - PAXTRANSX = ops4j/org.ops4j.pax.transx > - PAXJDBC = ops4j/org.ops4j.pax.jdbc > - PAXTIPI = ops4j/org.ops4j.pax.tipi > - PAXLOGGING = ops4j/org.ops4j.pax.logging > - PAXEXAM = ops4j/org.ops4j.pax.exam2 > - PAXURL = ops4j/org.ops4j.pax.url > - PAXTB = ops4j/org.ops4j.pax.tinybundles > - BASE = ops4j/org.ops4j.base > - PAXSB = ops4j/org.ops4j.pax.swissbox > - PAXCDI = ops4j/org.ops4j.pax.cdi > - PAXRUNNER = ops4j/org.ops4j.pax.runner > - PAXSCANNER = ops4j/org.ops4j.pax.scanner > - PAXCONSTRUCT = ops4j/org.ops4j.pax.construct > - PAXSHIRO = ops4j/org.ops4j.pax.shiro > - PAXWEB = ops4j/org.ops4j.pax.web > > These GitHub projects have not their issues migrated from Jira to GitHub > (usually they're inactive, or I simply didn't work on them before), though > if you like, I may migrate them: > - ops4j/exam-eclipse > - ops4j/git-helpers > - ops4j/ops4j.github.io > - ops4j/ops4j-infra > - ops4j/org.ops4j.dadl > - ops4j/org.ops4j.mpjp > - ops4j/org.ops4j.orient > - ops4j/org.ops4j.pax.ace-maven-plugin > - ops4j/org.ops4j.pax.carrot > - ops4j/org.ops4j.pax.clapper > - ops4j/org.ops4j.pax.confman > - ops4j/org.ops4j.pax.exam1 > - ops4j/org.ops4j.pax.jmx > - ops4j/org.ops4j.pax.jpa > - ops4j/org.ops4j.pax.monitoradmin > - ops4j/org.ops4j.pax.remote > - ops4j/org.ops4j.pax.useradmin > - ops4j/org.ops4j.pax.vaadin > - ops4j/org.ops4j.pax.warp > - ops4j/org.ops4j.pax.wicket > - ops4j/org.ops4j.ramler > - ops4j/org.ops4j.resources > - ops4j/org.ops4j.xvisitor > - ops4j/pax-repository > - ops4j/peaberry > > Kind regards and I invite you to contribute to OPS4J projects at GitHub ;) > Grzegorz Grzybek >
OPS4J projects migration from OPS4J (cloud) Jira to GitHub issues
Hello I'm proud to announce that I've just finished the migration of OPS4J Jira issues to GitHub. We were discussing this ~half a year ago. For each Jira issue I've migrated: - description and comments preserving html (converted to markdown), creation dates and authors (although not pointing to GH users, which is obvious) - Jira statuses, issue types, components and labels as GitHub labels - Jira fix versions as GitHub milestones with due date and closed status - Images - Attachments - Jira inter-project references as real GitHub references - cross project! (i.e., PAXWEB issues referencing PAXLOGGING issues are changed to working GitHub issue references between org.ops4j.pax.web to org.ops4j.pax.logging projects) These projects were fully migrated: - TOOLS = ops4j/org.ops4j.tools - PAXJMS = ops4j/org.ops4j.pax.jms - PAXTRANSX = ops4j/org.ops4j.pax.transx - PAXJDBC = ops4j/org.ops4j.pax.jdbc - PAXTIPI = ops4j/org.ops4j.pax.tipi - PAXLOGGING = ops4j/org.ops4j.pax.logging - PAXEXAM = ops4j/org.ops4j.pax.exam2 - PAXURL = ops4j/org.ops4j.pax.url - PAXTB = ops4j/org.ops4j.pax.tinybundles - BASE = ops4j/org.ops4j.base - PAXSB = ops4j/org.ops4j.pax.swissbox - PAXCDI = ops4j/org.ops4j.pax.cdi - PAXRUNNER = ops4j/org.ops4j.pax.runner - PAXSCANNER = ops4j/org.ops4j.pax.scanner - PAXCONSTRUCT = ops4j/org.ops4j.pax.construct - PAXSHIRO = ops4j/org.ops4j.pax.shiro - PAXWEB = ops4j/org.ops4j.pax.web These GitHub projects have not their issues migrated from Jira to GitHub (usually they're inactive, or I simply didn't work on them before), though if you like, I may migrate them: - ops4j/exam-eclipse - ops4j/git-helpers - ops4j/ops4j.github.io - ops4j/ops4j-infra - ops4j/org.ops4j.dadl - ops4j/org.ops4j.mpjp - ops4j/org.ops4j.orient - ops4j/org.ops4j.pax.ace-maven-plugin - ops4j/org.ops4j.pax.carrot - ops4j/org.ops4j.pax.clapper - ops4j/org.ops4j.pax.confman - ops4j/org.ops4j.pax.exam1 - ops4j/org.ops4j.pax.jmx - ops4j/org.ops4j.pax.jpa - ops4j/org.ops4j.pax.monitoradmin - ops4j/org.ops4j.pax.remote - ops4j/org.ops4j.pax.useradmin - ops4j/org.ops4j.pax.vaadin - ops4j/org.ops4j.pax.warp - ops4j/org.ops4j.pax.wicket - ops4j/org.ops4j.ramler - ops4j/org.ops4j.resources - ops4j/org.ops4j.xvisitor - ops4j/pax-repository - ops4j/peaberry Kind regards and I invite you to contribute to OPS4J projects at GitHub ;) Grzegorz Grzybek
