I've been experimenting with different ways to name nightly
distributions. For now, I'm using something like this:
http://download.openlaszlo.org/nightly/[buildnumber]/openlaszlo-3.3.x-
[os].[extension]
For example -- preview of a preview...
http://download.openlaszlo.org/nightly/682/
contains installers for linux, osx, and windows. No new code in
these, though; it's pretty much just lps 3.3.
So before we go too much farther with this, let's agree on a naming
system for the nightly builds.
questions:
1) do we want to group related releases into a directory? ie, all
products from build 682 into the nightly/682 directory?
2) Is identifying things by build number enough, or do we want $
{buildnum}-${date} ?
3) What should this look like for branches? I don't think we'll ever
have 682-somebranch and 682-anotherbranch builds for the same
revision number.
4) Should the build number go into the actual file name of the
downloaded file, ie 682-openlaszlo-3.3.x-trunk-unix.tar.gz ?
benjamin shine
software engineer
[EMAIL PROTECTED]
_______________________________________________
Laszlo-dev mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
