Demo 0.4.3 released; ahead to 0.4.4
31 views
Skip to first unread message
Efraim Feinstein
Jul 3, 2011, 3:44:10 PM7/3/11
to opensid...@googlegroups.com
Hi all,
Last night, I released the next demo version (0.4.3). The release notes are at http://wiki.jewishliturgy.org/Release_Notes/0.4.3
The main new features are in the backend:
- there's a job scheduler that will cache the first processing stage in the background, instead of doing it when there's a request for the document. That should save some processing time.
- new testing for the user api
- lots of bugfixes from 0.4.2
Looking ahead to 0.4.4, the expected features are:
- using the job scheduler for all stages of compilation.
- provide new APIs to interact with the job scheduler
-- instead of initiating a compilation immediately, POSTing a compilation job will return a URI to provide compilation status
-- have APIs that indicate the current status of compilation jobs
--- add the "status" column to the "my siddurim" UI to indicate as a front end to the status API
- begin documentation of the data APIs (will also likely result in bugfixes)
- eXist has changed its security system in their recent trunk, which tightened up on permissions. We need to do some code updates to make sure the code works with the new permissions system. This will likely show up in the data API testing.
Where I think volunteer priority should be:
- Finishing the 1917 JPS conversion project. We're really close!
- If anyone would like to help out *writing* the API testing code, I'd be glad to show you how. It would also potentially make a good intro to XQuery and/or PyUnit.
With few exceptions, the data URIs can generally be auto-discovered using HTTP GET (aka, browsed) while logged in.
A lot of the process is basically asking:
what happens if I GET, POST, PUT or DELETE this URI?
... and pass it correct data (and content-type)?
... and pass it wrong data?
... and are insufficiently privileged to access it?
The test should specify the expected return code and the features of the expected data.
Ze'ev's help in getting the user API tests working was definitely appreciated! Thank you!
Happy Independence Day (to Americans),
Last night, I released the next demo version (0.4.3). The release notes are at http://wiki.jewishliturgy.org/Release_Notes/0.4.3
The main new features are in the backend:
- there's a job scheduler that will cache the first processing stage in the background, instead of doing it when there's a request for the document. That should save some processing time.
- new testing for the user api
- lots of bugfixes from 0.4.2
Looking ahead to 0.4.4, the expected features are:
- using the job scheduler for all stages of compilation.
- provide new APIs to interact with the job scheduler
-- instead of initiating a compilation immediately, POSTing a compilation job will return a URI to provide compilation status
-- have APIs that indicate the current status of compilation jobs
--- add the "status" column to the "my siddurim" UI to indicate as a front end to the status API
- begin documentation of the data APIs (will also likely result in bugfixes)
- eXist has changed its security system in their recent trunk, which tightened up on permissions. We need to do some code updates to make sure the code works with the new permissions system. This will likely show up in the data API testing.
Where I think volunteer priority should be:
- Finishing the 1917 JPS conversion project. We're really close!
- If anyone would like to help out *writing* the API testing code, I'd be glad to show you how. It would also potentially make a good intro to XQuery and/or PyUnit.
With few exceptions, the data URIs can generally be auto-discovered using HTTP GET (aka, browsed) while logged in.
A lot of the process is basically asking:
what happens if I GET, POST, PUT or DELETE this URI?
... and pass it correct data (and content-type)?
... and pass it wrong data?
... and are insufficiently privileged to access it?
The test should specify the expected return code and the features of the expected data.
Ze'ev's help in getting the user API tests working was definitely appreciated! Thank you!
Happy Independence Day (to Americans),
-- --- Efraim Feinstein Lead Developer Open Siddur Project http://opensiddur.net http://wiki.jewishliturgy.org
Reply all
Reply to author
Forward
0 new messages