<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 10, 2017 at 6:20 PM, Ralph Versteegen <span dir="ltr"><<a href="mailto:teeemcee@gmail.com" target="_blank">teeemcee@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Ah, I see I was mistakenly counting the 3 months from Dwimmercrafty+1 rather than Dwimmercrafty!<br><br></div>What counts as something that "can't wait" for F? Only things to fix bugs or backcompat problems? Or does it include changes that other work depends on, and would result in too much being done in a branch?</div></div></div></div></div></blockquote><div><br></div><div>I would say any of the above. Basically is there anything you think is better to merge now rather than to wait to merge until after etheldreme?<br></div> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>For how long before a release do we want to avoid major changes? Sitting around in nightlies is no substitute for testing with release candidates. People only download new nightlies rarely. I'd say how long to wait depends on how significant the change is rather than a hard cut-off.<br></div><div>Also, we can keep things out of the release either by not checking them into wip (eg by using git branches) or by branching etheldreme early in svn. I think it's easier not to branch stable releases long ahead.<br></div></div></div></div></div></blockquote><div><br></div><div>How about if we aim for a RC around the 18th and a release around the 25th if all goes well?</div><div><br></div><div>I know that is a short RC testing range, but I don't think a longer range will actually result in a lot more testing</div><div><br></div><div>I also agree that it is better not to branch the stable release long ahead. I think I didn't branch the dwimmercrafty release until the day of the release, and that worked fine for me.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div></div><div><br></div><div>I keep jumping between working on so many different things that I can't decide what to do next.</div><div><br></div><div>The biggest things I had been planning to work on in the next weeks was changing the graphics file format, replacing the spriteset browser, and to convert battles to slices.</div><div>That would allow raising the sprite size limits, and possibly the 16-color limit (with additional work in the sprite editor) without depending on the new animation system.<br></div><div>However it looks like I'll have little time to work on the OHR for the next 10 days anyway, so it's all moot.<br></div></div></div></div></div></blockquote><div><br></div><div>That sounds like a lot of work for just 10 days, even if you had nothing else to do in the world! :)<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div></div><div><br></div><div>More realistically, I've been doing lots of work on slices recently, most of which isn't exposed yet. I'll think about whether it's ready to expose.</div><div>And I wanted to work on equip slots.<br></div><div><br></div>A general summary of stuff I'm actively working on but haven't merged yet:<br></div>-line slices</div><div>-template slices (hidden slices which are ignored for all purposes)</div><div>-refactoring embed_text_codes, so that you can use embed codes in text slices<br></div><div>-map editor improvements</div><div><br></div><div>And some stale stuff that's close to mergeable:<br></div><div>-nicer looking minimaps either using scale_surface (which require 32 bit color) or an alternative (which doesn't)</div><div>-joystick rewrite, to fix our utterly broken joystick handling (so little risk of breaking anything by merging it)</div><div>-a color replacement tool for backdrops, which REPLACES the 'disable palette colors for import' menu.<br></div></div></div></blockquote><div><br></div><div>Those last two especially sound like great things to sneak in before etheldreme. :) <br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div></div>BTW, don't forget to update this out-of-date whatsnew line:<br> * You can now browse for items rather than typing in their ID<br> numbers [James]<br></div></div></blockquote><div><br></div><div>I'm not sure what I need to change there... Maybe I phrased it badly?</div><div><br></div><div>----</div><div>James<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 11 November 2017 at 12:43, James Paige <span dir="ltr"><<a href="mailto:Bob@hamsterrepublic.com" target="_blank">Bob@hamsterrepublic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div>It is almost time for the Etheldreme stable release!<br><br></div>If possible, I hope to release it by the end of this month (Last week of November, ideally)<br></div><div><br></div><div>My general impression of the current nightly wip builds is that they are pretty stable, not to crashy, and have a respectable amount of nifty new stuff.<br></div><div><br></div>I don't have any pending critical stuff that I need to finish. TMC, do you have anything that needs to be checked in that can't wait for the f* release?<br></div><div><br></div><div>The only halfway ambitious thing I might attempt before then (only if I have time) would be to try and do a little more work on ThingBrowser to enable editing while browsing (which currently only makes sense for ItemBrowser, but will be important for AttackBrowser, HeroBrowser, EnemyBrowser, etc...)</div></div></blockquote></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><div><br></div><div>---<br></div>James<br><br></div>
<br>______________________________<wbr>_________________<br>
Ohrrpgce mailing list<br>
<a href="mailto:ohrrpgce@lists.motherhamster.org" target="_blank">ohrrpgce@lists.motherhamster.o<wbr>rg</a><br>
<a href="http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org" rel="noreferrer" target="_blank">http://lists.motherhamster.org<wbr>/listinfo.cgi/ohrrpgce-motherh<wbr>amster.org</a><br>
<br></blockquote></div><br></div></div></div>
<br>______________________________<wbr>_________________<br>
Ohrrpgce mailing list<br>
<a href="mailto:ohrrpgce@lists.motherhamster.org">ohrrpgce@lists.motherhamster.<wbr>org</a><br>
<a href="http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org" rel="noreferrer" target="_blank">http://lists.motherhamster.<wbr>org/listinfo.cgi/ohrrpgce-<wbr>motherhamster.org</a><br>
<br></blockquote></div><br></div></div>