The scheduling for the next update to MacJournal is starting to work itself out and I just wanted to let y'all know about it. But first, a word about 2.6.1: there will indeed be a MacJournal 2.6.1. The primary driver for this is a problem with "Multiple Spaces to Space" in the Clean Up menu. It can cause things to go a little wacky if used over large areas of text. So there's a few small things that will be fixed as well. No new features, just some good fixes. 2.6 was a fantastic release in terms of total amount of changes vs. bugs found after shipping. 2.6.1 should be out within two weeks; I have all the bugs fixed in 2.7 so it's just a matter of bringing those changes over to the 2.6 code base and integrating them in there.
Before we get to 2.7, I want to mention printing though. 2.6 corrected some printing appearance issues that people had been complaining about, but it appears to have to changed some other things. To me, it seems like you want the printed output to match the screen exactly and anything different is a bug. But apparently TextEdit prints stuff to A4 differently than I would have expected. It's kind of shrunken, except I don't know why or to what degree. So I'm kind of in a quandary here: I don't know what's really correct for the different paper sizes.
But anyway, back to the issue at hand. The first alpha of 2.7 should be finished this week. 2.7 has a much shorter schedule than 2.6, so the milestones will be defined a little bit differently this time around. The alpha milestone will represent "feature complete" in the traditional sense: all the expected features will be present and at least functional (if a little incorrect and/or buggy at times). This is what alpha typically means and this time I'll stick to it. There just isn't time in the schedule to keep adding things like I have in the past post-alpha. The good news is that there already has been a metric boatload of changes and 2.7 won't be lacking for good stuff. There are some things on the questionable side that may have to get cut (page numbering is the prime example there). There may only be one alpha depending on how it goes and beta might hit come start of December. Beta will mean that all the features are in and all bugs are squashed for the most part. It will mostly be for localization purposes; they will all need to get updated again (however it should be lighter than 2.6). Then hopefully 2.7 will get out the door before the end of the year. That's the plan anyway.