1. This is not possible, but easy to work around by creating a release that lasts enough to contain all your sprints. Releases carry the vision for a consistent set of features that will be provided by a major version of the product. Nothing prevent to build and deliver versions more often than that: every sprint, every day, or several times a day.
2. In a single iceScrum project, this is not possible. Can you elaborate on why you need this feature?
iceScrum follows the rhythm of Scrum so the planning is tied to a sequence of iterations materialized by sprints. I think that managing continuous deployment and continuous delivery with Scrum is a methodological issue rather than a tool one. You can get rid of sprints in iceScrum the same way you can work around releases: just create a single sprint that lasts several months.
