ISPConfig 3.1.16 becomes ISPConfig 3.2

Discussion in 'Developers' Forum' started by till, Jul 23, 2020.

  1. till

    till Super Moderator Staff Member ISPConfig Developer

    We decided to rename the upcoming 3.1.16 release to 3.2 to make it more clear that the next release is not just a small bugfix release. The release will contain many improvements and some of the changes have the potential to cause issues on very old systems and with this higher version number, we want to make users aware of that.
     
  2. Th0m

    Th0m Active Member HowtoForge Supporter

    Shall the "stable-3.1" label be renamed to "stable-3.2" aswell?
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    We will make a new branch where the 3.2.x released get developed in.
     
    budgierless and ahrasis like this.
  4. Jesse Norell

    Jesse Norell Well-Known Member

    Seems appropriate; I've not mentioned it, but thought for some time that the larger/several year plans for 3.2 would better fit a major release number, 4.x
     
  5. Th0m

    Th0m Active Member HowtoForge Supporter

    I meant the label we add to feature requests and bugs that are scheduled to work on for the stable release ;)
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    ah, ok :) Yes, sure, this needs to be changed.
     
  7. budgierless

    budgierless Member

    hi, just wondering will the new user manual be released the same time as 3.2 or just before?
     
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    I will start working on a new manual when 3.2 is finished, so it will be release after 3.2 release. You will find a notice in the ISPConfig blog when it becomes available.
     
    Th0m, budgierless and ahrasis like this.

Share This Page