Download Padre


Once Padre or one of the plugins is released based on the following process it is uploaded to CPAN. There are various way [wiki:Distribution Repackaging and Distributing] those modules.

Prerequisites to releasing Padre

As the Release Manager you will be uploading the Padre tarball to pause, to ensure you have the right permissions to do this you must obtain co-maintenance permissions for all of the namespaces in the Padre distribution. Talk to Gábor Szabó (szabgab), Adam Kennedy (Alias), or Steffen Müller (tsee) about this. Make sure you get Wx::Perl::Dialog, Wx::Perl::Dialog::Frame, Wx::Perl::Dialog::Simple, and Wx::Perl::Dialog::SingleChoice too. For the ppi_version utility, install PPI::PowerToys.

Release of Padre using a branch

In order to allow a few days of stabilization of Padre and to allow the translators to catch up while allowing everyone else to freely work on the main trunk we release from a branch.

A few (2 or 3) days before the planned release date the release manager creates an svn copy of trunk to branches/release-n.nn.

The high level steps are as follows:

  • Make sure all tests pass,
  • Set the release version, commit,
  • Tidy the project, commit,
  • Update Changes file, commit,
  • Rebuild the messages.pot, commit, ** no longer required **
  • Set the version from current dev to next production release, commit,
  • Branch
  • Announce branch and URL to dev list,
  • Allow a few days for translators,
  • Build Tar Ball,
  • Test where you can.
  • Upload to PAUSE.
  • Prior to merge back, set version to current dev version ( should be +1 ), commit,
  • Merge changes on Branch back to Trunk, this should only be the translations if all went well.

Detailed Steps for a Release

Note: All commands are taken as relative to your Padre directory ( the one with Makefile.PL in it )
  1. run perltidy on the trunk {{{ ../tools/ }}}
  2. commit
  3. Update the Changes file, noting the date of the release being the date you start the branch
  4. commit
  5. set the version from the current development version number to the release version number ( should be even numbered for released odd numbers for development )
  6. Note: there is a script in tools that will update the $VERSION string, however PPI::PowerToys has an awesome ppi_version, use this when you can: {{{ppi_version change old_ver new_ver}}}, ie {{{ppi_version change 0.81 0.82}}}
  7. commit
  8. rebuild the "messages.pot" file, run {{{ ../tools/ }}}
  9. commit
At this point trunk is ready for you to make the branch: * {{{ svn cp }}} (replace X.XX with the future version number) You have now created the for Padre. To complete the final tasks on trunk, update the Changes file by "opening" the next version. * Modify Changes, set the next development version number, this should be odd and the next release version number should be even, ie if you have just branched release-0.82, then changes gets updated with: 0.84 TBA 0.83 Dev - not released. Make the changes to the version number to the next development cycle number: {{{ppi_version change 0.82 0.83}}} * Commit the changes From this point onwards you switch your working copy between the branch and trunk as needed. To switch between trunk and the branch:
  • {{{ svn switch }}} .
  • then every commit will go to the branch while the plugins are still from trunk
  • the release can be done here but probably it is better NOT to run the perl tidy on the branch as it will make merging very difficult

Announce the Branch in padre-dev

Announce the branch in the dev mailing list and put out a call for translators, an email template is provided:

Hi Team,

I have just made a branch of trunk for the next Padre release .

Could all translators be so kind as to update their language.

To do so, either check out a working copy of the branch here:

{{{svn co}}}

or alternately you can switch your working copy:

{{{svn switch}}}

Please commit all changes to the branch for inclusion into the next great release of Padre.


Padre Release Manager.

