Due to a serious security issue with the new Flask notebook (see
#13270), it has been decided on that ticket not to ship sage-5.2 with
sagenb-0.9.0.
Since I see no reason why the other tickets in sage-5.2 couldn't be
released, I will unmerge #11080 and related tickets and release sage-5.2
still with the old notebook.
On Monday, 23 July 2012 15:06:35 UTC+8, Jeroen Demeyer wrote:
> Due to a serious security issue with the new Flask notebook (see > #13270), it has been decided on that ticket not to ship sage-5.2 with > sagenb-0.9.0.
> Since I see no reason why the other tickets in sage-5.2 couldn't be > released, I will unmerge #11080 and related tickets and release sage-5.2 > still with the old notebook.
On Monday, 23 July 2012 15:06:35 UTC+8, Jeroen Demeyer wrote:
> Due to a serious security issue with the new Flask notebook (see > #13270), it has been decided on that ticket not to ship sage-5.2 with > sagenb-0.9.0.
> Since I see no reason why the other tickets in sage-5.2 couldn't be > released, I will unmerge #11080 and related tickets and release sage-5.2 > still with the old notebook.
> > Could we please, please, have it added and everything related re-merged > > back? > Somebody needs to create a sagenb spkg fixing this and add this to > #13270, and it needs to be reviewed.
> Due to a serious security issue with the new Flask notebook (see
> #13270), it has been decided on that ticket not to ship sage-5.2 with
> sagenb-0.9.0.
Since #13270 is fixed, that decision has been undone, and sage-5.2.rc1
now contains sagenb-0.9.1.