Opened 6 years ago
Closed 6 years ago
#1227 closed task (fixed)
Copy over pdfs of updated correlation function tutorial before 4.2.1 release
Reported by: | smk78 | Owned by: | smk78 |
---|---|---|---|
Priority: | blocker | Milestone: | SasView 4.2.1 |
Component: | SasView | Keywords: | |
Cc: | Work Package: | SasView Documentation |
Description
The correlation function help file and tutorial have been updated to fix #1225.
Unfortunately, the tutorial build server is not building at the moment so there are no pdf's of the updated tutorial to distribute with the release. Hence this blocking ticket.
Wojtek is aware.
Change History (3)
comment:1 Changed 6 years ago by butler
comment:2 Changed 6 years ago by smk78
I wasn't aware that the website change had also altered how we deploy the documentation. This ticket and #1229 were therefore trying to ensure that the bundled documentation and the web documentation were in synch as per the instructions in /tutorials/README.md If we now have full auto-deployment and these instructions are deprecated, great!
comment:3 Changed 6 years ago by butler
- Resolution set to fixed
- Status changed from new to closed
not fully deprecated but lots of confusion with the changes due to the new website. At this point however this ticket can be closed. @smk78 has updated readmes and copied files to appropriate places. Releases of Tutorials happens independently of SasView releases which will bundle the latest tutorials at the time of the release. Discussion about whether to keep the full pdf tutorials bundled in the release or just have SasView point the the appropriate website page is ongoing. Either way this ticket can now be closed.
Note this is not a 4.2.1 but a 4.3 release issue. Ticket #1225 was created about a week after the final release process was started and a day after the pre-release (i.e. end of process except to check that the release builds did not introduce anything untoward) was released. These tutorials are therefore not included in that release build. However, the tutorials are a separate repo and I would argue can be updated on the website independently of the SasView release cycle. of course if that is the case it probably should go against a different milestone than the release milestones?