Okay, so I’m behind on my “Ravencon Panels (I DID do)” series. I get it. Maybe I’ll be able to get back to that, soon (hopefully I’ll finish the Ravencon Panels series before my next convention. Heh). But, in the meantime, I’ve got something else to discuss:
Today’s blog post is to announce that I FINALLY HAVE A (BLEEP)ING COVER FOR THE MERRIMACK EVENT!
This means that I can finally finish building the book and release it. Now, I had an outside hope of getting that done by today (which would have made this blog post an announcement that the eBook, at least, had been released, and not merely a cover reveal), but between thunderstorms, a convention I’m scheduled to guest at asking me to pick the panels I want to be on (this will be the subject of its own blog post in a couple weeks; I’m finally listed on their web page), and a few other odds and ends, I haven’t had any time to work on it since I got the cover. I should be able to get to work on it by tomorrow. My next Sunday Blog Post (which I’m hoping will be next weekend, but shouldn’t be more than the weekend after that even in a worst case scenario) should be to announce said book release.
I have one last decision to make on the book, however. Do I make it a wide release, as I have all my other books to date, or do I experiment with a Kindle Select listing (which requires Amazon exclusivity)? I’m leaning towards setting it up for one round as an Amazon exclusive, just to see what the service is like from the inside (as opposed to my more vicarious observations of other authors’ experiences), but it seems every time I’m about to release a book, I start hearing of bad things happening with Kindle Select. (Note: This decision will have NO impact on the print edition, for those five or six of you who prefer to buy my print books). Regardless of what I decide, it will ONLY be for the one 90 day period, and then (if I haven’t already) I will open it up to the wider release.
Stay tuned. The book release will be coming here, soon.
Edit: Seriously, spammers? Comments closed here, too. Dammit.