Roadmap/Release Criteria/Milestones?

[jkoritzinsky]

I just noticed that we don't have any of these, so we should get something down. What's our release criteria for our next version? What features are we planning on for the next version? V1.0?

Can we get some of this planned so we have some direction we are working toward?

[magico13]

I was recently thinking about that as well.

There's not really a "current" version. Do we want to release what's available now as a sort of beta or pre-release so we can start getting some outside testing, or should we try to finish more features first and then expand each feature with subsequent updates?

I think a push to get a fully featured release for 1.0.5 doesn't seem too far-fetched, with everything before then as a pre-release. If for some reason we can't do that, then 1.1 probably isn't too far behind 1.0.5.

FMs: We've got Payroll and Salaries up now (I haven't gotten a chance to test them yet), which I'd consider the two most important FMs. The others that I was thinking about were Building Maintenance and active flight costs (for ground crew primarily). We should consider making a list of these somewhere and decide who should do what. If anyone has a quick idea for one, don't hesitate to write it up. Even if they're not "defaults" we can still have multiple packs of FMs or individual downloads.

Loans: I believe you (jkoritzinsky) are working on those at the moment. I'm not sure what all you've done with them, but based on your other contributions they're probably pretty awesome. Once you've got something up and running for those, then we can do testing and see if anything should be altered. If you weren't working on those, then we should discuss what we want to do for them and figure out who will primarily work on that. If we want to do a few pre-releases then I think we can save loans for a later one.

Core features:

• I'd like to see a history option. Minimally to view totals for each quarter/year up until the current date, but optimally with detailed histories about when invoices were paid and money was given to the player.
• Global settings. We provide FMs a way to save settings per-save currently, but do we want to have a single global settings file. Some FMs might use it for default settings, the core could use it to store things like the Skin to use. Alternatively, each FM can define its own external settings file quite easily.

That's all I can think of off the top of my head at the moment. I apologize for not being very active lately. I haven't really touched KSP or KSP-related things in a while due to life+loss of interest. I've got a job interview later this week so I'll be out of town this weekend, but starting next week I'll probably start working on things again.

E: If Payroll and Salaries are functioning, then now might be a good time for the first full pre-release. The question then is should we wait to put it on CKAN until v1.0, or do it now?

[jkoritzinsky]

FMs: Maybe we should create an issue on the BROKE_Defaults project for each proposed FM. That's one way we can track ideas. We could use the issue threads to figure out the details and balance of each.

Loans: The code for managing issued loans (tracking payments, adding late fees, etc.) is already committed. The only thing that's missing (which is pretty important) is any GUI to show the player loans to take out.

Core features: I like both of these features. We don't need them for our a beta release, but we definitely should aim to have them for v1.0.

I'm all for putting a pre-release version out now. Our last one is extremely out of date (pre-InvoiceItems) so we definitely should get one out sometime soon.

[johnqevil]

I'm all for having issues open to track milestone progress for the Core and each FM. The only thing the Core needs for a proper release is a setting to change the invoice interval, unless you added it while I wasn't looking :).

[magico13]

I put out a second pre-release, including the two default FMs. I didn't get a chance to play too much with them, but I fixed a bug in the core and noticed a few odd things. I'll make separate issues for those.

I think any larger features we want should each have their own issue that we can use to discuss, then we can use this one to figure out what we want in each release up to 1.0 and set up milestones.