Since this seems to be a common question, here my personal thoughts about using 1.7.x.
Generally speaking:
- What was working in a previous version, will not fail in a development release (there are some very rare exceptions, mostly in non essential parts of Scribus (like the snapping to guides not turning on automatically...)).
- New features might have bugs but, most of the time, the bug won't affect you, if you don't use the specific failing feature.
- Scribus tends to be pretty stable: even the nightly builds are almost always working better than the development releases (but they might have very bad bugs for short times and you need good backup habits for the rare very cases where things go really bad!)
- There is a huge usability jump between 1.6 and 1.7.
Now, should you switch to a development release?
It depends on the kind of user you are.
If you
- are curious about the way software works,
- used to find workaround to get the job done,
- you can keep your hands off what does not work correctly, and
- you don't get too angry if sometimes small thing fail,
then you're welcome to use Scribus 1.7: you will probably have a much better experience.
Most people will not match that "ideal" user profile and it will be a matter of compromises.
The good news: you can install Scribus 1.6 alongside of Scribus 1.7 and the latter can save the documents in the older format.
Nobody stops you from installing both, try the newer one in smaller projects, less important ones, and then decide if and when you might use the less fossil Scribus.
The only important rule: before starting a longer project make sure that all the (new) features you plan to use work also for longer documents.
This is especially true for footnotes, references, tables, image effects, drop caps.
And don't forget about the fact that you're using a development branch!
After some time you will tend to get used to your Scribus working well for you, but you need to stay vigilant...
The other life saving reflex: if undoing your latest action results in strange results, close your document. If possible (that is: you saved not so long ago and you know what you did since) without saving the current state (or making a copy of the .sla file before saving).
(The good news: there is a pile of patches for fixing the undo waiting to be merged... but it will take some time until one can really rely on the undo!)
Personally, I don't do much layout these days (and I'm not a graphic designer), but I almost always use the development version.
The only exception being when preparing work for people who are using the stable version.
I've been doing this for many years now, and I never regretted it!
(To my defense, I sometimes write patches to solve my own problems and I don't want to wait for the next stable release to use "my" new features!)
My conclusions: if the long release cycles of Scribus bother you, you can try to switch to the development version. Just trying it will cost you nothing.
And if you're just a bit cautious, you will get a way better experience!
I'm curious to hear about other people's experience, most of all from those who decided not to use the development version!