Next beta release

[Chris H.]

We have a large number of new cards and some bug fixes and code improvements. I think that this weekend may be a good time to release the next beta.

[Sloth]

Good idea Chris! I'm sure some people are waiting for some Scars of Mirrodin cards to play with.

Let's make sure not to add any serious bugs until then.

[friarsol]

Definitely time for a new release. There's been a major onslaught of new cards lately.

[DennisBergkamp]

Yup, and everything seems pretty stable...

[Rob Cashwalker]

Let's see a handful of keywords, a new deck generator, and oh yeah, a major architectural change to the card data storage!

[juzamjedi]

Excellent. I look forward to breaking things

It seems like this project has a ton more support behind it than the other projects on this site. Is there a main CVS / where would I go to see if someone has already squashed a bug?

[DennisBergkamp]

Yes:

http://code.google.com/p/cardforge/source/list

[Chris H.]

I may release it Saturday or Sunday. Hard to tell at this moment. If anyone is working on a project and they need more time to finish, then let me know and I can wait a few more days.

I am starting to think that releasing a new beta every week or so might be hard to maintain over the long term. Dennis is surely familiar with this sentiment. I also hope to avoid multiple bug-fix jars unless it is absolutely necessary.

A once a month at the start of the month release schedule might be best overall.

[friarsol]

I may release it Saturday or Sunday. Hard to tell at this moment. If anyone is working on a project and they need more time to finish, then let me know and I can wait a few more days.

I am starting to think that releasing a new beta every week or so might be hard to maintain over the long term. Dennis is surely familiar with this sentiment. I also hope to avoid multiple bug-fix jars unless it is absolutely necessary.

A once a month at the start of the month release schedule might be best overall.

It would be best if we had a build script for putting everything together and then into a package. That way you wouldn't have to spend however many hours putting everything together.

[zerker2000]

Throwing in my two cents: "(unofficial BETA)".
Once a month would work well as a version which has less known bugs than usual, and is linked to by rares' blog. However, the point of the beta is for new bugs to be found quickly, and since not everyone uses the svn script, the releases should be kept relatively up to date.

It would be best if we had a build script for putting everything together and then into a package. That way you wouldn't have to spend however many hours putting everything together.

We don't? As far as I remember, I was (at some point) able to use the eclipse built-in jar builder to compile it. Or at least a jar file that, when placed in the old forge directory(replacing the old jar, and having updated res/), functioned identically to the eclipse launch.

[Chris H.]

It would be best if we had a build script for putting everything together and then into a package. That way you wouldn't have to spend however many hours putting everything together.

`
Turns out that putting together the archive is not too bad. Adding the new card names and the Commit log messages to the change file takes substantially more time.

[friarsol]

It would be best if we had a build script for putting everything together and then into a package. That way you wouldn't have to spend however many hours putting everything together.

`
Turns out that putting together the archive is not too bad. Adding the new card names and the Commit log messages to the change file takes substantially more time.

Well then we should have a script for that :-d Or at least a way to speed up the process.

[friarsol]

Actually I was just thinking about this and maybe we could make a monthly release (with all the changelog info and everything) but also do a weekly trunk build. This would just be a quick build and zip, and we could post it up to http://code.google.com/p/cardforge/downloads/list for people who don't want to mess with svn downloading, but do want to see what we've been up to more than once a month.
This would be less likely to be stable as our monthly beta releases.

[timmermac]

I'm actually finding the SVN releases that I download to be reasonably stable, aside from my own goofiness when typing in deck names into the easy/medium/hard text files. :-Þ

[DennisBergkamp]

Oftentimes they're actually more stable (since they include a lot of bugfixes). But in some cases, we screw up when adding new stuff - and then large parts of functionality might break