Forge version 1.2.4

[Chris H.]

Starting a next version thread.

[Sloth]

Some important fixes have been commited and nothing dangerous was added since the last beta. Maybe we can take the opportunity to release a more stable version than normally?

Is anyone hatching something big at the moment?

[Doublestrike]

I just consolidated FPanel and FRoundedPanel (a fairly big change), but there shouldn't be any blowback from that - mostly aesthetic changes, not architectural.

The next big thing on my list is slicing out legacy UI code, but I'll hold off on any commits until post-release since that will definitely be sensitive.

[Chris H.]

I updated my local copy to rev 13962 and started forge. There appears to be some sort of a stability issue graphics wise. Moving my mouse pointer over the various components is causing them to appear and disappear with interesting color changes.

I think that I should hold off of releasing the snapshot build at this time though. I think that we should also hold off of a new beta until after this UI issue is resolved.

I can release another beta on Monday if these issues are resolved by then.

Max mentioned that he was working on some deck changes. It sounds like he is just starting to work on this portion at this time. I do not think that he mentioned any sort of a time line.

[friarsol]

Hopefully we can get everyone to hold off on all but small changes or bug-fixes until 1.2.4 is released. It'd be great to have a stable release to clear up some of the last minute issues that arose in 1.2.3

[Roujin]

Have you guys considered branching for releases? Other open source projects I've followed use this technique.
Basically at some point you would start a branch for the release using current trunk head. Then you go on deving as normal, implementing features and fixing bugs in trunk, but only bugfixes (sometimes only critical ones) are ported to the release branch. After a fixed time or when you feel no more (critical) bugs are in the release branch, you release it.

[Max mtg]

So, what are current plans?
My deck reforging is mainly working, but in current state it disabls custom cube drafts should I commit.
The update will also need a convertor to move decks from current heap at decks to appropriate folders

So, if I commit, it will introduce some bugs for the next 10 days or so. Is that ok for the release plan?

[Chris H.]

Our plans are in a holding pattern at this time due to the clip issues being experienced on some of our computers. If we can figure out a good solution by this weekend, then we could release the next beta on Monday.

You could then merge your work in after the beta and the daily snapshot builds would provide us with a group of testers for your new work.

[Doublestrike]

I've got to examine the newGame, cleanupNewGame, deinitGame, etc. methods which will also introduce a few bugs. There's a massive bug between matches that @slowe wrote about. So, I'd support the 10-days-or-so theory - maybe next Friday for release?

[Chris H.]

I've got to examine the newGame, cleanupNewGame, deinitGame, etc. methods which will also introduce a few bugs. There's a massive bug between matches that @slowe wrote about. So, I'd support the 10-days-or-so theory - maybe next Friday for release?

`
Sounds good to me.

[Max mtg]

If it's about 10 days, I will have enough time to clean the remaining problems in my code.

[Chris H.]

Monday Feb 27 will give us 10 days and a couple of weekends. If this turns out not to be enough time we can then try for Friday March 2nd.

[Max mtg]

That is a plenty of time
I have commited my changes - decks are now nicely organized in their own folders.
Discussion would be better at viewtopic.php?f=52&t=6380

[Doublestrike]

Great, I'll aim for 27 Feb.

[Chris H.]

We are getting close to the release date for the next version. Is anyone aware of any problems that need to be addressed prior to the next release?