July 4, 2009 at 2:43 a.m.

Это хорошо что вы начали вести блог,ведь у вас это отлично получается и надеюсь будет еще лучше. Главное писать о том,в чем вы разбираетесь. Удачи. :)

July 3, 2009 at 3:02 p.m.

One more ticket to go :)

July 2, 2009 at 4:17 a.m.

First of all, people have the right to complain and its one of the greatest pleasures of humanity... lol

But I think people are not complaining about the open tickets and they are not complaining about the release delay... everybody that uses Django just like the way Django works...

But, for some reason the Django Team don't give us a frequetly CLEAR and DUMB update. The last update was almost 2 months ago...

I have a link for the roadmap and I know that at the moment this is the status... (http://code.djangoproject.com/roadmap)

Closed tickets: 539
Active tickets: 16 (translation, admin, forms, manuals,...)

BUT, I ACCESS THIS LINK EVERYDAY...

I think a lot of Django users would appreciate frequently updates at least every 15 days or something like that and I think it wont hurt.

My suggestion is (three options):

1) Frequently update of status for dumb programmers like me that can't read minds and don't wanna count open tickets in trac... it sucks!

2) Remove all information about future versions like this post (almost 2 months! Man!!! Hellooooo??? lol)

3) Change Django slogan to: "Django - The Web framework for perfectionists WITHOUT deadlines"

I hope you keep doing this awesome framework...

Congrats

July 1, 2009 at 7:57 p.m.

As someone who uses Django in a production environment, I’m very thankful they are holding back the 1.1 release until all the critical bugs are resolved.

If you want the release out sooner then maybe you can open the bug tracker and see if you can offer some assistance with any outstanding bugs, I see there are open tickets for language translations and documentation as well as those requiring Python and Django expertise.

Alternatively there are other frameworks out there that are happy to push out more regular, slightly buggier releases that you might be interested in.

I’d much rather the developers spend their time trying to resolve the outstanding bugs, rather than posting regular blog entries, keeping all those people happy who are too lazy to open the bug tracker and see why the 1.1 release is being delayed.

Keep up the great work Django team, your efforts are appreciated.

July 1, 2009 at 4:52 p.m.

"We're not setting a timeline for the 1.1 release because the remaining issues are "blockers": they have to be fixed before we can put a release out."

Since they didn't set a timeline, it doesn't make sense to write "hooray, just 3 bugs to release!". You can see by yourself in <a href"http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&component=!Translations&component=!Documentation&milestone=1.1&order=priority"> the provided link</a>. If they already said that before correcting all issues presented in the link the 1.1 is not going to be released, everyone can see the overall status just visiting the link without needing them to post here every week.

Is this the best way to conduct an open source project? I don't know. If it's not the best one, django itself is going to lose market. If it's not this case, then it really doesn't matter.

July 1, 2009 at 9:34 a.m.

Hey naysayers, it's getting pretty old.

You know, there ARE other frameworks out there. If you don't like how this is team is running things, feel free to switch at any time. I am sure the majority of individuals here wouldn't miss your your bitching.

Keep up the great work Django team!!! Thank you for saving me days worth of work. Numbers are arbitrary, perfection is not.

June 30, 2009 at 7:26 p.m.

Once more...

You are generating expectation...

Expectation is evil because people will loose confidence...

I know this is an open source project, but listen to us and update the site more frequently please...

June 29, 2009 at 9:29 a.m.

ooo

June 28, 2009 at 4:41 p.m.

@Daniel Gerzo, that is why I'm developing against trunk, since I started my project in the 0.97 days. When v1.0 came out I released a version against the stable thread, but after a while when 1.1 was maturing I started to release against the SVN version again because I needed the. OK, it's only a non critical intranet app, but none the less, I have never experienced any serious issues. The only thing I do is that I keep the release version on its own thread and only update the development version and fix when needed.

That said, I agree that minor bugs should be propagated to the next release with proper notifications..and that it is awfully quiet on this blog on what intricacies exactly are keeping 1.1 from appearing.

June 28, 2009 at 11:41 a.m.

@John

I don't want to argue here but well when I wrote my message I was hoping to avoid this lame/common excuse of open source project: if you are not happy, contribute ...

Do you really believe that my contribution at this stage would make any difference ? I never understood that the release was late because of a shortage of contributors.

If I contribute, it will be by writing a contrib module. At this stage, if I was contributing to Django core I would do more harm than necessary. Please, don't ask all Django users to be Django guru, it just makes no sense.

So it cannot be said enough time: "open source does't not mean I am not releasing on time unless you help me".

Thanks Daniel I would not say it better.

I have high respect for all Django contributors ! Thanks for your beautiful work.

June 26, 2009 at 4:30 p.m.

Time-based releases are _so_ much better than feature-based releases; that's what we have learned in the past in the FreeBSD project. Minor bugs should not delay the release that long, it keeps people using old release for longer period of time (avoiding them to track critical changes), the new version gets little testing, etc, etc. Releasing a bug-fix release (even more) quickly is just better than not releasing anything...

June 26, 2009 at 7:20 a.m.

Just don't open closed bugs, like I did once. :)

June 25, 2009 at 7:28 p.m.

Well, sorry if I sounded over-critical, I didn't mean that. I have tremendous respect for the developers of Django, and will try to contribute when I have learned more about it...

June 25, 2009 at 9:41 a.m.

@Pascal, Michael

It can't be said enough times: this is an open source project. YOU can contribute to fixing that bug if you're so eager. Some people do this for free.

June 24, 2009 at 9:25 a.m.

Whilst I agree with the majority of the frustrated delay messages..I gotta say, to me it seems rare enough to get so much transparency with a new, significant release. So whilst I'm fit to burst in waiting for 1.1 I applaud the fact I can easily see exactly what is left to complete. Something a lot more software/hardware/frameworks releases could adopt?