Hi all,
What’s the best way to gain access to the repository so I can create my own branch and possibly participate?
I’m a highly experienced C#/C++ developer that has recently begun doing some Java at work. I also use VASL quite a bit. I emailed Rodney already as per vassalengine.org/wiki/doku.p … ipse_setup but that wiki article seemed to be out of date and I figured I’d double up here.
Thus spake “Morbii”:
Asking here is the best way. What’s your SourceForge username?
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
I believe it is morbii (if that’s what I set up just the other day during this process that requires lower case - I think it was 
Thus spake “Morbii”:
You’re added. Feel free to create branches as necessary, but please
coordinate with whomever is handling the VASL trunk before committing
there.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Sure thing - thanks J.
Rodney hasn’t been active on the mod for one year now.
I’m not sure if we need him to commit changes to trunk, or define some alternative process until further notice.
For VASL 5.9 beta 3, I provided binaries from my own branch, but if we have to work on several branches, at some point we need to synchronize, either in a shared 5.9 branch, or in trunk.
Thus spake “wlk”:
The process we’ve had for some time now with VASSAL for merging changes
is that for “stable” branches (e.g., the 3.1 maintenance branch), we
have one person responsible for managing merges. (For the 3.1 maintenance
branch, this person has been me.) This seems to work, since the volume of
changes is not so great that one person can’t handle it in a timely
fashion. It also forces the “branch manager” to look at all the code being
merged, which means that you get some minimal amount of code review and
it builds codebase familiarity for the manager. (I’ve learned a lot about
parts of the VASSAL codebase I’ve never worked on myself this way.)
So, my suggestion is to get together the people who are coding on VASL and
decide amongst yourselves who should manage the trunk.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Thus spake “wlk”:
How close are you guys to a 3.1-compatble release, BTW? We’ve had at least
one bug report every day since the release of 3.1.0 about VASL being
incompatible with 3.1…
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
This is most exaggerated 
Actually, I fixed like 5 bugs now, and there’s none left I am aware of, at least the ones related to VASL binaries.
I’m using 5.9 with 3.1.13 daily and didn’t notice anything wrong.
Jeffrey was waiting for 3.1.14 to be released to publish VASL 5.9.
Thus spake “wlk”:
Oh! I didn’t know you were waiting for 3.1.14. I can put together a test
build tonight, and if people try it out to confirm that it’s ok, we can
release tomorrow.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
The site is working again? OK, I’m officially totally confused.
Thus spake “bsmith”:
WTF? Me too. I wonder what happened.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
I’m so relieved it’s back; I needed 4 coffees and 6 Diet Cokes to overcome the mood it put me in this morning. 
Thus spake “wlk”:
All the bug reports I see come through the VASSAL bug tracker and are
due to people trying to run VASSAL 5.8 in VASSAL. It really is about
one per day…
VASSAL 3.1.14 is released, so we’re not blocking you anymore.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)
Any objection if I close all bug reports from VASL 5.8 running on VASSAL 3.1 and later, with a “won’t fix” ranking, unless reproduced with 5.9 ?
Thus spake “wlk”:
I have three reservations:
Don’t close them unless the same problems really are fixed in 5.9.
Don’t close them until 5.9 is actually released.
When you close them, email all of the users who have left an email
address to let them know that they should upgrade to 5.9.
–
J.
Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org
Post generated using Mail2Forum (mail2forum.com)