Quote:
Originally Posted by Rev. Bob
Have you listed yourself in the credits? If not, please do so to credit yourself for the port, and please add an entry to the changelog to document this update.
|
I don't need credit. I will update the change log when it is released.
Quote:
|
I would also suggest not considering the beta version number increments as “real,” since they were only used for testing and not released as official versions. I’m not at my computer to verify the current release version number (the first post in this thread lists two entries for 1.4.0, leading me not to trust that), but I would suggest bumping the current version number to the next 1.x.0 version for this one. So, if you’d picked 1.5.2 (the first of your betas I see) because the current one is 1.5, let’s go with 1.6.0.
|
That is what I was planning to do.
Quote:
|
I’m still on 4.23 myself, so I’ll try to grab this tonight and test it using my usual CLI settings to see how it goes. Assuming all goes well – and if nobody’s run this on a Google Play book or a Kobo book yet, please speak up so I can be sure to test that – releasing it Tuesday or Wednesday sounds like a fine plan.
|
I agree, assuming by then I fix the problem @JSWolf found.