Skip to content

[11.0][MIG] report_py3o (Work in Progress) - #217

Closed
BT-nfrei wants to merge 183 commits into
OCA:11.0from
brain-tec:11.0-mig-report_py3o
Closed

BT-nfrei wants to merge 183 commits into
OCA:11.0from
brain-tec:11.0-mig-report_py3o

Conversation

@BT-nfrei

Copy link
Copy Markdown

Hello everyone,
This PR is just a starting point for the migration of this module. At brain-tec, we like this module and we will contribute to its migration to 11.0.
After looking at the technical implementation in 10.0, we still have some doubts about the parser part (report_sxw/rml_parse, contexts). So it would be nice to get some inputs from the initial creators like @lmignon, @alexis-via or @guewen.
In 11.0, it seems quite clear that we have to move away from the SXW/RML technology. So I'm not sure if we should try to keep as much as possible from the current implementation or maybe get some inspiration from report_xlsx which is already migrated to 11.0.
So if you have inputs or advice, please let us know.

bt-admin and others added 30 commits October 8, 2017 01:13
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
@alexis-via

Copy link
Copy Markdown
Contributor

It's certainly not fun to do, but it would be great to get the latest improvements from v10, in particular the support for PDF export options (#211).

@ghost

ghost commented Aug 17, 2018

Copy link
Copy Markdown

Good morning @gmarczynski-ira @lmignon @alexis-via, thank you for the feedback, I will take some time for making the changes and for getting closer to the merge. As soon as I have the version updated I will comment the thread.

Thank you!

@gmarczynski-ira

Copy link
Copy Markdown

@BT-ccebrian after some more tests I find that the document merging does not work (neither for PDF nor for ODT). I will let you know if I find a solution for that.

bt-admin and others added 6 commits August 28, 2018 01:10
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
Syncing from upstream OCA/reporting-engine (11.0)
@njeudy

njeudy commented Oct 2, 2018

Copy link
Copy Markdown

@BT-ccebrian any news on this ?

@oca-clabot

Copy link
Copy Markdown

Hey @BT-nfrei, thank you for your Pull Request.

It looks like some users haven't signed our Contributor License Agreement, yet.
You can read and sign our full Contributor License Agreement here: http://odoo-community.org/page/cla
Here is a list of the users:

  • @BT-ccebrian (login unknown in OCA database)
  • @BT-nfrei (login unknown in OCA database)

Appreciation of efforts,
OCA CLAbot

ccebrian and others added 2 commits October 29, 2018 12:28
@ghost

ghost commented Nov 2, 2018

Copy link
Copy Markdown

Hi @ALL I have received news from above, we reached that this is a low-priority task for us.
Feel free for taking the migration task!

Thank you very much,
Best regards.

@lmignon

lmignon commented Nov 23, 2018

Copy link
Copy Markdown
Contributor

@BT-ccebrian I have to migrate this addon to V12. The first step is therefore to finalise the migration in V11. The commit history is a little bit ugly. Can I rewrite your commits to group all your changes into one ? I'll preserve the authorship.
Regards,

lmi

@bennals

bennals commented Dec 13, 2018

Copy link
Copy Markdown

@lmignon Do the decisions you've made about migrating this module to V12 mean that migrating it to V11 will be bypassed (for now at least)?

@lmignon

lmignon commented Dec 14, 2018

Copy link
Copy Markdown
Contributor

@bennals IMO you can take the code from #238, change the version into the manifest and that should work as is in V11. I've finally based the migration on the latest changes into V10.

@bennals

bennals commented Dec 14, 2018

Copy link
Copy Markdown

@lmignon ok, thanks, but should that be #258 rather than #238

@lmignon

lmignon commented Dec 15, 2018

Copy link
Copy Markdown
Contributor

@bennals Yes it's #258 rather than #238

@bennals

bennals commented Dec 16, 2018

Copy link
Copy Markdown

thanks!

@abdelhamid-attaby

Copy link
Copy Markdown

Hi everyone, this work is really amazing. Can I know the progress of this migration and what is the expected time to be migrated to V12.0 ?

@tbaden

tbaden commented May 1, 2019

Copy link
Copy Markdown
Member

is anybody working on this?
otherwise I think it would be quicker to backport the v12 migration #258

@tbaden

tbaden commented May 1, 2019

Copy link
Copy Markdown
Member

opened a new PR for this migration: #285
I'm grateful for any help.

@lmignon

lmignon commented May 2, 2019

Copy link
Copy Markdown
Contributor

@tbaden Indeed, it should be easier and quicker to backport chanegs from V12. I close this one.

@lmignon lmignon closed this May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.