Where oh where is the new release?

LightWolf posted 16th of August 2010 in Community Voice. 14 comments.

Well it is now the middle of the month and I see by the trac that they have added more things to be fixed on this next release. I thought we were going to get this release this month? i don't see how it can happen when we have more fixes added now then when it first started. I still stand by my prediction of a release in Sept. If they release this now , I am worried they will do as they have done in the past and push the left over fixes to the next release. Boonex, can we at least get 1 software release where you have fixed all of the tickets, not just shove them off to the next release?

Comments

Newest

·Oldest

·Top

Please login to post a comment.

Nathan Paton•16th of August 2010

You haven't learned a thing about their releases through all these years, have you?

Permalink•Reply•Plus•0 pluses

Stuart038•16th of August 2010

As people report more bugs, things are bound to be delayed. Because a lot of those bug reports are pertinent to the upcoming release. Now we don't want to be complaining that 7.03 causes more problems do we :-) (tongue in cheek!)

Permalink•Reply•Plus•0 pluses

CodeSatori•16th of August 2010

It's an interesting venture alright --- drop in new tickets and see how far they can travel! =)

Seriously though, if the reported bugs and fixes are dependent on each other, there's no point in releasing partial fixes. On that note, it's probably a good idea to delay "independent" tickets and crunch away the tickets with dependencies first to increase overall stability. Once the platform housekeeping is done, individually fixable bugs shouldn't be much of an issue to clear out of the see more

Permalink•Reply•Plus•0 pluses

LightWolf•16th of August 2010

Thanks for the responses, but I was really asking Boonex this question.

Permalink•Reply•Plus•0 pluses

LeatherSportB•16th of August 2010

For some reason Boonex won't have more then one minor version road map open at a time (e.g. start the 7.0.4 road map when working on 7.0.3). So anytime a new ticket is opened, it delays the release. Obviously some tickets have to go in the current road map, but many could be delayed. And while I do not want to be installing updates all the time, 'mega updates' have their own issues. When you have changes to your site the bigger the update the harder it is to fix things.

Permalink•Reply•Plus•0 pluses

DeeEmm•17th of August 2010

Permalink•Reply•Plus•0 pluses

Andrew Boon•17th of August 2010

Everything is back on track now, but it hasn't been for a while. Due to DDoS attacks we had to work on Unity more, then the big upgrade of forums and a new security report on Dolphin added some unplanned overhead. It's only now that we have all developer back on Dolphin and it should be ready soon.

I keep saying that we try to commit to a certain schedule, but such is the nature of development of a web-script, you can't predict unless you overestimate. So, we work on 7.0.3 now at full pace and see more

Permalink•Reply•Plus•0 pluses

houstonlively•17th of August 2010

@ Andrew Boon ...RE: we have identified some weak spots (and their roots) that need large overhaul....

Mind sharing what those are? (Just want to see how closely your list matches mine)

Permalink•Reply•Plus•0 pluses

JasonVan•17th of August 2010

Perhaps I'm just crazy, but am I the only one who would be fne with smaller but more frequent updates? I too hate waiting. I know it's ideal to have as many issues as possible resolved in each release, but we do not live in an "ideal" world... we live in the real world. How about smaller more frequent updates? Or is that just too much work for too little reward?

Permalink•Reply•Plus•0 pluses

LightWolf•17th of August 2010

Thanks for the quick reply Andrew. It is nice to see such a quick response. I really appreciate it and am sure other members do to.

Permalink•Reply•Plus•0 pluses

CodeSatori•17th of August 2010

@JasonVan on frequent updates:

I believe the problem with issuing frequent releases has to do with the fact that many of the problem areas are interrelated, arising from old D6 architecture that's falling off the sleigh with all the new D7 features being coded in. This is of course something that would have been best addressed before public alphas and betas for D7.0.0 were released...

Permalink•Reply•Plus•0 pluses

dolphin_jay•17th of August 2010

I sure hope that .xml call is on that list of yours. With that fixed there goes a few hundred posts of my server was shut down because of high usage !

Permalink•Reply•Plus•0 pluses

Andrew Boon•17th of August 2010

After the release of 7.0.3 we'll compile a more definitive list of tickets in Trac for 7.1 to show what's planned.

CodeSatori is right, in a way, Dolphin 7 still has too much left from the old architecture and code, although it has been significantly improved. It can still be improved and brought up to date, but it's just a little more work-intensive than working with a brand-new platform. We keep tearing ourselves apart trying to bring Trident soon and still maintaining D7 in good shape, but see more

Permalink•Reply•Plus•0 pluses

CodeSatori•19th of August 2010

@dolphin_jay: If you look up dosDawg's thread on XML.php and my notes, I think we're onto something as far as identifying the problem goes. Issuing a fix is likely a more involved a process!

Permalink•Reply•Plus•0 pluses

Where oh where is the new release?

Blogs

Help

Product

Company