You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The abstract specification *.pdf file generated by building the ASpec session is labeled with the seL4 API version number, which has not changed in the past four years. However, it seems that the abstract specification has undergone some substantial changes over that time period. I have encountered multiple seL4 specifications which are quite different from one another, yet list the same version number.
I found this confusing. Wouldn't it be better to label the abstract specification with the seL4 version number, e.g. 7.0.0?
The text was updated successfully, but these errors were encountered:
This is now addressed in e6c6535, at least to the degree that PDF generation will now automatically include the seL4 version and repository hash from which the document is generated.
The PDF is still not automatically generated and published to the website for point releases. Since that's really a separate issue, I think we can close this one.
The abstract specification *.pdf file generated by building the ASpec session is labeled with the seL4 API version number, which has not changed in the past four years. However, it seems that the abstract specification has undergone some substantial changes over that time period. I have encountered multiple seL4 specifications which are quite different from one another, yet list the same version number.
I found this confusing. Wouldn't it be better to label the abstract specification with the seL4 version number, e.g. 7.0.0?
The text was updated successfully, but these errors were encountered: