Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confusing version number for Abstract Specification #21

Closed
sdconsta opened this issue Jan 25, 2018 · 3 comments
Closed

Confusing version number for Abstract Specification #21

sdconsta opened this issue Jan 25, 2018 · 3 comments
Assignees

Comments

@sdconsta
Copy link

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?

@lsf37
Copy link
Member

lsf37 commented Jan 25, 2018

You are right, absolutely. It would be even better to automatically generate the PDF for each release.

It's been on our todo-list for a while, I'll bump up the priority.

@lsf37 lsf37 self-assigned this Jan 25, 2018
@lsf37
Copy link
Member

lsf37 commented Feb 7, 2018

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.

Do you agree?

@sdconsta
Copy link
Author

sdconsta commented Feb 7, 2018

Yes and yes. Adding the commit hash is a nice touch. Thanks!

@sdconsta sdconsta closed this as completed Feb 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants