Version 10 (modified by Bruno Cornec, 8 months ago) (diff)


Creating a new pb version

  • Ensure that all dev tests are ok first ;-)
      cd pb
  • Ensure that the SVN status is correct for both devel and pbconf:
      svn up
  • Ensure that the Changelogs are OK for all packages:
      cd devel
      svn log pkg
      gvim ../pbconf/devel/*/pbcl
  • Use pb to create the target version from the devel branch:
      pb -p pb -r devel -V 0.15.1 newver
  • Edit again the pbcl files for the new version 0.15.1 and remove mentions of new version
      gvim ../pbconf/0.15.1/*/pbcl
      svn ci
  • Edit the config file to declare the version stable (delivery and testver):
      gvim ../pbconf/0.15.1/pb.yml
      svn ci
  • Build a test version in a ctn:
      pb -p pb -r 0.15.1 -m centos-7-x86_64 sbx2ve
  • Build for all ctns:
      pb -p pb -r 0.15.1 build2ve
  • Build a test version in a VM:
      pb -p pb -r 0.15.1 -m rhel-7-x86_64 sbx2vm
  • Build for all VMs:
      pb -p pb -r 0.15.1 build2vm
  • Check what is produced
      pb -p pb -r 0.15.1 checkssh
  • New distributions
      pb -p pb -r 0.15.3 build2docker -m mageia-8-x86_64
  • Update trac
      Manage milestones - Edit the target one (0.15.1) and close it with a comment as in - Default is now the next one.
      Manage versions - Add the new one as a default.
      Review BR/ER
  • Update Web site (new distros versions)
  • Write a blog article
  • Announce it
    pb -p pb -r 0.15.1 announce
  • Publish the website with the announce integrated
    pb -p pb -r 0.15.1 sbx2webssh
  • Update the build environment with this new version