[TechniSol]

He may be a bit over the top, okay 100 feet over Kilimanjaro, but he has a point. To my knowledge the only information science connected entities that believe it is OK to break other things while fixing yet others, on an ongoing basis, are government subsidized.

Let's lay the cards on the table here, Kobo has all the grace of Chinese tablet manufacturers when it comes to maintaining/improving firmware -and I'm not altogether sure we aren't insulting the tablet manufacturers at times... Maybe it's being a one man show these days, maybe it's that I have top down control over the projects I elect to take on, but if I had to break things, while fixing others, and could not fix/manage the fallout, I'd have the good sense to do nothing! Were I being paid by others to do so, I'd live in daily fear of my job while getting better(sneakier?) as quickly as possible.

No disrespect to the developers, but there is a time for all good men to make a stand. If the marketing department is running things I suggest the programming department inquire just how soon the marketing department will be up to speed to take over further development, at the most crucial stage possible.(If you're going to fight, fight dirty and feel bad about it later if you must.) But, then not knowing the term or details of their employment agreements it's easier to say what I'd do. I wish the development team the best, but I'm not happy as a customer, and I'm a little ashamed as a developer when release after release leaves fundamental issues unaddressed while adding new window dressings. If I wanted new curtains, I'd buy them. I just want Kobo development to realize its full potential.

I, too, offer apologies to those more genteel than I.