boss-developers / boss-developers.github.io Goto Github PK

Here's a rough plan of action:

1. git-svn the whole Google Code repository into the boss repository.
2. Tag the releases in the boss repository.
3. Remove the release binaries from the repository, and attach them as releases.
4. Create appropriate wiki pages, using a mix of the ones on Google Code and the ones for LOOT.
5. Update the site.

The Google Code repository having a non-standard layout and changing layout several times over its history make splitting it up and converting it fully a pain, so I'm not sure if I want to convert branches or split the repository up.

@boss-developers: Some of you may be aware of the recent flare-up in the BOSSv3 development thread over the direction that BOSSv3 has taken and its readiness for release.

As a result of that discussion, I have decided not to release BOSSv3. Instead, BOSSv3 will revert back to its development codename of LOOT (Load Order Optimisation Tool), and a version of 0.5. This avoids the sense of expectation and inevitable disappointment that some users would face moving from v2 to v3 while we get its metadata up to scratch, whilst still allowing us to release and gather more feedback without a flood of complaints.

LOOT will be run as a separate project (though with no practical changes other than the name and repository locations). You all have access to its repositories.

As this strips BOSS of a future release, I shall be releasing a v2.2 of BOSS to fix the outstanding major bugs with it. To my knowledge, these are:

• Broken version checks. This should be a trivial fix.
• Broken masterlist updating. This isn't a trivial fix, and the easiest involves moving to Git. That will break updating completely for existing BOSS releases, but I suppose that an obvious failure is still better than the current situation.

The move to Git is covered by issue #1. This issue is to make you guys aware of the situation and to give us a place to discuss how we want to handle it. I for one would be happy to release v2.2, then leave BOSS behind, so there's no pressure on you to continue maintaining it. We could just put it up for adoption - the move to Git would just so happen to make that easier to do. You also don't need to follow me to LOOT, if that's what you wish.