prawn
prawn copied to clipboard
prawnpdf
Release a version
Recently was integrated a PR who solves the font cache issue.
Is possible to release a version? The last release is from December 31.
https://rubygems.org/gems/prawn
A new release is required for proper dependencies for Ruby 3.1:
https://github.com/prawnpdf/prawn/commit/3658d5125c3b20eb11484c3b039ca6b89dc7d1b7
OK, I will push a new release before the snow melts away. But to set expectations right it won't happen in the next two weeks.
A prawn version 3.0 would be pretty neat eventually.
We have some competition e. g. hexapdf by gettalong. I have quite a lot of pdf-generation code in different projects, so I am re-evaluating old code every now and then. One advantage gettalong has is that he is quite active (and home boy in my city too! \o/ ).
@pointlessone If you need help with a new release, let me know! But no stress, when you have time, you have time..
@gettalong We've got a bunch of PRs open. I'd love some help with reviews. That extends to the broader community, too. Thank you.
@pointlessone any reason the master branch can't be released "as-is"? Are there any specific open PRs blocking the release?
I don't think any of the PRs are blocking release. It's just an area where I could use some help.
Perhaps we should decouple the two? Do a release, and then the good folks on this thread can chip in to help with PRs?
To be clear, I'm not waiting on PRs to merge before cutting a release. Prawn release is a somewhat complicated process so I need a solid block of time for it. That's the blocker. While we're waiting on that PRs might as well get reviewed.
@pointlessone I have created pull requests https://github.com/prawnpdf/prawn/pull/1242 and https://github.com/prawnpdf/pdf-core/pull/48 for open issues. Those are rather small changes and would be good candidates for merging before making the new release.
Is the master branch stable? Can I use it directly with gem 'prawn', github: 'prawnpdf/prawn' for now or is it better to just add gem 'matrix' to my Gemfile?
Generally we're trying not to break master branch. However, sometimes it might be a little confusing because master might depend on unreleased changes in ttfunk or pdf-core. You might need to use those from their master barnaches as well.
Prawn release is a somewhat complicated process so I need a solid block of time for it.
Is this process described somewhere and could parts of it be automated?
This is not described and hard to impossible to automate. The main issue is that there are at least three gems whose releases need to be coordinated. Dependencies are not strictly acyclic, too.
Is the master branch stable? Can I use it directly with
gem 'prawn', github: 'prawnpdf/prawn'for now or is it better to just addgem 'matrix'to my Gemfile?
@zavan Save yourself the future headache and just use the gem.
Here's to adding more noise in hopes it pushes this release out quicker
@shirts I would gladly accept a contribution that gets us there. Maybe start with something less ambitious than fully automated dependency resolution.
One Idea I muled over for a while is to have alpha/beta gem builds on every commit to master. I believe it might be a bit easier to achieve. GitHub Actions + GitHub Packages looks like a viable option.
@pointlessone please let us know the status of getting a new release out?
@johnnyshields Please see https://github.com/prawnpdf/ttfunk/issues/91#issuecomment-1110585178 which also applies here.
@gettalong the war is truly a catastrophe and I appreciate that it is disruptive for many.
That being said, there are highly qualified people in the community, e.g. @petergoldstein, who have volunteered to help with the maintainership of this gem. Can we please appoint someone to help move this forward and unblock issues?
@johnnyshields As far as I know only @pointlessone has all the permissions and means to do a release which is quite complicated involving multiple libraries. @petergoldstein volunteered to help out and he massively did but I don't think @pointlessone got to the point where he was able to explain the release process and assign permissions.
It happens in many projects. For instance, andlabs who used to maintain libui stopped adding code or reviewing code changes since about 2 years. Someone eventually overcame the inertia and added libui-ng, which is more active. I think having a project base with more different people in charge who can push at the least new patch sets in would be useful. They can focus on the quality of these patches and contributions which worked for libui-ng very well.
Is any news about this issue?
Not really. The war is still on.
Maybe a new release before the snow falls this time? 😁
The snow has fallen over here so that ship has sailed. Maybe Christmas? 😉
Now seriously. I will spend some time on Prawn this month. To set expectations properly: that is not a promise of a release by any specific date.