planning

Quoted from the “precomputing map tiles” thread:

One more thing: Should we be targeting this at the next 3.1 release, or
at 3.2? If the latter, then maybe we should try to get 3.2 out the door
with only the features it has now.

Depends on how long you want to wait. I would be tempted to say include it in
3.1. It doesn’t add any module functionality, so shouldn’t break any modules
and will make things a lot simpler. 3.2 is going to require a lot of testing
and debugging and several of my features need ‘polish’. It will take plenty
of time even with adding minimal extra functionality. I would like to set a d
efinite plan for what we want to include in 3.2 and work towards that for a N
ew Year release perhaps?

I’d like to finish the tile cache now, since I’m thinking about it already.
Putting it into 3.1.11 is fine with me; as you say, it’s not a features
change.

Since you want the Jabber server setup and I think it won’t be too difficult,
I’ll plan to that sometime this week.

After that, do you care whether I go after the new site or 3.2 stuff next?

Two more things:

  1. What about the bugs in the bug tracker? They still seem to be accumulating faster than we can dispatch them.

  2. It would be great if we could get a VASL release which works with 3.1 before we start working seriously on 3.2.

No, the Jabber server will give me plenty to do. It will be good to get the new site bedded down.

B.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

A daunting, soul crushing task that cuts hugely into the amount of developer time available to work on the new version.

We need more help, not necessarily with programming. It would be a huge help if someone could triage these problems, weed out duplicates, contact the submitter and attempt to reproduce, setup test cases etc.

I’m not really sure what is going on with VASL or who is maintaining it. I could look at overcoming the specific incompatibilities with 3.1, but I am not keen on taking on any sort of ongoing responsibility, I just have way too much happening at the moment.

B.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

Thus spake “Brent Easton”:

Are you talking about writing my dissertaion? That’s over now. :slight_smile:

Yeah, I agree. I would be less worried about it if not for the fact that
we find so many real problems this way.

Yep. It would be great to have someone doing this.

It’s definitely not for me, since I’m not even an ASL player. It’s terrible
PR for us to have people trying to run VASL with 3.1 and failing, though.
I asked Rodney what the situation was with it some while back, and he said
he was having some issue with packaging, but then I heard no more about it.


J.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

However, VASL is not actually available as a VMOD download, it only comes as a webstart or as a zip of jar files pre-packaged with VASSAL 3.0.18. The only people trying to run it under 3.1 have ‘hacked’ the distribution. If you follow the VASL instructions, it works perfectly. If the VASL people are happy with that, I don’t really see a problem. I haven’t actually seen any posts saying ‘VASL doesnt work’. Perhaps on other fora?

It’s was probably issues with the way it is packaged with a set version of VASSAL. VSQL used to do this as well, but it got too difficult. I ripped out a lot of customizations (often replaceable with standard features) until it became stable under 3.0/3.1.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

Thus spake “Brent Easton”:

A few times a week I close a bug report which is due to trying to load VASL
in 3.1. That’s where I’m seeing it.


J.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

Then the exception should be weeded out in VASSAL.

  • M.

Post generated using Mail2Forum (mail2forum.com)

Thus spake Michael Kiefte:

I don’t know how to reliably filter these exceptions out without also catching
some we want to see. Anyway, it would be better to fix the problems rather
than ignore the exceptions, and I’m guessing about the same amount of work.


J.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)