What are the new Sybase ASE/REP patches SPxxx? [closed] - sybase-ase

Sybase is going to release some new ASE/REP patches SP100 then SP101 instead of ESD#
What will be the differences between ESD# and SP100?

According to SAP/Sybase it's just name change to fall in line with the SAP way of doing things, as they continue to integrate product lines. SP stands for Support Package, where ESD stands for Electronic Software Distribution, but functionally they are both patches to prior software releases.
Some of the expected changes between versions of ASE can be found here:
http://www.sybase.com/detail?id=1038641
More about the change in patch naming:
http://www.sybase.com/detail?id=1099335
Rob Verschoor, one of the SAP Sybase Engineers just posted a blog about this very topic:
http://scn.sap.com/community/sybase-ase-custom-applications/blog/2013/06/02/sybase-ases-version-numbering-goes-the-sap-way

Related

sugarCRM 6.5 still updated?

I'm a little bit confused. I know that sugarCRM no longer supports version 6.5 as of 2016, but there are still security patches being applied in 2017 as per
http://support.sugarcrm.com/Resources/Security/sugarcrm-sa-2017-005/
Does this mean that no new functionalities will be added but security patches and bug fixes will still be applied?
Support vs maintenance
As per Clint's thread: https://community.sugarcrm.com/thread/18434
We are expecting to support and issue maintenance releases to v6.5
through summer 2015 when v6.5 hits it end-of-support period.
So I'm assuming that support for 6.5 ended in 2016, but on this page http://support.sugarcrm.com/Resources/Security/sugarcrm-sa-2017-005/ we see the mention:
The list of affected products reflect all currently maintained
versions at the publication date of this advisory.
Which is a bit confusing.
Thank you
As per Sugar support. So it's no longer supported in any way shape or form it seems
6.5 is no longer supported and no additional patches of any kind (including security) are being developed. End of life for 6.5 was
reached in July 2017. Our current supported versions list can be found
here: http://support.sugarcrm.com/Resources/Supported_Versions/. This
blog post may also be helpful to read, especially if you're using CE:
Sugar Community Edition open source project ends.

Movable Type 4 vs 5

I have a Movable Type site running MT 4.38, and I was wondering whether I should upgrade to 5.
For a while, MT 4 and 5 seemed to have been developed concurrently, but now I only see activity in MT 5. Has MT 4 been abandoned?
The person using the site is change averse, so I only want to upgrade if it's absolutely necessary (i.e. security issues).
Thanks
Yes. Movable Type 4.38 has a patch for a security vulnerability which you should be sure to apply. But beyond that, you should absolutely upgrade to Movable Type 5.2.3.
The big reason is that Movable Type 4.38 will be end-of-lifed on December 31, 2013. This means that there will be no security updates for Movable Type 4.38 after that date.
Movable Type 5 has a number of great new features that are huge improvements over MT 4.38:
New and improved Rich Text Editor based on TinyMCE
Revision history on the most-used objects in the CMS
List-management framework enhances Movable Type's ability to manage large amounts of data inside the CMS
Sortable categories and folders
Template tags for things like mt:EntryPrimaryCategory
Enhanced multi-blog support
Huge support improvements for Webkit-based browsers (Safari and Google Chrome) as well as IE 8 and 9
Login failure detection, allowing either account or IP address lock out
With all due respect, no one should be running a version of Movable Type that is no longer supported with security patches. It's foolish to think that any one person can know all of the possible security issues in an older version of a Content Management System such as Movable Type.
Yes, MT4 is no longer developed. It still receive security patchs every few months, but there will not be a new version.
As for what you want to use, MT4 and MT5 have a different set of plugins. So if you want to upgrade, check that the plugins that you need support MT5 or have a MT5 replacement.
Upgrading would work without any problem if you are not using 3rd party plugins.
If you're using 3rd party plugins, you might encounter compatibility issues because the v5.x architecture is much different than 4.x.
Before considering to upgrade to v5.x you may like to check your 3rd party plugins and see if there is a version that works with v5.x.
Another thing to consider is to clone your installation and try to upgrade it on a different domain/folder or on a stage server where you could check that everything works before upgrading your live installation.
Alternatively you could order a professional movable type upgrade service from:
http://www.movabletypeupgrade.com/

