Upgrade Misago to Django 1.8

[sirex]

Currently Misago 0.5 runs on Django 1.6 and Django 1.6 is no longer supported.

See: http://misago-project.org/thread/how-stable-misago-is-445/

[narun4sk]

@sirex can you remind me what was wrong with the 0.6?? As far as I remember the only problem was that it wasn't fully thoroughly tested? But it not necessarily mean it is unstable, does it?

[sirex]

0.6 is completely under development and simple don't work. You can try to run it yourself or you can trust my word, because I tried it to run and found message that sounded something like this: "Soon here will be list of forums, but this feature is under development.".

I talked with Misago author and her said, that 0.6 will be ready, when it will be ready. Anyway, 0.6 is in development for about 2 years.

See: http://misago-project.org/thread/how-stable-misago-is-445/

[sirex]

0.5 is the latest working version.

[narun4sk]

OK, convinced :)

Could you please tell me more about what steps must be taken to migrate misago to _Django 1.8_.

Doesn't it mean fully rewriting misago core? If so our project will become rather a fork of misago than being based on it.. lol

[sirex]

If I'm not wrong, 0.5 does not have tests or test coverage is very low. So in first place we have to rise test coverage. We can rise test coverage by writing functional tests using Django webtest. Usually functional tests are easy to write so it should not take too long.

When we have good test coverage (at least major use cases covered), then it will be save to start migration process to Django 1.8.

To migrate to Django 1.8 we will not need to rewrite Misago (probably :) ). I did migration to Django 1.8 on other projects, and usually it was matter of changing import paths or other minor issues and changes. So when tests will be in place, this should be the easiest part.

So first, we need tests.

[narun4sk]

@sirex We'll have to collaborate on this, as my django skills quite rusty now, and as you know I wasn't on the side of django fans :)

[sirex]

@narunask I think, this user story looks like high priority. Should we add it to current sprint?

[narun4sk]

This one is important but as well will consume most of the time to complete...

[sirex]

How about Python 3 support? I would like to have it 👍 .