Do the regular release process

  1. The release manager first builds a distribution and when she is sure it creates a good release, she can run the script again to also tag the release in SVN and then ask others to test it:
    • the environment variable RELEASE_TESTING should be set to ensure testing for a release is run.
    • the script will set it if the variable isn't found. If you want more control over the testing before a release set RELEASE_TESTING to 1 to test, 0 to turn testing off.
    • run {{{ perl ../tools/ --revision REV --version VERSION }}} will try to create a distribution using a temporary directory and copy the resulting Padre-X.XX.tar.gz in the current directory.
    • Test it by yourself (install it using pip, run it)
    • run {{{ perl ../tools/ --revision REV --version VERSION --tag }}} This will also create a tag in SVN.
    • Upload it somewhere public and ask Gabor to copy to
    • Tell people on IRC #padre about it and ask them to test it
  2. Upload to PAUSE
  3. Send announcement to [ padre-dev] mailing list
  4. Send announcement to [ padre-news] mailing list (Gabor might need to send the message but at leas he needs to approve it after you sent it)
  5. Submit announcement to or some other well-read blog (e.g. one that is syndicated on Iron Man and on )
  6. Update the [wiki:Release_History Release History]
  7. Add the version number to the list of versions in Trac. A trac admin needs to do this:
    • Go to Admin/Versions in the "Name:" box type in the version number eg. 0.45, click on "Add"
    • Select the radio box on the right hand side of the newly added line and click on "Apply changes"
  8. Important: Assign primary maintainer status to Gabor (PAUSE ID 'SZABGAB') for all namespaces that are new in the current release.
    • Log into your PAUSE account
    • Click "View Permissions" in the menu
    • Note all Padre::* classes for which you are listed as "first-come" (as opposed to "co-maint").
    • Click "Change Permissions" in the menu
    • Under "2. You are primary maintainer:" select any one or all of the Padre::* namespaces that appear in the list view.
    • Click Select for "2.1 Pass primary maintainership status to somebody else (giving it up at the same time)"
    • Make sure all Padre::* namespaces are selected in the new listbox.
    • Enter "SZABGAB" in the text field.
    • Click "Pass Maintainership Status".
    • You will automatically become co-maintainer instead of primary maintainer of the classes in question.
  9. Update [ Padre's Wikipedia] page with the new version number
  10. ppm creation:
    • tar xzf Padre-X.XX.tar.gz
    • perl Makefile.PL
    • make
    • make ppm will create a Padre.ppd file and a Padre.tar.gz file
    • change the other files in /trunk/ppm according to the README there
    • upload Padre.tar.gz as Padre-X.XX.tar.gz to
    • upload the other files from trunk/ppm to
  11. Create executable for Linux:
    • make exe
    • Upload to

Merging back to trunk

  1. set the version in the branch to the current development version, {{{ppi_version change old_ver new_ver}}}
  2. when finished merge the branch back to trunk:
  3. {{{ svn switch }}} .
  4. {{{ svn log --stop-on-copy }}}
  5. Take the FIRST and LAST revision number from that log
  6. {{{ svn merge -rFIRST:LAST }}} .
  7. If you do not get any merge conflicts, then follow the next step, otherwise use "Resolving Merge Conflicts" as a quick guide to help resolve any conflicts.
  8. {{{ svn commit -m'merge -rFIRST:LAST' }}}
  9. now you can remove the release branch:
  10. {{{ svn rm }}}

Resolving Merge Conflicts

If you are fortunate you will not see merge conflicts when you merge the branch back to trunk, however if you do, then the following is a quick crib on how to deal with it.

When dealing with merge conflicts consider "where you are". If you switched from the branch to trunk, the notion of "theirs-full" is going to be the branch that you are merging in. If you are merging trunk back to the branch, then trunk will be "theirs" and the branch will be "mine".

When you make a mistake with the merge, you can undo the merge with {{{ svn merge -c -15702 . }}} where the revision number here is the revision number of the commit to trunk you just made after merging.

Once you have done that, commit the change to trunk, start the merge from the branch again, keeping in mind "where you are".

Note: you will likely get a conflict with messages.pot, you can "skip" this conflict by selecting "tf", "Theirs Full" option if you are merging trunk to the branch, or "mf", "Mine Full" if the merge is the branch to trunk.

When svn updating you SVN will halt at the file in conflict asking you what to do, simply select "postpone" as we will go back to the conflicted file(s) after the merge has completed.

SVN will create three files if there is a merge conflict in trunk and the branch, a 'left.merge', 'working' and 'right.merge' file.

The simple way to work this out, is open the actual file in vim.

Look for lines that begin with >>> or <<<

Depending on which lines you keep, remove the lines between >>> or <<< and === and remove these lines too.

Once you have completed the merge and are happy with the changes, tell svn you have resolved the problem:

svn resolved file-name

This removes the merge conflict files.

Once you have completed all the conflicts, return back to the parent directory and svn commit with a message like 'merge -rFIRST:LAST' as this shows up in the log where you merged the branch back.

Release of Plugins and other packages

The packages can use either Makefile.PL (Module::Install) or Build.PL (Module::Build). We have not tested the below process with ExtUtils::Makemaker

No need to keep MANIFEST and META.yml in version control!


# avoid pot files (gettext)

If you are using Module::Build

Don't add a Makefile.PL to the version control as it will be created during packaging

Release process

  1. cd to the directory of the plugin or the package
  2. ../tools/
  3. run {{{ perl ../tools/ }}} (commit)
  4. run {{{ perl ../tools/ VERSION }}} and update Changes (commit)
  5. run {{{ perl ../tools/ REV VERSION [--tag] }}}
  6. upload to PAUSE

Release Manager

The current release manager is Peter Lavender (waxhead on [wiki:IRC IRC]).

Release schedule

The exact release schedule is decided by the current release manager, below are the general guidelines

Padre is released to CPAN about once every week when trunk seems to be in a stable state.

Once a month we set aside a version for a "packaged" release for which we use a longer time on the release branch.

We take the latest regular release and base the "packaged" release right on the regular release. So for example we have 0.43, 0.44, regular releases then based on 0.44 we create a release branch for 0.45 We give the translators a few days to catch up on this branch. That time will also allow people to give feedback on 0.44 so we can fix really critical issues on the 0.45 branch.

This release should be scheduled just a few days after Rakudo is released.

Once it is done CSJewell creates the windows [wiki:Distribution distributions] based on Strawberry Perl.

That means we have these "packaged" and translated releases by ~ 20-25th of every month.

See this post and create a better tuned process for the "packaged" releases.

Pre-Release Tests (proposal)

Pre-Release Checklist