So when there will be next release. Since now there are 100+ commits in develop branch and no release. It's sad.
Charius, we do not have an official maintainer (if you want you can apply for that position). There are lots of patches, and they all need to be tested, marked as useful, marked as incomplete or missing functions, or missing testcases (which you can pull-request to those, before they get merged into PHPWord), etc. That work can be done by enthousiasts like us. For example: there are 3 versions of TemplateProcessor Images insertions. Which would you choose? Just go into the patches, test them, and comment on their usefulness, the name of the functions, the ideas to make it easier on the user later on, this way the patch gets better.
@FBnil thanks for the answer and information!
this issue related with #848
So I close this one
@FBnil
we do not have an official maintainer
What about this comment?
https://github.com/PHPOffice/PHPWord/issues/948#issuecomment-305099226
I see @troosan in the dev branch. It would be nice to get some clarification. I'm starting to lose my confidence in this project.
@connerbw the situation is really interesting, thanks for your comment. Maybe @troosan or @FBnil will clarify this for all of us.
@connerbw @Charius hmm... you are quite right, I have been spreading lies. (which means I need to read closed messages too...).
My apologies @troosan ! @troosan has been committing and closing steadily through the months see the closing dates for
Closed issues for milestone 0.14.0
... a bit of a quiet person (but replying to issues is not the task of the maintainer). Now, it looks like all bugs (marked for that milestone) are closed, but the sourcecode in dev Still shows some nasty errors https://scrutinizer-ci.com/g/PHPOffice/PHPWord/issues which need to be cleaned up a bit.
Which also leaves us with a heap of pull requests and feature requests that could be considered part of the core. pushed to the next milestone... far into the future.
I have updated my profile picture accordingly. (oh, the shame)
Hi, indeed, I'm not as volubile as @FBnil :-) (thanks for the support BTW)
Anyway, I'm trying to go through the PR (there are a lot) and integrating the ones that can easily be merged and that do not risk breaking to much things.
As you can see I updated the copyright to 2010-2017, so I'm still hoping to publish 0.14 as a Christmas present!
After that I guess we'll have to have a release dedicated to all the nice changes done on the TemplateProcessor. I'm a bit nervous about those changes as there is virtually 0 unit tests covering that part.
@troosan thanks for your response, glad to see your answer!
Most helpful comment
Hi, indeed, I'm not as volubile as @FBnil :-) (thanks for the support BTW)
Anyway, I'm trying to go through the PR (there are a lot) and integrating the ones that can easily be merged and that do not risk breaking to much things.
As you can see I updated the copyright to 2010-2017, so I'm still hoping to publish 0.14 as a Christmas present!
After that I guess we'll have to have a release dedicated to all the nice changes done on the TemplateProcessor. I'm a bit nervous about those changes as there is virtually 0 unit tests covering that part.