On 10/13/2010 06:36 PM, Andrew Whitworth wrote: > It should still be easy to track master to do testing and identify > bugs as they are created. However, in terms of development and > requiring particular versions, it does seem like nightly snapshots > would be the better way to go.
Well, the two go hand in hand. Some Rakudo developers track master/HEAD to identify problems or benefit from newest parrot speedups. On the other hand we want to make sure that others who don't recompile that often (but still track development versions) don't accidentally run older versions that are known to cause trouble. For that, the 'git-describe' output works just as good as the parrot revision numbers, just require a comparison of more numbers. We'd require a minimum version of parrot, and in between releases also a minimum patchlevel-since-last-release (or whatever the 48 in 2010.09-48-g5d23e30 is called). The Rakudo releases will continue to track Parrot releases. Cheers, Moritz _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
