Automated Content Transformation Software
Home | 1-877-893-2967 | Support
Where the * is Scotty?
View by Blog
  • All WebWorks Blogs
  • Scenes from the Engine Room
  • Digital Publishing & Automation
  • blurnge
  • Unicorns and glitter!!
  • Technical Communication
  • Christopher Ward
Recent Posts
  • The Reverb Effect
  • Happy Snowman Donut Award
  • Google Chrome == Internet Yes, Desktop No
  • Building a better AutoMap
  • Is anybody out there there?
  • Sketching the Future
  • Keeping Pace with ePublisher
  • Focus, Focus, Focus
  • Bugs and Car Talk Syndrome
  • 2009.4 and the missing feature
View by Category
  • Automation
  • Business
  • Communication
  • community
  • Details
  • ePublisher
  • Heart
  • Licensing
  • Random
  • RoundUp
  • Uncategorized
  • Wiki
View by Month
  • May 2011
  • February 2011
  • September 2010
  • April 2010
  • February 2010
  • January 2010
  • August 2009
  • July 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
Blog Access
  • Log in
  • Entries RSS
  • Comments RSS
Subscribe to the Blog Feed

Scenes from the Engine Room

2009.4 and the missing feature

Life here in the Engine Room continues on as always; a combination of brimming potential and vexing challenges.  I love creating new things.  I love to solve problems. Sometimes I get to do both at once. But not this time.

You see, we’re preparing to ship ePublisher 2009.4.  And 2009.4 isn’t about features.  It’s about making the best ePublisher 2009 release possible.

Why am I writing about this?

Because I promised folks we’d include just one new feature in 2009.4.  It’s a great feature.  Something that increases ePublisher’s flexibility and power.  The problem is that it is just too complex to ship in a maintenance release.  The feature I’m talking about is the capability to define per target style settings.

“We’ll just shim it in there,” I told Jesse.  “No sweat.”

That was back in November.  Back before.  Before we spent hours and days wrestling with PDF defects.  Before we spent weeks chasing workarounds for Frame crashes which we could only bypass, not fix (we don’t have access to that code base).

And so I have to let it go this round.  I have to let people know, “No, not this time.“  There really is no other choice.  The time has been spent.  It was spent on exactly what we needed to do; stability.  It’s just that I like creating new things.  I don’t want to let go.

…

Then again, once 2009.4 ships, all that maintenance work is done.  And if 2009.4 is done, then we can focus on 2010.1.  And we can put new stuff in 2010.1.

…

I think this is going to work out alright after all.

Posted in ePublisher |

6 Responses to “2009.4 and the missing feature”

  1. Suzanne - January 11th, 2010

    You guys are doing a great job. We can wait for this feature. I sure would love to see the ability to generate a file list, though! ;)

  2. Malcolm - January 14th, 2010

    Stability is definitely important: I think you’re doing the right thing.

  3. Ed McElroy - January 14th, 2010

    keep up the great work. Looking forward to seeing a fix for the disappearing ampersand issue.

  4. Lisa - January 29th, 2010

    Personally, I would rather only see two updates a year…seems we get one in and there is another one starring at me and each one makes me cringe. Have you thought of going to two per year?

  5. allums - February 4th, 2010

    Hey Lisa! Your request, that we slow down our quarterly releases, is something that I’ve heard from several customers in the past. I wanted to explain how users can make the most of our quarterly release system. The explanation wound up being more of a blog post than a comment. So, now it IS a blog post, Keeping Pace with ePublisher. Have a read, and then tell me what you think.

  6. Scenes from the Engine Room » Keeping Pace with ePublisher - February 5th, 2010

    [...] a few weeks ago, I wrote about “2009.4 and the missing feature“.  Customers gave that post some great feedback. People seemed to understand our goals for [...]

Leave a Reply


  • « Previous post
  • Next post »
This blog is protected by Dave's Spam Karma 2: 2359 Spams eaten and counting...