Provide CCBV for master (ie development version) as well as released versions

[jaylett]

Having both 1.3.1 and 1.4 is great, but for people working towards the next version of Django having a version rebuilt periodically off master would be awesome too :-)

[meshy]

I was planning to do this with tagged alpha, beta, and release candidate versions. Do you think it's worth having master as well?

[jaylett]

I think so — it'd have helped me today during the Djangocon sprints :-)

Of course I could run it locally, but I think it'd be a helpful option. You could perhaps just not link to it from the front page, but provide a link elsewhere? To avoid overwhelming/confusing.

[meshy]

OK. Currently the import script depends upon the version of django it's parsing being installed into the same virtual environment as the running website (nasty I know). I need to work out some sort of better arrangement for importing/updating the database before I can really implement this. Issue #39 therefore blocks this for the moment.

[meshy]

@jaylett Just to say that this issue has not been forgotten, I've just had an awful lot to do! I am still investigating a way to automate having the dev version on the site, but for the moment I thought you might like to know that the WIP version of CCBV is deployed to http://ccbv.herokuapp.com/ and has the cbv data for Django 1.5b2 on it. There are a few bugs to iron out (especially #56), but like I said, it's a work in progress... Hope it comes in handy to you :)

[mlen108]

Bump.

@meshy I think it is still very good idea if ccbv provides docs for alpha/beta/master (whatever you prefer) versions of Django CBVs.

[meshy]

Agreed, it still is. We need a way to automate this, and to ensure that the redirects to the latest version don't use these beta/master versions.