Incoming 2.0 release - final call for contributions

[Tom Christie]

Right, I've claimed 2.0 will be out before the end of the month, which doesn't leave much time now.

We could pretty much keep polishing this thing indefinitely, so I'm planning on sticking with the slightly arbitrary release point.

If you'd like your feature in, in time for launch, now is your last chance.  Get cracking now, or over the weekend, and you should be in time.

If you're looking for things to do to help...

* The login/logout is unstyled - nice well-contained task for someone to pick off.

* The breadcrumbs disappeared from the browsable API at some point - shouldn't be too hard to figure out why and fix it.

* OAuth - sounds like a biggie, but actually it just needs a small custom auth and custom permission class, a bit of testing of django-oauth2-provider, and enough docs to get folks started on.  It bugs me that this hasn't been picked off yet - I'm tempted to just throw the damn thing in untested, label it 'experimental' and let the pull requests come.

* Would be great to see Issue #316 and #185 addressed, if only in part.

* Testing, reviewing, filling in any missing documentation, generally throwing things around and seeing what you can get to break.

My own remaining priorities are:

* Work on the tutorial - revising it into something a little more practical, filling out the missing few sections.

* Work on the 2.0 migration guide.

* Improving serializers and serializer fields documentation.

* Filling out some of the 'topics' documentation.

Of course I'm not expecting everything to just stop once 2.0 goes live, we'll be following up with plenty more, but it'd be nice to make as big an impression on first release as possible, so...

Cheers all,

  Tom

[Bruno Desthuilliers]

On Tuesday, October 23, 2012 5:19:43 PM UTC+2, Tom Christie wrote:

Of course I'm not expecting everything to just stop once 2.0 goes live, we'll be following up with plenty more, but it'd be nice to make as big an impression on first release as possible, so...

As far as I'm concerned, you succeeded.

I started using v0.4 in our current project three days ago, got the first user story to work in half a day (minimal "useless" api just to prove we have something working and our customer's information system can call on us) but wasn't really happy with it (done the "easy magic way" and I know next stories will require something that just won't work that way), was about to refactor it in a much less magical way when I saw this post. So I switched to the 2.0 branch and I don't regret it - fully refactored my code in another 1/2 day and it's _much_ more to my tastes, this time I'm fairly confident this will fully support our needs without getting in the way.

Cheers

B.

[Tom Christie]

Thanks Bruno, glad to hear it!

Yup I think it's been good to go since at least the last week or two.

At this point it's just a case of taking an extra weekend to polish up as much as possible, on the basis that first impressions count.