Ths Parts Update process is automated to the extent that it makes sense to do so.
However there are some manual steps involved :
- Header errors slip through review so the release candidates are checked programmatically and fixed manually.
- Dependency checking cannot be fully automated. I don't want to release Certifed subparts/primitives unless they are in use (i.e the parent part is Certified). The dependency checking is particularly important for "fixed" parts.
- Creating the Windows install file cannot be done on the Linux server, so there is a manual ftp step to build this on my Windows system.
As usual this boils down to quality versus speed. I prefer to take the time to check the quality of the Parts Update, which mitigates against future corrective actions and impact upon the user community, rather than release an update with errors that then need fixing. It would not be appropriate to automatically release Certfied Parts into the official library.
I agree that two releases a year is inadequate, and my personal target for 2011 was three (as was the case in 2009 and 2010). Unfortunately due to pressure of other work, I failed in this aim, but as has become traditional, an end-of-year update (2011-02) will be issued within the next few days. I am not able to commit to fixed release dates, because my availability to work on this volunteer project is constrained by other demands on my time - not least my paying job.
I suggested here that I was open to discussion on how the Review community could be extended.
However there are some manual steps involved :
- Header errors slip through review so the release candidates are checked programmatically and fixed manually.
- Dependency checking cannot be fully automated. I don't want to release Certifed subparts/primitives unless they are in use (i.e the parent part is Certified). The dependency checking is particularly important for "fixed" parts.
- Creating the Windows install file cannot be done on the Linux server, so there is a manual ftp step to build this on my Windows system.
As usual this boils down to quality versus speed. I prefer to take the time to check the quality of the Parts Update, which mitigates against future corrective actions and impact upon the user community, rather than release an update with errors that then need fixing. It would not be appropriate to automatically release Certfied Parts into the official library.
I agree that two releases a year is inadequate, and my personal target for 2011 was three (as was the case in 2009 and 2010). Unfortunately due to pressure of other work, I failed in this aim, but as has become traditional, an end-of-year update (2011-02) will be issued within the next few days. I am not able to commit to fixed release dates, because my availability to work on this volunteer project is constrained by other demands on my time - not least my paying job.
I suggested here that I was open to discussion on how the Review community could be extended.
Chris (LDraw Parts Library Admin)