'Nightlies' for the branch
It would be great to have 'nightly' builds for the branch (sort of a 1.2 pre-release?), just like we have them for the trunk.
Maybe not really nightly, but weekly, as the branch doesn't change as much as the trunk and would probably cause less work?
What do you think?
Bye, Jojo
Comments
When I look ast the Mac nightlies, I see one for 4891, but as per the CVS this is branch rather than trunk, so for Mac the 1.2 prereleases are made available? If so: please do it for Windows too!
In reply to When I look ast the Mac by Jojo-Schmitz
No. All the nightlies are currently for the trunk only. The build system just check if there is a new revision on the SVN and not if it's on the branch or the trunk.
In reply to No. All the nightlies are by [DELETED] 5
Oh, OK, a bit confusing...
Still my question whether it would be possible to provide 'weeklies' for the branch?
Should I create an RFE in the issue tracker?
In reply to No. All the nightlies are by [DELETED] 5
are the "nightly" build system scripts available via svn? I've implemented similar build scripts for other projects with multiple branches and would happy to help refine the MS scripts if needed.
In reply to are the "nightly" build by mtherieau
The build method is the same for the nightly and the branch, but there is no batch script file included.
In reply to The build method is the same by schepers
by "no batch script file included" do you mean that the script is not in the svn repository? (just checking to make sure I understand). If yes, then no problems here. May I suggest this? ... "svn log --limit 1" is an easy way to discover the latest revision number that a specific branch (or trunk). I've found it very convenient to use that revision number as the build number. Using this "last changed" revision number means that trunk and branch build numbers would be unique (almost always anyways)
In reply to by "no batch script file by mtherieau
After I posted my comment, I realized that my understanding of "scripts" and yours is likely very different. By "script" I understood that to be a shell/batch file, some automated method of that kicks off the compile. While there are certainly files (scripts) used for the compile, there is no automated BAT/CMD file (under Windows).
Personally I've written my own CMD compile script for Windows 7/XP, which works well on both the trunk and branch.