Hi,
The old Alpha, d20, permissioned set up was outdated, outmoded and replaced by a better system - STATUS.
A set can have a STATUS - Alpha, Beta, Release, or TESTONLY. Which we determine when it's approved for inclusion.
The current method is similar to back then. A set is worked on by a lst monkey or monkeys. After the monkeys deem it complete, it has a license review, and after license review it has a data chimp review, which then it goes into the release as per normal, and a STATUS of Alpha (really unstable or experimental features), Beta (deemed clean, but could have bugs or incomplete features), Release (This has survived one full production cycle and has correct calculations, and is deemed to be bug free.
If your set is finished, we advance it in the jira as ready for license review. I'll try to get it in. If you miss the deadline, it is released separately from the release as an Out Of Cycle installable set, and is merged into the next production release cycle. The goal is once we hit BETA, all efforts should be on fixing any outstanding bugs as best we can.
Cheers,
Andrew
Hi Andrew,
This might not be the place to ask for it but what about newish sources (such as the Midnight 2nd Ed that I'm working on). I remember a long time ago of an alpha sources folder. Would this get thrown into there?
Thanks,-Dan
Sent from my iPhoneHi all,
James has the release scheduled for the 26th (3 days).
Content team is ready to transition to Beta. Nothing gating our team.
Only thing gating final production for us is the working converter to
convert all the existing sets to use FACT/FACTSET.
I understand Tom has some code to be entered before we enter Beta as well.
Is there any other last minute features people are working on and would
like to get in? I have some free time this week.
Cheers,
Andrew
Posted by: Andrew <drew0500@yahoo.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (4) |
No comments:
Post a Comment