<html><body><div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:10px"><div style="" class=""><span style="" class="">Albert,</span></div><div class="" style="color: rgb(0, 0, 0); font-size: 10px; font-family: Courier New,courier,monaco,monospace,sans-serif; background-color: transparent; font-style: normal;"><br style="" class=""><span style="" class=""></span></div><div class="" style="color: rgb(0, 0, 0); font-size: 10px; font-family: Courier New,courier,monaco,monospace,sans-serif; background-color: transparent; font-style: normal;"><span style="" class="">in the two years i've been following Poppler, I think youve been amazing. A big THANKS is in order. <br style="" class=""></span></div><div class="" style="color: rgb(0, 0, 0); font-size: 10px; font-family: Courier New,courier,monaco,monospace,sans-serif; background-color: transparent; font-style: normal;"><br style=""
class=""><span style="" class=""></span></div><div class="" style="color: rgb(0, 0, 0); font-size: 10px; font-family: Courier New,courier,monaco,monospace,sans-serif; background-color: transparent; font-style: normal;"><span style="" class="">I'm guessing that most of the Poppler users are using Poppler though Python or Ruby bindings. I use Poppler through Ruby bindigs which are behind current release. The current Ruby Poppler Gem 2.2.0 <a style="" class="" href="http://rubygems.org/gems/poppler">http://rubygems.org/gems/poppler</a><br style="" class=""></span></div><div style="" class="">is using Poppler version 0.18.4 <br style="" class=""></div><div style="" class=""><a style="" class="" href="http://ruby-gnome2.sourceforge.jp/hiki.cgi?Poppler#Poppler.version">http://ruby-gnome2.sourceforge.jp/hiki.cgi?Poppler#Poppler.version</a><br style="" class=""></div><div style="" class=""> </div>Therefore your
way ahead of us Ruby users, I dont know about Python users.<br><br><div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"><div class="" style="font-family: Courier New, courier, monaco, monospace, sans-serif; font-size: 10px;">What ever, or however the Poppler user base is accessing Poppler, a sustainable release cycle is necessary given the resources. <br style="" class=""><br style="" class="">I've been working on a Ruby PDF app using Poppler.<br style="" class=""><br>Looking at the time stamp of your e-mail, i guess your somewhere in Europe. I'm in the USA.<br style="" class="">Thanks<br style="" class=""><br style="" class=""><br style="" class=""><div class="" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12pt;"><div style="" class="">On Wednesday 24 of September 2014 00:51:06 Albert Astals Cid wrote:<br style="" class=""
clear="none">| Hi all, we released 0.26.0 five months ago. And we have no schedule for 0.28.0 <br style="" class="" clear="none">| (or i can't find no email discussing it).<br style="" class="" clear="none">| <br style="" class="" clear="none">| This is something that has been happening repeateadly, we "forget" when the <br style="" class="" clear="none">| next feature release or we need to delay it because we only release it every <br style="" class="" clear="none">| so often and we *really* need a feature in.<br style="" class="" clear="none">| <br style="" class="" clear="none">| I'd like to propose a change from having bugfix releases every month and <br style="" class="" clear="none">| feature releases every ~6 months to just having a release every month.<br style="" class="" clear="none">| <br style="" class="" clear="none">| In that release we would introduce both bugfixes and features.<br style="" class="" clear="none">| <br style="" class=""
clear="none">| We have been *very* good in the past with not introducing regressions thanks <br style="" class="" clear="none">| to running the regression suite, so i think this is a good thing since it <br style="" class="" clear="none">| makes it easier for our features to reach the users earlier (e.g. i have a <br style="" class="" clear="none">| feature in poppler-qt that need to be released to make okular faster).<br style="" class="" clear="none">| <br style="" class="" clear="none">| The downside is that some distros won't like it, but honestly those distros <br style="" class="" clear="none">| already don't update some of the minor releases because we do changes to our <br style="" class="" clear="none">| internal APIs so one can't fix distros.<br style="" class="" clear="none">| <br style="" class="" clear="none">| Given the manpower we have at the moment (i.e. very low) i think a monthly <br style="" class="" clear="none">| release (or maybe
every two months) that contains both bugfixes and features is <br style="" class="" clear="none">| the best for us.<br style="" class="" clear="none">| <br style="" class="" clear="none">| Comments?<br style="" class="" clear="none">| <br style="" class="" clear="none">| Cheers,<br style="" class="" clear="none">| Albert<br style="" class="" clear="none"><br style="" class="" clear="none">Sorry for maybe missing something obvious, but how about just releasing when you feel there's something warranting the release instead of sort of forcing yourself to do release cycles?<br style="" class="" clear="none"><br style="" class="" clear="none">While a little bit orthogonal, this could also involve choosing different versioning method[1].<br style="" class="" clear="none">Patch releases whenever important enough fixes are delivered (so that distros don't have to backport them from git).<br style="" class="" clear="none">Introduce major releases for
"important" changes, minor releases for maybe less "important", but preferably API backward compatible changes.<br style="" class="" clear="none">"important" is differently defined by different parties. For distros it could mean "anything that breaks API or considerably enhances functionality".<br style="" class="" clear="none">Poppler is somewhat known for changing internal (XPdf?) API more than once so - following distros' "important" definition - that could mean numerous major releases if that API is considered public API, but hey..<br style="" class="" clear="none"><br style="" class="" clear="none">1. <a style="" class="" shape="rect" href="http://en.wikipedia.org/wiki/Software_versioning#Change_significance" target="_blank">http://en.wikipedia.org/wiki/Software_versioning#Change_significance</a><br style="" class="" clear="none"><br style="" class="" clear="none">regards<br style="" class="" clear="none">MM<div style="" class=""
id="yqtfd90778"><br style="" class="" clear="none">_______________________________________________<br style="" class="" clear="none">poppler mailing list<br style="" class="" clear="none"><a style="" class="" shape="rect" ymailto="mailto:poppler@lists.freedesktop.org" href="mailto:poppler@lists.freedesktop.org">poppler@lists.freedesktop.org</a><br style="" class="" clear="none"><a style="" class="" shape="rect" href="http://lists.freedesktop.org/mailman/listinfo/poppler" target="_blank">http://lists.freedesktop.org/mailman/listinfo/poppler</a><br style="" class="" clear="none"></div><br style="" class=""><br style="" class=""></div> </div> </div> <div class="" style="font-family: Courier New, courier, monaco, monospace, sans-serif; font-size: 10px;"> </div></div> </div></body></html>