How about Nightly-Builds?
- Watermelon
- Code contributor
- Posts: 551
- Joined: 08 Oct 2006, 09:37
Re: How about Nightly-Builds?
It's a good idea to promote new features and draw attentions,but the data is too big to go nightly,because the text files are changed every now and then,though I think the data can be incremental via physfs system.
tasks postponed until the trunk is relatively stable again.
- DevUrandom
- Regular
- Posts: 1690
- Joined: 31 Jul 2006, 23:14
Re: How about Nightly-Builds?
Weekly maybe... There aren't enough new features or even commits each day...
And using a base-data.wz and loading overlay .wz's for each version of the weekly-build sounds possible, even though you either have to supply a commandline like "-mod 2006.11.wz -mod 2006.12.wz -mod 2007.01.wz ..." with the current implementation of mod handling.
When we got depencencies between .wz files / data portions (I want to work on this in the holidays) we can even through all data into one directory, load each ones metainfo and the unload it again till another datapart depends on it. (By the time something depends one the chunk, we would have a list of .wz, files sorted by priority, which contain the needed chunk.)
And using a base-data.wz and loading overlay .wz's for each version of the weekly-build sounds possible, even though you either have to supply a commandline like "-mod 2006.11.wz -mod 2006.12.wz -mod 2007.01.wz ..." with the current implementation of mod handling.
When we got depencencies between .wz files / data portions (I want to work on this in the holidays) we can even through all data into one directory, load each ones metainfo and the unload it again till another datapart depends on it. (By the time something depends one the chunk, we would have a list of .wz, files sorted by priority, which contain the needed chunk.)