1.0 Status Update?

[Gregory Brown]

Hi everyone!

Question for the core team: what exactly needs to be done before 1.0 is released?

I know we've been tracking 1.0 blockers in the bug tracker, but I'd like to see
a checklist of sorts for everything that needs to be done, not just technical issues.

If you guys can provide me with one, I can try to free up some time to help
push things along. While I'm not sure how much time I'll have,
I sent in a pull request adding a foreword to the manual as a sign of
good faith. :-)

-greg

[Brad Ediger]

On Tue, Mar 5, 2013 at 10:59 PM, Gregory Brown
<gregory...@gmail.com> wrote:
> Question for the core team: what exactly needs to be done before 1.0 is
> released?

Here's my collection of TODOs for Prawn 1.0:

- Sweep issue tracker for blocking issues
- Audit licensing of everything that ships with Prawn (images, fonts,
etc.) and find replacements as necessary
- Clarify the post-1.0 Ruby version support policy
- Co-release 1.0 with 0.13.0, which will support Ruby 1.8 but will not
backport new features
- Remove 1.8 support from master
- Read through the manual to make sure everything hangs together
- Write a CHANGELOG and release notes

Other suggestions welcome.

Brad

[Brett Neumeier]

On Tue, May 7, 2013 at 2:46 PM, Brad Ediger <brad....@madriska.com> wrote:

On Tue, Mar 5, 2013 at 10:59 PM, Gregory Brown
<gregory...@gmail.com> wrote:
> Question for the core team: what exactly needs to be done before 1.0 is
> released?

Here's my collection of TODOs for Prawn 1.0:

[...]

 

Has there been any progress on getting those things squared away? It looks like 1.0.0.rc1 was cut about two years ago, and rc2 was cut five months ago. Perhaps an actual 1.0 release could be done?

I see that the issue tracker has two blockers listed (licensing sweep and upload final 1.0 manual), both of which were filed two years ago. Is there something I could help with to get some traction on those?

--
Brett Neumeier (bneu...@gmail.com)