Link to download older Tivaware releases?

Hi John,

I'm curious, what is the reason for this search?

May I suggest that if you identify the desired version here - one user may have - and be able to pass to you quickly.

Hello John,

Which version of TivaWare are you looking for? May be I may have some installers.

Regards
Amit

I will note here that this is not an uncommon requirement.    Although, the question that arises is if you have it certified with an older version of the library why do you not have a copy of it? I know of some possible answers to that as well, some people are reluctant to share copies of libraries even when allowed, preferring the consultant working with the code get a pristine copy direct from the source¹.

Another set of reasons for need older versions may be performance, support for older devices, bug fixes etc...

There are definitely people on the forum working with older versions so please let us know which version you need.

Robert

1 - There's also "Fred's laptop got run over by a bus and it had the only copy" ;)

Robert Adsett said:

"Fred's laptop got run over by a bus"

And that's especially "bad" when said bus was "controlled" by Fred's laptop...

Amit,

Is there any reason we don't archive the old versions anywhere so that they can easily be searched and downloaded?

John

Thanks Amit!

I must register my differing opinion / protest.

Amit Ashara said:

Also if there is a bug reported on the older release which is applicable to the newer release, a fix is made and when sufficient fixes accumulate we make an incremental release.

Like the last incremental release? The list of fixes was quite formidable and the "when" was quite some time. With incremental releases like this, users are going to have to resort to working around the bugs in their own software and/or making local, unofficial patches to the provided library. This essentially ties them to a specific version, which may well differ from the "latest & greatest" release. At that point upgrading to a newer version, even if it is a bug-fix-only release, might not be very simple. Especially if any kind of code audits are involved.

Amit Ashara said:

Otherwise it becomes managing different software releases based on archived data base tougher to handle.

I do not understand how having previous releases available complicates anything. The previous versions need not be supported, just have them available for download for those who need them. Have some sort of disclaimer saying "this version shouldn't be used and is only provided for archival/historical purposes" or something like that if you're afraid of any legal consequences.

Amit Ashara said:

when sufficient fixes accumulate we make an incremental release

Another comment on this. Really just one acknowledged bug should be enough to make an incremental release - within a few weeks if not days. If that causes major trouble, it is a very clear sign that your software version management system (be that software or human-based, or a combination of both) is not up to the task and should be reviewed. There are much bigger software projects that do not have a problem with pushing out bugfix releases on a very short timeframe.

Hello Veikko,

Veikko Immonen said:

With incremental releases like this, users are going to have to resort to working around the bugs in their own software and/or making local, unofficial patches to the provided library

That is why we always try to keep the patch as much same as the final code and notifying the forum post if we make a change to it. This will reduce the tie-up issue.

Veikko Immonen said:

The previous versions need not be supported, just have them available for download for those who need them

Good point, but I am not sure if archiving shall be supported on the main web page. We may have to move to a wiki page

Veikko Immonen said:

Really just one acknowledged bug should be enough to make an incremental release - within a few weeks if not days

I would disagree. The amount of work and checks that need to be made is not a few days. I can be on the forum or behind the release machine!!!

Regards

Amit

Amit Ashara said:

That is why we always try to keep the patch as much same as the final code and notifying the forum post if we make a change to it.

Amit Ashara said:

The amount of work and checks that need to be made is not a few days.

I find these two statements contradicting. And as I said before - if an incremental release causes many days worth of work, then your software version control system and/or development methods just don't cut it. Working on the patch is one thing, releasing a patched version is another - does the latter really take many days?

Amit Ashara said:

I can be on the forum or behind the release machine!!!

From previous postings I had the impression that you were not even part of the software team, rather just communicating with them. From this post I gather that you are the software team - is this really so? I smell a serious understaffing issue here.

Another point - if you're on the forum putting out fires caused by said bug, then you really should rather be behind the release machine preventing further fires.

Hello Veikko,

The 2 statements are not contradictory. As a bug patch is released based on complexity of the issue, checks are done based on tests run around the API. If there is any break to something unrelated, a debug cycle is begun and patch updated. This is what takes time and need independent set of eyes (not available all the time). Doc changes, approvals also are put in the pipe. I wish it could have been simpler.

I work as part of both teams to ensure information is bridged. Otherwise we end up speaking different languages due to different set of job roles. Now who better than you to understand, that I made a commit on the forum for the release and ended up delaying it for almost 5-6 months and hence the bridge person becomes "slightly" important to ensure that nothing gets missed.

Anyways, we have another round of bug fixes happening, but the cycle time is good this time around... and check boxes waiting for new application codes...

Regards
Amit