Release 0.20 Planning

[elrido]

My main goal is to provide a stable and robust 0.20 release. As #15 shows, having many configuration options brings the danger that some conflict each other.

I have already begun to create unit tests for the zerobin class. A next step could be to automate the test creation so that based on a list of configuration options, settings and tests for these we could generate all possible combinations and for each case see if paste creation, display and deletion works.

@Hexalyse was working on the password function, maybe we could include that in the release.

Additionally it might be worth to merge @vikstrous branch with file upload support.

Both the password and the file upload functions should of course be configurable options for server admins (and for the users, if enabled).

[vikstrous]

Be careful what you merge. I did a lot of things on that branch and I'm not very proud of all of them. If it's just the file upload part, then that would be cool.

[marsjaninzmarsa]

There are another (another? didn't compared the code, to be honest) approach to file upload in sebsauvage#57, it may be easier to merge.

[elrido]

Thank you for your helpful advice! I will definitely look into both.

[elrido]

Quick update: Apart from the file upload I consider the state currently quite clean. So if you don't mind I will make a release without it and then look into @vikstrous next weekend. Its probably more helpful to provide frequent releases then to try to implement everything at once.

[elrido]

The 0.20 release is done, I did split of the file upload into a separate issue.