Maintenance releases?

[megatr0n]

There have been many new plugins release in the last few weeks.

When, can we expect to see maintenance releases to iron out and fix a few bugs.

 

[Cosmic]

Pretty much all bugs should be fixed at this point. There is an update cycle due for i think 4 mods in september as well, which should add new functionality etc to some of our existing mods ^.^

 

[megatr0n]

Are you sure?

There are a few bugs outstanding in the bug queue.

 

[Cosmic]

If you check the dates on them, those should be very recent (i.e in the process of being fixed) or very minor (which will be handled in the product updates)

Any important bugs get handled as and when they come up generally =)

 

[megatr0n]

So, you mean a patch is released and/or is re-packaged in the zip?

 

[Cosmic]

Yup, for most bugs the zip is just repackaged without a version ujpdate.

 

[chewbacca]

Is there some way to let us know if a package has been updated?

 

[Fillip H.]

Not really, but we let you know if you post an issue we believe has been fixed

Sent from my X10i using Tapatalk

 

[the_quilter]

Is there some way to let us know if a package has been updated?

This would be very helpful! Or at least some sort of email or announcement. When vBShout came out there were a few releases where the version number didn't change and there didn't seem to be any notification.

 

[Fillip H.]

Maybe I should take this opportunity to ask y'all a question;
What do you prefer,
a) collective maintenance releases with bugfixes
b) updated zips where we tell you to re-download the package

With a), there'd be a couple days delay where stuff remains broken until a collection of stuff is gathered so that it's worth pushing a version number update, but with b) there's the issues brought up in this thread.

 

[Trekkan]

b, just get it out there and tell me.

I don't need you guys to tell me what files are updated, whether or not the XML needs to be reimported.

I'll DL it, overwrite all files and reimport the XML. It takes more time to ask and wait for an answer, etc.

However, one key thing here, let me know you've made an update to the zip file. Just so I know.

Eventually, I think you should move to a more traditional versioning system. Meaning once a product is stable. It's a pain in the ass for you guys and adds more time though. But... I dunno, it's what I'd like to see. But really... just give me the damn files as soon as things are fixed.

 

[Deceptor]

I'll discuss with Bel something we've considered before, a global product that can reside in your AdminCP to check for updates to any DBT products - not just version updates but these bug fixes too which we do tend to resolve quickly and push them out

 

[the_quilter]

Here is a suggestion of what how I would do it. Say you make a small update to vBShout 5.0.0. Create an announcement saying there is a new update out and explain what is changed, call it vBShout 5.0.1 etc...large updates would change the version to v 5.1.0.

Zip it and release it.

Unless I'm missing some part of the process that is time consuming or troublesome, this should be fairly easy to do.

 

[Cosmic]

Here is a suggestion of what how I would do it. Say you make a small update to vBShout 5.0.0. Create an announcement saying there is a new update out and explain what is changed, call it vBShout 5.0.1 etc...large updates would change the version to v 5.1.0.

Zip it and release it.

Unless I'm missing some part of the process that is time consuming or troublesome, this should be fairly easy to do.

We'd run out of numbers =) Theres usually wellll over 10 patch updates for new products especially.

Plus, making the announcement, logging all of the changes etc, that all takes time that adds up. It might only be 15 minutes per fix, but you need to realise that over the entire team, there could easily be 10-20 of those fixes per week. Thats 5 hours that could have been spent improving things, or fixing things up etc.

TBH I think the vast majority of people would prefer that the products be better, than to have a new email every day telling them a line has changed on something that would probably never have affected them anyway =P especially as our product catalogue grows, those constant email updates would get quite annoying if nothing else xD

Personally I think a combination of the two is best. Updates are applied and uploaded as needed, and then once a week or so the version number is updated and a rough changelog added if required (though tbh, bug changelogs never get read anyway. and everyone's first action on finding a bug should be to download the latest files to ensure they have the latest version and see if the bug persists)