• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

Whatever convention is agreed for naming releases (http://twiki.org/cgi-bin/view/Codev/TWikiReleaseNamingConvention), we have to automate it somehow.

The build process currently names all releases "TWiki" i.,e. does not differentiate packages. The proposed automation is:

  • build.pl prompts for a release name
  • sed TWiki.pm to insert the release name in $RELEASE, and svn ci it (Item000:) to ensure correct repository labelling ($RELEASE is currently 'Dakar')
  • derive a TWiki topic name from the release name using an RE e.g.
$release =~ s/^(TWiki)?(\d+)\.(\d+)\.(\d+)$/TWikiR$1_$2_$3/ or die "Invalid release name $release";
  • Use the release name as the name for the zip and topic

CC

All done except RE, which is not strictly necessary. All we need now is agreement on the release naming scheme.

SVN 8209

CC

ItemTemplate
Summary Automate release naming
ReportedBy CrawfordCurrie
Codebase

SVN Range Fri, 06 Jan 2006 build 8154
AppliesTo Engine
Component BuildScripts
Priority Urgent
CurrentState Closed
WaitingFor

Checkins 8209 8365
Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r4 - 2006-01-10 - CrawfordCurrie
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback