Lack of time is the main reason for this failure (remember that we, the Evince development team, are all volunteers), but it’s not the only one. During the 2.25/2.26 cycle we have started to work on the annotations stuff, although (as usual) a little bit late, when the feature freeze deadline approached. When we had the minimum support already implemented, we realized that poppler didn’t have support for writing annotations yet. I don’t know why, but I was quite sure it was already implemented. The thing is that there isn’t writing support for annotations in poppler right now. So we had, at least, two options: releasing evince 2.26 with annotations support in a read only mode or delaying the annotations support to the next cycle once again. Both have advantages and disadvantages, but the main reason why we decided not to release 2.26 with annots support is because we don’t think that annotations are useful if you can’t actually use them. I’m sure we were going to receive lots of bug reports about non editable popups.
So, what’s the plan? The idea is to implement writing support in poppler ASAP, and merge the evince code early in the next development cycle.
Despite the annots stuff, I’m very happy with the work done during this cycle, but I think I’ll better talk about Evince 2.26 later in another post.