[ANN] Prawn 0.6.3 Maintenance Release (Please Upgrade)

[Gregory Brown]

This is a bug fix release that fixes issues with some of the new
features in Prawn 0.6. It should not introduce any incompatibilities
with Prawn 0.6.1-2, so please upgrade immediately.

== Bugfixes since 0.6.2:

In prawn-core:

* Fixed a bug in annotations that prevented proper references from
being generated [#58] (jlh)
* Prawn::Reference on_encode() method removed, this should fix
marshaling issue in transactions. [#56] (Brad Ediger)
* Document extensions now work in inherited classes [#57] (Gregory Brown)

In prawn-layout:

* Cursor is now placed directly at the bottom of a table after
generation, as in Prawn 0.5.x (Gregory Brown)

In prawn-format:

* Fixed internal links in basic forrmatting example [#11] (jlh)
* width_of() and height_of() now should work as they did in 0.5.x
[#12,#13] (Gregory Brown)

As a result of fixes in core, Prawn::Format should work in classes
inherited from Prawn::Document, and links should now work again.

== Thanks again to our vigilant users for spotting these bugs and
reporting them.

- greg

[Valera]

Will Prawn-0.6.3 be released as a gem? Or maybe it's already released
as a gem and I can't find it?
The gems.rubyforge.org repo is still at 0.6.2...

If there are no plans to release 0.6.3 as a gem, I will just pull it
from GitHub.

[Gregory Brown]

On Thu, Nov 19, 2009 at 2:23 PM, Valera <vetr...@gmail.com> wrote:
> Will Prawn-0.6.3 be released as a gem? Or maybe it's already released
> as a gem and I can't find it?
> The gems.rubyforge.org repo is still at 0.6.2...

Looks like maybe they're busy with the gemcutter cutover.

0.6.3 is released as a gem and was working when I released it.

http://rubyforge.org/frs/?group_id=5849

I'll bug them if it isn't updated soon.

-greg

[Valera Trubachev]

Thanks. I forgot to check there, and instead only checked the gems.rubyforge.org site (http://gems.rubyforge.org/gems/prawn/versions), and this shows 0.6.2 as the latest version.

Sorry for taking up your time with this... :(

--

You received this message because you are subscribed to the Google Groups "Prawn" group.
To post to this group, send email to prawn...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/prawn-ruby?hl=.

[Gregory Brown]

On Thu, Nov 19, 2009 at 2:39 PM, Valera Trubachev <vetr...@gmail.com> wrote:
> Thanks. I forgot to check there, and instead only checked the
> gems.rubyforge.org site (http://gems.rubyforge.org/gems/prawn/versions), and
> this shows 0.6.2 as the latest version.
> Sorry for taking up your time with this... :(

I'm looking into how to use gemcutter for future releases, it looks
like because of a bug in our gemspec on prawn-security, I'll need to
contact them, but other than that, I should be able to get 0.6.3
migrated today.

[Gregory Brown]

Should be fixed now. Still need to get prawn-security migrated, but
that won't affect this install because we didn't bump its version for
0.6.3.
Gemcutter was nice, it just would have been even nicer for RubyForge
to you know... tell us the indexing was going off.

I'm sure it was probably announced somewhere other than Tom's twitter,
but frankly, an email out to all RubyForge users would have been best.

-greg

[Valera Trubachev]

Thanks a lot for taking care of this. I completely agree that RubyForge should have given a better notice to its users. 

[Gunnar Wolf]

Gregory Brown dijo [Thu, Nov 19, 2009 at 02:26:07PM -0500]:

> > Will Prawn-0.6.3 be released as a gem? Or maybe it's already released
> > as a gem and I can't find it?
> > The gems.rubyforge.org repo is still at 0.6.2...
>
> Looks like maybe they're busy with the gemcutter cutover.
>
> 0.6.3 is released as a gem and was working when I released it.
>
> http://rubyforge.org/frs/?group_id=5849
>
> I'll bug them if it isn't updated soon.

/me crosses fingers

Would you considering releasing also the .tar.gz files again?

Thanks a lot,

--
Gunnar Wolf • gw...@gwolf.org • (+52-55)5623-0154 / 1451-2244

[Gregory Brown]

On Tue, Nov 24, 2009 at 6:34 PM, Gunnar Wolf <gw...@gwolf.org> wrote:
> Gregory Brown dijo [Thu, Nov 19, 2009 at 02:26:07PM -0500]:

> /me crosses fingers
>
> Would you considering releasing also the .tar.gz files again?

Already done. http://github.com/sandal/prawn
Hit the download link and select the tag you want. I'll be more clear
about the existence of this Github feature in future releases.

-greg

[Gunnar Wolf]

Gregory Brown dijo [Tue, Nov 24, 2009 at 06:53:42PM -0500]:

> > /me crosses fingers
> >
> > Would you considering releasing also the .tar.gz files again?
>
> Already done. http://github.com/sandal/prawn
> Hit the download link and select the tag you want. I'll be more clear
> about the existence of this Github feature in future releases.

Yup, I am aware of this functionality - I'm even the maintainer of the
Github redirector:

http://githubredir.debian.net/github/sandal/prawn

I'll have to explain a bit more... As you might have guessed by now, I
am the Debian maintainer for Prawn (and to a certain degree, Ubuntu's
as well - Ubuntu syncs from Debian at least once for each of their
releases).

Now, a problem with Github's tarball service, as they relate to Prawn,
is that they do not include the git submodules - This means, I have to
separately download ttfunk and pdf-inspector. And, as they are not
tagged, I can only download the most current version (master), which
might yield suboptimal results - no warranty that you have ever tested
the specific combination.

Debian has recently adopted a new packaging format with which a single
package can be built off several orig.tar.gz files, so this fact by
itself should no longer be an inconvenience for us - but having a
point to which to relate for each component when building would be
most appreciated. Alternatively, possibly you could tag with the
corresponding Prawn releases in your ttfunk and pdf-inspector trees?

(Or even more alternatively, explain me why I'm not getting something
right ;-) )

Greetings,

[Gregory Brown]

On Tue, Nov 24, 2009 at 7:33 PM, Gunnar Wolf <gw...@gwolf.org> wrote:
> Gregory Brown dijo [Tue, Nov 24, 2009 at 06:53:42PM -0500]:
>> > /me crosses fingers
>> >
>> > Would you considering releasing also the .tar.gz files again?
>>
>> Already done. http://github.com/sandal/prawn
>> Hit the download link and select the tag you want.  I'll be more clear
>> about the existence of this Github feature in future releases.
>
> Yup, I am aware of this functionality - I'm even the maintainer of the
> Github redirector:
>
>    http://githubredir.debian.net/github/sandal/prawn
>
> I'll have to explain a bit more... As you might have guessed by now, I
> am the Debian maintainer for Prawn (and to a certain degree, Ubuntu's
> as well - Ubuntu syncs from Debian at least once for each of their
> releases).
>
> Now, a problem with Github's tarball service, as they relate to Prawn,
> is that they do not include the git submodules - This means, I have to
> separately download ttfunk and pdf-inspector. And, as they are not
> tagged, I can only download the most current version (master), which
> might yield suboptimal results - no warranty that you have ever tested
> the specific combination.

This is true, but if you do a git checkout on that tag, you can get
the proper submodule hash keys.

> Debian has recently adopted a new packaging format with which a single
> package can be built off several orig.tar.gz files, so this fact by
> itself should no longer be an inconvenience for us - but having a
> point to which to relate for each component when building would be
> most appreciated. Alternatively, possibly you could tag with the
> corresponding Prawn releases in your ttfunk and pdf-inspector trees?

Absolutely. I'll start this by tagging them with the same version
scheme of Prawn in 0.7

[Gunnar Wolf]

Gregory Brown dijo [Tue, Nov 24, 2009 at 07:37:27PM -0500]:

> > Now, a problem with Github's tarball service, as they relate to Prawn,
> > is that they do not include the git submodules - This means, I have to
> > separately download ttfunk and pdf-inspector. And, as they are not
> > tagged, I can only download the most current version (master), which
> > might yield suboptimal results - no warranty that you have ever tested
> > the specific combination.
>
> This is true, but if you do a git checkout on that tag, you can get
> the proper submodule hash keys.

Yup... Sadly we are still basing off the tarball. But I hope it will
be a transitory situation.

> > (...) having a point to which to relate for each component when

> > building would be most appreciated. Alternatively, possibly you
> > could tag with the corresponding Prawn releases in your ttfunk and
> > pdf-inspector trees?
>
> Absolutely. I'll start this by tagging them with the same version
> scheme of Prawn in 0.7

Great.

Now, on a related question: I see Prawn is currently a fast-moving
target. I know that around December, a Ubuntu long-term release will
be frozen (and it will most probably get Prawn 0.6). Debian will
freeze probably a couple of months later. What do you thinking about
having this version of Prawn distributed as part of our system for a
very long time? You have repeatedly stated that 0.4 is no longer
supported "for well over a month"... do you think it is wise to ship
pre-1.0 versions? Should I explicitly ask Ubuntu (and later Debian)
_not_ to ship it instead?

Thanks,

[Gregory Brown]

On Tue, Nov 24, 2009 at 8:01 PM, Gunnar Wolf <gw...@gwolf.org> wrote:

> Now, on a related question: I see Prawn is currently a fast-moving
> target. I know that around December, a Ubuntu long-term release will
> be frozen (and it will most probably get Prawn 0.6). Debian will
> freeze probably a couple of months later.

How much later? I can try to schedule a 1.0 for around then if it
coincides with our schedules. While I absolutely cannot guarantee a
release by that date, I planned to do 1.0 in Q1 of 2010 anyway, so if
it's like, late March, we might be able to swing it.

The benefit of Prawn 1.0 will be that the 1.0 API will likely be held
constant at least for those features that ship with 1.0.
Can't promise that either but that's the goal, and for that reason, i
think it'll be much more stable than some of the other projects out
there.

-greg

[Gunnar Wolf]

Gregory Brown dijo [Tue, Nov 24, 2009 at 08:06:16PM -0500]:

> On Tue, Nov 24, 2009 at 8:01 PM, Gunnar Wolf <gw...@gwolf.org> wrote:
>
> > Now, on a related question: I see Prawn is currently a fast-moving
> > target. I know that around December, a Ubuntu long-term release will
> > be frozen (and it will most probably get Prawn 0.6). Debian will
> > freeze probably a couple of months later.
>
> How much later?

When it is ready™.

Yup, it can be frustrating at times, but that's the way Debian
works. Once the freeze is declared (and before the new version comes
out, which will be inevitably several months later, as there are just
too many wrinkles to iron), I will need to ask for specific
release-manager approvals for any updates. And updates for new major
versions are often frowned upon.

> I can try to schedule a 1.0 for around then if it coincides with our
> schedules. While I absolutely cannot guarantee a release by that
> date, I planned to do 1.0 in Q1 of 2010 anyway, so if it's like,
> late March, we might be able to swing it.

We should not plan on dates for Debian... I guess that Ubuntu is just
out of the question. But anyway, would you prefer me to ask this
package not to enter 'testing' (which will become our release
candidate) at all before 1.0? Or is it better in your eyes to have
most exposure, and handle API changes for delighted users (such as
myself) as just a fact of life?

> The benefit of Prawn 1.0 will be that the 1.0 API will likely be held
> constant at least for those features that ship with 1.0.
> Can't promise that either but that's the goal, and for that reason, i
> think it'll be much more stable than some of the other projects out
> there.

Agree...