What can I do to help get a release out?

[hvds]

I'd really love to see a release with some of the bugfixes and new features. What can I do to help make that happen?

I have a lot of experience with rebasing in git, so if there are partial changes that are not ready to go out, I might be able to produce a branch which moves those to the end of the history.

If there are tests missing for any function I understand I could try adding those.

If there is code that absolutely must be written, I could try to write it.

If the Changelog has gaps, I could attempt to fill them in.

What is needed, how can I help?

[danaj]

The number one thing is just this -- poke me.

The main holdup is testing. I don't want to push out a release that hasn't been tested on a variety of platforms. This means I should get my gnu compiler farm account reinstated so I can test on those machines, and then figure out the best naming method for trial cpan releases (releases that won't show up for normal updates, but get tested by cpan testers).

I don't believe there is anything big that has to be done for a release. There are always a million todo features of various importance, but nothing part-way. The GMP backend has a number of small things that would be nice to get in this release, but there is no reason they should hold anything up.

[danaj]

I'll take a look tomorrow at where things are and try to make a list.

[hvds]

Thanks, I'll try to remember to keep poking.

[hvds]

Poke: I'm starting to build up quite a few dependencies on bug fixes and new features that haven't been released, so I'm really eager to see a release happen.

I'll take a look tomorrow at where things are and try to make a list.

Do we have a list?