Is there somewhere where detailed release notes are located? I am specifically looking for what's in v8.24 and v8.24.1, as I am using 8.23.
Thanks in advance.
The full changelog between any two versions can be found on Github.
We do not publish any written release notes - personally, I think that we should get better at that.
Currently I am using angular v1.2.26. When I upgraded it to v1.5.0(or v.1.4.8), the application stopped working.
What are the changes in the existing code of v1.2.26, I should not be missing, to make the application work?
There's now a guide available https://docs.angularjs.org/guide/migration - probably slightly less tedious than reading every single ChangeLog
Migration Guide - https://docs.angularjs.org/guide/migration
See the change log
https://github.com/angular/angular.js/blob/master/CHANGELOG.md
An easier way is to see where your code fails, debug a bit and hit the nail. There are no huge changes between the versions in question.
Although, your question is not a good candidate for StackOverflow questions but you should read the ChangeLog to see the breaking changes and fixes in each release after v1.2.26 to v1.5.0.
See the changes https://github.com/angular/angular.js/blob/master/CHANGELOG.md
Please take a look if this may help you:
http://www.diatomenterprises.com/migration-history-from-angularjs-1-3-to-1-5-and-then-2-0/
I can assist you in migration from 1.3/1.4 to 1.5 since did it a few times on different projects and all went smooth. Of course there're some tricks to do, but in general nothing breaking.
I was working on an incremental backup solution for my Cloudant databases.
I was using the documentation at https://docs.cloudant.com/backup-guide.html and today I tried to go back to that link to look something up and the page is gone.
Is this an error in the documentation, or has support for this been removed?
Thanks
The documentation on the page you were reading was for features that have not yet been released. Once the features are officially released, we will make that page available again. In the meantime, this page may be helpful: https://docs.cloudant.com/backup.html
We are working towards a PC based software client for our industrial control module box and we are using QooxDoo for the UI.
I wish to use the qxe package for the StatusBar widget it provides. However, there is no clear direction on how to acquire the package. The docs (Qx 2.1.1) refer to a SVN repository (https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/), which seems to be empty as of today.
We would also later like to use the contributed themes in our product.
Any help would be great.
Thanks and best regards,
Vishal Sapre
The qooxdoo-contrib SF project was upgraded recently to their Allura platform, during which the SVN repo URL changed. The updated one is:
https://svn.code.sf.net/p/qooxdoo-contrib/code/trunk/qooxdoo-contrib
The old repo has been retired, to avoid confusion (hence it's empty). The new URL is also what you get looking at the qxe homepage entry at qooxdoo.org. For contrib-specific information I suggest that you start there.
If you follow this blog post, applying the referenced patch to your qooxdoo SDK, the change should be transparent for you project. Ie. the reference to qxe via the contrib://qxe/<version>/Manifest.json pseudo URL should continue to work.
Besides the new repo URL nothing has changed in using contributions, so the correpsonding manual entry you are referring to basically applies. For offline usage, though, as the tarball downloading feature is not supported with SF's new repositories anymore, the easiest would be to let the Generator download it once (using the contrib:// entry in config.json), then locate it on your disk ('generate.py info' will list your local download path) and copy it from there.
We are in the process of migrating our bug tracking to Bugzilla from a really old version of track and I am running out of Advil.
We have a legacy application that has been around for a long time. Mix in the fact that our versioning management has been through a few iterations it generated a lot of different versions in the wild. To make matters worse, because of contractual limitations it is not always possible to upgrade the clients to the latest and greatest, so we must branch, fix, test and release, on the version they currently have, yielding yet another version number.
The end result is that the version combo box is ludicrously long. Lastly, for various reasons, we want to track three different version information :
the version in which the bug was found (version), the version in which we plan to fix (milestone) the bug and the version in which it has ultimately been fixed (open to suggestions). here is my problem in fact... this can actually be multiple numbers where we did a retroactive fix for some of these customers (this happens VERY often).
This is where I need your collective wisdom :
How do you keep track of these versions (found, planned and multiple fixed) in Bugzilla?
What are the best practices around linking versions and bug tracking ?
Answers
It seems that cloning the bug for each version is a good way to track, thus the target version is always tracked in the milestone as well as the fixed version, and the buggy version is always the native version.
Also to have each clone block the original bug make it a good way to trace the history back to the original submission.
Although I have accepted the answer I still welcome your input.
Often, if we need to fix something in multiple released versions (generally branches in the source code repository), the bug will be cloned for each branch so that all the commits and release status can be tracked separately. I think the only time we don't do this is when the change is not directly related to the codebase itself and cannot be fixed simply by updating our libraries.
As for version tracking in general, this has struck me as a reasonable way to do things, given that we generally only need to support 2-3 major versions (plus the trunk) at any time. If you have multiple disjoint versions that need supporting, e.g. customer-specific deployments, then things are going to be harder to track. (Arguably this is going to cause headaches in general and it would be better to unify things to a more central version theme).
I use Bugzilla to keep track not only of bugs, but also of new features, enhancements, and vague ideas. For each planned and released version, I have a Tracking Bug (something that I saw on the original Mozilla bugzilla, and found to be useful).
So if you have a bug report, you enter the bug with the version number that it was reported. Create additional bugs (one for each version you plan to fix it in) which all depend on (block) the original bug and block the version-specific Tracking Bugs.
If all bugs blocking the original bug are closed/verified (whatever your QA implements), you can also close the original bug.
I was looking for a similar feature in TFS, and while doing some investigation, I found that there is an enhancement request to manage "sightings" in Bugzilla:
"Bug 55970 - (bz-branch) Bugzilla needs to deal better with branches (implement sightings)":
https://bugzilla.mozilla.org/show_bug.cgi?id=55970
There is also a proposed design:
https://bug55970.bugzilla.mozilla.org/attachment.cgi?id=546912
For information, we are going to implement something similar in TFS 2010, with a "Bug Parent" or "Bug Master" to hold the information about the bug itself (repro steps, severity, technical info, impacted components...), that can have child of type "Bug Child" or "Sighting" that will hold the information specific to a given branch (target milestone, priority, specific information for that branch...).
We are using jira and still have this problem. I think it is a question of requirements and how are versions used rather than any one tool.
Who uses versions and how do they use them?
How are versions related to milestones in a project plan?
We use a 4 dectet version (major.minor.patch.buildNO). buildNo is the SVN head revision # at time of build. Each version is stored in JIRA and issues have an affects version and fixed-in version field that's a multi select.
After a short while we have many versions. Jira does allow us to control the list in two ways
1. Archive versions (greyed out from pick list)
2. Merge versions (rolls several versions together into a new version - no undo)
We have used Archive, but have avoided Merge due to the lack of the undo. So we still have a list of many many versions.
I'm sure you could probably accomplish a merge action in Bugzilla with some scripting and time, the question is: when is it OK to merge several older versions together?
If I have released, do I need to know that I have 17 builds between start and release? Do I need to keep the knowledge of a bug being found in build 1, fixed in 2, found again in 7, fixed again 9? Or is Found in release 1.0.0 fixed in release 1.0.1 good enough?
i'm going to ask a large question on this topic later on today, but I know the basic answer already:
- Depends on how your team wants to track things.
Implementation is fun, but it all comes down to requirements, goals and working back from user experience to solution. Which is rough when people don't necessarily know how that want to use something that doesn't quite exist in the form they'd like to use.
I have created a custom field (string) to list to version(s) (as V.M.P.B) where a bug has been fixed.
I have created also another custom field (string) to list to version(s) affected by a bug.
Doing that you are able to perform quick-search on specific version.