> >since you've already made bundles publicly available for 2.2., we
> >have to release 2.2.1 as the `official' one -- redoing a 2.2
> >release would lead to confusion.
>
> it wasn't officially announced (no message at freetype-announce for
> example), I wouldn't care about this problem.
Ha! Making a package available to the public -- whether announced or
not -- counts as a release. We already had this problem, can you
remember? It doesn't hurt to release 2.2.1, does it?
Werner
_______________________________________________
Freetype-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype-devel
