L Aerospace KSP/R&D Division
Welcome to the Research & Development Division from L Aerospace.
Please vest your blast helmet and suit: Area subject to Uncontrolled Landings and Rapid Unplanned Disassemblies, usually followed by Incredibly Fast Air and Heat Expansion With Debris events.
The following states the current status for the Supported KSP versions:
- Fully Supported (exceptions when documented the Add-On's
- 1.4.1 (Maintenance)
- Unless really needed otherwise, add-ons are compiled against this set of libraries.
- 1.4.3 (Guaranteed Support)
- It's the last version with the older PQS system.
- 1.5.1 (Maintenance)
- There're not really too much changes (from the code point of view) from 1.4.5 to 1.5.1. But there're not that much neither from 1.5.1 to 1.6.1, so it's kind of pointless to fully support 1.5.1 - almost every 1.5.1 user can switch to 1.6.1, and the few that can't, will be served by 1.4.x or 1.6.x series add'ons.
- 1.6.1 (Guaranteed Support)
- 1.4.1 (Maintenance)
- Planned Support (when possible)
- 1.3.1 (near future)
There are no plans to support any other KSP versions at the moment.
Understanding the Different Teams on the Repository
In order to prevent confusion and misunderstandings, and to make my life easier by groping projects by support level, every project of mine is tied to a Team, and not to myself directly:
- These are projects that I effectively Maintain, Develop and Support.
- I accept responsibility and act properly when any of these projects breaks or cause breaks
- I fix bugs no matter they affects me or not.
- I create features, and/or improve existing ones.
- Eventually (but I try hard to avoid) it became incompatible with previous versions.
- Some are Officially under my Management on Forum (i.e., I withhold Copyrights and TradeMarks on the Historical Versions). These are the "New Management" forks. They are Mainstream.
- Others are parallel forks, that should not be confused or mistaken with the mainstream ones. These, are not on the "New Management" status
- All of them has '/L' on the naming.
- These, has "/L Unofficial" (abbreviated to "/L-U") on the name
- These ones I forked and adapted to some special needs of mine.
- They should be considered Experimental and Unofficial.
- I do not accept any kind of responsibility on them, does not claim official statuses of any kind and I don't provide support for it.
- You use it at your own risk
- But I try to help in issues as the time allows.
- I add some new features that suits me, but avoid deviating from the mainstream ones (unless that feature is horribly broken and it's the reason I decided to fork the thing).
- I only fix bugs that I introduced, or fix bugs that annoys me.
- I am not the Maintainer of the thing.
- Now and then one of these is "promoted" to the net.lisias-ksp Team, as I became the Official Maintainer of it (see "New Management" above)
- There are direct forks from the Mainstream (or even some parallel forks) where I apply patches and submit to the up-stream.
- I gladly do the same on the net-lisias-kspu ones, but this one is intended specifically to this.
- No releases are issued. No customizations are done. It's essentially a place where I fork things to then apply pull-requests to the upstream.
- It also plays a hole as "backups".
For the sake of curiosity, here is how I handle things here:
- Development is done on a branch called
KSP\x.xxfor KSP version specific development).
- New Releases are committed to the
devbranch, and the binary package is also committed to the
Archivebranch for historical reference
- A tag in the formante
PRERELEASE/x.y.z.bare issued on the
- The whole shebang is uploaded to the remote repository.
- The Release is created and commited to the DEV branch.
- Binary is commited into the Archive branch
- A GitHub Release is created.
- The Master is reset to the Release commit for broadcasting announces
- When applicable, the binary is uploaded to CurseForge and Spacedock.
Send your questions to <support at lisias dot net> . You can also create issues on the Project's Repository page.
[KSP:<plugin_name>] to the subject, or the automated filter system can filter out your message to the trash bin. Thank you.