When was Progress DB 9.1 and 9.1D released?

I have an old application that I manage that runs on top of a progress database. I'm trying to gather some information, for various reasons. At a minimum, I need to know when Progress 9.1 and 9.1D were released. I mention these two versions because we are using 9.1D and, I assume, the "D" revision is probably just the fourth iteration in miner updates since the initial release of 9.1.
Optimally, I'd like to find a source-link to a Progress DB change log. However, questions for documentation aren't typically acceptable around here. Instead, I'm asking for the date these versions were released and requesting that you provide a source that I can explore further.
9.1A was 1999, 9.1D was 2002.
9.1E SP04, the very last release of version 9, was released in 2004.
With version 10 the product name changed to "OpenEdge". Which is much easier to google than "progress" ;)
If you actually have a given release of Progress installed you can look in the "version" file. It will tell you what the build date was.
For a general idea: http://www.oehive.org/VersionHistory

Is there any point in writing pre-Mango (7.0) Windows Phone 7 applications

Inspired by an exchange on a recent question, I wanted to know whether there is any good reason to develop Windows Phone 7 applications that target pre-Mango models, i.e. by creating applications that target the 7.0 APIs rather than the more recent 7.1 APIs.
My impression was that because the Mango update has now been fully rolled-out, there is very little reason why anyone would have a phone with a pre-Mango OS. My guess is anyone with a pre-Mango phone probably never connects it to their computer and probably does not download applications.
Are there any good statistics on OS version demographics that can inform this decision?
I know from the analytics of my apps that there are still people out there using pre-Mango versions of Windows Phone, but as you point out, they are unlikely to be connecting their phone to their PC to perform updates or even update apps they've already downloaded (my wife for example would still be on the original shipped version if I hadn't updated her phone myself!).
With that in mind, personally, I don't see the point in creating applications now that target pre-Mango versions of the operating system. The return is highly unlikely to warrant the effort.
There isn't much of a reason to target pre-Mango as opposed to Mango as the upgrade is available to all models of phone currently, and for free.
It is worth keeping on the latest SDK for no other reason than there is no reason not to... lol, made sense in my head. Things like performance improvements, bug fixes, new features etc are all reasons to keep up with the latest, as you are likely aware.
The only reason I would target an older SDK is if a particular version of the phone OS was not available to a certain piece of hardware for any reason.
Then again, if you can make your app with the lowest common SDK, why not - it will in theory only increase your user base as backwards compatibility is enforced, over choosing a newer and not-completely-rolled-out version. You just personally suffer the older APIs and miss out on new features. However, I see this counter-point as a largely academic argument and adds little weight to the choice of older versions.
Save yourself the headache, go with the new stuff. Anyone actively using their phone enough to also use your app is likely hot on updates.
I don't do 7.0-specific programming any more since the roll out of Mango is now available pretty much everywhere I'm interesting in deploying apps. This question will rear it's head again when vNext is released (with potentially updated hardware requirements / sensors, etc), but for now I can't see much reason to target the old version.

osTicket Open Source Alternative

For anybody who uses osTicket you may have noticed that it is no longer being developed and it has been two years since the latest update. I want to switch to a open source ticket software which is supported and updated.
Any tips on what to use?
I have obviously googled and found some great looking solutions but I would be interested in getting opinions from people who actually use alternatives.
You should consider OTRS - it is open source, and actively developed. It has a strong company backing it, a vast number of bigger and smaller companies using it, and it has a strong community with active mailing lists and forums.
Actually osTicket isn't dead. In fact there were several release candidates available at the time that this question was posted. Their new stable version 1.7ST (desoto) was also released on 02 apr 2013. (After 6 released candidates [RC] and several developer preview releases [DPR])
Check it out at: https://github.com/osticket
or at http://osticket.com
You could also use GLPI. It is written on the php/apache/mySQL stack, was started in 2003 (I think) and is still actively developed: 1 major release abut every 2 years and minor ones 3-4/year.
It is translated in about 40 languages.
Very good as a ticketing system, but also very strong for asset inventory (integration with Fusion Inventory and OCS Inventory).

Resources