[scribus] Trunk branched for future development work

[Craig Bradney]

Hi

 

For those that use subversion to get Scribus code, please note that we have branched to separate future development.

 

The Version15x branch will be the branch used to finish work on 1.5.x, leading to the 1.6.0 stable release. Once 1.6.0 is released, this will entirely deprecate 1.4.x.

 

Trunk will now be versioned 1.7.x, and move to Qt 6.2 and higher compatibility.

 

Usage advice:
For those using 1.4.x: if you’re happy there, use it for those older documents until we release 1.6.0. While 1.5.8 that we just released is more stable than 1.4.x, you’ve waited many years, no rush now I suppose. There’s potential risk there in terms of dependencies and their security so that’s up to you to evaluate, and depends on your installation method/platform. You can have 1.4.x and 1.5.x installed at the same time if you want (depending on how installed on your system etc, but it’s possible from a Scribus perspective).
For those using 1.5.x: it’s a good place and you’re heading for stable 1.6.0. I’d hope most people are in this scenario now. If you’re checking out SVN, switch to the Version15x branch (the basic checkout command becomes something like: 
svn co svn://scribus.net/branches/Version15x

There will be some more smaller features added and certainly more bug fixes, documentation updates, translation updates, etc in the move towards 1.6.0
For those who want to ride the bumps and brokenness when we get to move trunk to Qt 6.2, check out trunk (svn co svn://scribus.net/trunk). It may not be usable some days once the Qt 6.2 migration continues.
 

End result:

Current scenario:
Old stable:1.4.x
Development version: 1.5.8/x
Future scenario:
Stable: 1.6.x
Development: 1.7.x
 

Craig

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus/attachments/20220127/ad861db1/attachment.htm>