civicrm42 / civicrm42-core Goto Github PK

I think we'd agreed that we'd manage backports and such via issues and pull requests here. Please set me straight, if I misunderstood.

I just had a small pull request (civicrm/civicrm-core#645) merged into upstream CiviCRM master, and have requested that it be back-ported to 4.3 (https://github.com/civicrm/civicrm-core/issues/661). I'd like to do the same for 4.2. This would allow better consistency in Aegir's support of CiviCRM, and a simplification of that code.

Normally, I would have submitted this as a pull request, but I don't see the 'distmaker' directory in the source tree. From what I can tell, it was in 4.2 SVN (http://svn.civicrm.org/civicrm/branches/v4.2/), but it's also missing from Eileen's repo (https://github.com/fuzionnz/civicrm).

This all pre-dates my involvement with core, so I'm in the dark. I seem to recall hearing mention that we'd have to back-port these scripts. If that's the case, I've just been working with them, and would be happy to help out there.

I've begun a wiki page to document the 4.2-LTS release process.

In my current tests, the buildmaker.sh script stalls at line 177, when it tries to generate some XML:

cd $DM_SOURCEDIR/xml
$DM_PHP GenCode.php schema/Schema.xml $DM_VERSION

This obviously fails, as we appear to have neither an xml/ directory, the GenCode.php script, nor the xml/schema/Schema.xml required for this step. Do these need to be backported? Or are they extraneous to 4.2? If the latter, we should probably backport the buildmaker scripts, so we can tweak them to our needs.