| Heiko Scheit wrote: | Not really, unless you have a fixed 2.5.9 version. Version 2.6 has
way too many new features, which I don't want at the moment. Or is
there a config option to get the old behavior?
Maybe you should consider supporting two branches, say 'stable' (2.5.9
currently) and 'experimental' (2.6 currently)? For 'stable' only
severe bugs and security issues are fixed and in 'experimental' new
features are introduced. What do you say?
|
I think elog is such a small project that supporting several branches makes no sense. You can do this if you have several developers, one taking care of each branch. But as you know I'm alone. But what I can do is the following:
- Have a default switch for the Encoding. So if "default encoding = plain", the "plain" radio button is on by default, so people tend to write plain text rather than ELCoded text.
- Have either a switch for the email notification, to revert back to the old text format, or have a multipart email message. I saw that outlook sometime does that. One email can contain a "plain" part and an "HTML" part. So you can select in your email reader which one to display. At least thunderbird supports that. But I don't know what your bash scripts say to that, please let me know.
| Heiko Scheit wrote: | For me the risk of upgrading to 2.6 now seems to high, as many people
depend on the logbook. |
Well, that's why it's called "beta". I first want to make sure that the transition to the new version goes smooth, and nobody's installation gets problems. So the old logbooks should be still readable without any modification, and once I implemented the "dual plain/html" email notification, you should be fine to upgrade. Is that correct?
- Stefan |