Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
My team and I need to work on a project whose bugs are filed in Bugzilla, using Mylyn.
Do you know of any tool or plug-in that provides scrum-inspired burndown charts to Bugzilla or Mylyn?
Hopefully, this tool would be free for commercial usage, but we're not closed to commercial tools.
Update: 4 hours of research allowed me to find very few free tools. Looks like bugzilla isn't popular in agile teams! And obviously, it's not the best fit.
The Songbird project made a really good job of documenting how they customized their Bugzilla instance and developed tools to automatically generate daily reports, including burndown charts. They released their set of tools as ruby open-source code under the MIT license. Very interesting stuff, especially since it comes from a high-profile, important community project.
There's Scrum Vision:
free
open source in very active development
for mylyn
publishes burndown chart to a Google Spreadsheet
We think of this as the last resort option, because of the charts being generated offsite.
There's also TargetProcess:
commercial
free for up to 5 persons, self-hosted (need a Windows server)
integrates with Bugzilla and JIRA:
Bugzilla synchronization is automatic, one-way (read-only)
JIRA synchronization is automatic, two-way
Subversion, Selenium, and more
And there's VersionOne:
supposedly the most used commercial tool
integrates with Bugzilla, JIRA, Subversion, Fitnesse and more
There's also a really nice features list (PDF).
There's also Yoxel:
commercial open-source
integrates with Bugzilla and others
not sure if burndown charts are part of the free open-source offering
UI and UX made it really hard to find burndown charts. Or maybe because the demo data wasn't setup to make them work, because I've definitely seen line charts, just no burndown-looking one.
It wasn't easy to find out that ScrumWorks Pro features burndown charts, but on second look, it does:
commercial
price undisclosed (contact the company for a quote!)
Pro integrates with Bugzilla and JIRA
synchronization is manual: import or update-from-reimport
synchronization is one-way: bugs/issues are read-only in the software
I also found Rally Enterprise Edition.
commercial
EE integrates with:
Bugzilla and JIRA:
Bugzilla synchronization is automatic, two-way
JIRA synchronization is manual, two-way
Mylyn & TaskTop
Subversion, Fitnesse, Hudson, Ant, and much more
Free for commercial use
Online
Simple
Have a look:
http://www.burndown-charts.com/teams/dreamteam/sprints/prototype-x
Oh they also support teams in different time zones and openID.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Im trying to find some information about the Cognos analytics but without success.
Im trying to find out what is the latest version of Cognos 11 that is availible and When it was the version released?
How much updates this release have already?
How much bugs were discovered?
Does the upgrade from Cognos 10 to 11 is smooth?
Thanks alot
While the question appears a bit broad, I will try to answer the parts of the question I can understand and, hopefully, it will assist the OP.
These are the approximate release dates for the Cognos Analytics 11 that have been released as of the time of this post:
11.0.0: December 23, 2015
11.0.1: March 29, 2016
11.0.2: May 6, 2016
Interestingly, while the 11.0.1 and 11.0.2 releases are seeming to include fixes only, IBM does not appear to be using Fix Packs in the same way as prior releases of Cognos BI. These are full releases that install and upgrade in the same way as if you were upgrading from BI 10.2.1 to 10.2.2 . There have been at least two interim fixes (IF) released as well, one for 11.0.0 and one for 11.0.2, both related to security, if I recall correctly.
While I don't think there is any official statistic on how many bugs were discovered, fix lists can be found for the released versions here:
11.0.0
11.0.1
11.0.2
The upgrade process from Cognos 10 to 11 is smooth in the sense that the overall process is similar to upgrades in past releases. There are some architectural changes for multi-node environments that change the process for installing subsequent nodes. That said, there are some very important deprecations and feature changes/removals that you will want to learn about, not to mention the new navigation, authoring, and content consumption interfaces.
There are a lot of facets to the release that need considering for any production upgrade -- I would definitely jump into the documentation and, assuming you are a current customer, set up a sandbox to start testing functionality before I made any hard plans for moving a production system forward. If you want more very high level feature discussion, a quick Google search for "Cognos 11 new features" or similar will give you a lot of helpful information.
To follow the announcements on the latest releases, you can subscribe to the IBM Analytics blog:
https://www.ibm.com/communities/analytics/cognos-analytics/blog/
or periodically check the product page:
https://www.ibm.com/analytics/us/en/technology/products/cognos-analytics/
For bug fixes, you should refer to the product release notes:
http://www-01.ibm.com/support/docview.wss?uid=swg27047187
, though the list of bugs seem to be less granular than what you would normally see from other IBM products. The list of bugs does not seem to be broken down by fix pack either.
I do not think the upgrade is a smooth one, since it is not an in-place upgrade like you would have from, let's say, 11.0.1 to 11.0.6. I also could not find a clear statement about the upgrade from 10.x in the installation guide, so it is unclear (for me, as of now) whether the process entails the usual backup of the content manager database from original version and restore the backup image to a new database to be used by the new version
I tried exporting the contents from the 10.x installation via Cognos Admin console and then importing it into the 11.0x release, but 3 out of 5 of my reports simply hang on launch even after performing a report upgrade operation via Admin console.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
At our company we've built a data integration tool that we have sold to several customers. Most of the customers have distinct requirements. We implemented these customer-specific extensions by using a self-made mechanism based on inheritance (so every installation knows which classes to load and which not). But all this customer-specific code is still in the same codebase as the standard code.
Now, this is no longer possible for several reasons (codebase getting ugly and large, clashing requirements, etc.)
For this reason we have decided to separate the codebases: one for the standard product, and several customer-specific codebases.
I am now trying to find a version control system that supports this approach. Here's my wishlist:
support for several "standard" codebases for different releases
1.0 release
1.1 release
2.0 beta/development
support for multiple "customer" codebases
ability to create a customer codebase by cloning a standard codebase
ability to change standard code in a customer codebase
ability to update a customer codebase with a new standard release (and somehow marking the conflicts that come from changed standard code in the customer codebase)
As our team is still very small (~4 programmers), it should also be easy to handle by the developers themselves.
Btw, our software is built using Spring with STS (so, an Eclipse plugin would be great too).
All VCS that I have researched so far seem to have that target of building one piece of software - not several. I am hoping for some suggestions or best-practice approches.
Simply
Simply get git, go for pull request process and take advantage of some GUI, supporting this workflow.
Are releases much different form custom development?
To clarify, what is the situation you are facing: "standard" development comes in versions, they might live independent for maintenance, you may need to get some fixes from new versions to be incorporated in older releases, you need a way to solve hotfixes.
All these things are well solved by distributed version control systems like git, hg or others. I have started with hg, but later found, git is used more often and in standard installation offers all what is need (what is not a case for some hg features).
Regarding custom development - in fact, they do not differ conceptually much from standard versions - you just need another modification of your program being identified under unique name, which will eventually denote, these are custom things.
Branching or pull request process?
Now how to approach different "swim-lines" for different versions and custom developments?
Branching workflow models
Obvious answer is "branching". There is a lot of tutorials on various branching models and they shall be solving your problem.
However, branching is not trivial either and you may find long disputes on what style is the best one.
Topical repos and pull request workflow
Fortunately, there are even simpler solutions - Pieter Hintjens article http://hintjens.com/blog:24 about "Branching considered harmful" provides simpler model, using topical repositories and pull request process. This is how many projects on GitHub and BitBucket are managed and I found this really the most effective solution with minimal risks.
Final recommendations
For pull request working process, it is handy to have some GUI, which supports related communication - and apart form GitHub and BitBucket, there are solutions on the market (incl. some open source solutions).
Prepare yourself for long run - starting with linked article by Pieter Hintjens may make your run a bit shorter, next step could be playing with a project on BitBucket or so, then design "the final" system (which will anyway evolve during time, but git repos are well suited to keep with the changes).
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
What is the "Jazz Project" or Jazz based projects?
what is the role of Eclipse in Jazz based projects?
Its is a conceptual question.
I heard them in software engineering Podcast. but Don't Know much about them. So detailed reply will be appreciated.
(Note: I was a member of the team who built Jazz. I no longer work on the Jazz team but still work for IBM.)
Jazz is a family of technologies created by IBM's Rational division to enable software team tools and activities like software configuration management (SCM), bug and enhancement tracking, build automation, release and iteration planning, requirement management, test management, amongst other things.
Jazz was started in late 2004 by the Rational group because we realized that we needed a new technological foundation to help teams deal with modern challenges like geographically dispersed teams and governance and compliance issues.
There are several relationships to Eclipse. First of all, the original Jazz team was staffed with many of the same IBM folks who created Eclipse, e.g. John Wiegand, Erich Gamma, Jim des Rivieres, Nick Edgar, and Jean-Michel Lemieux, among others. Also, Eclipse technology played a bit role in the early days of Jazz. The first client technology we created was some new team extensions to the Eclipse IDE (this evolved into the Rational Team Concert Eclipse client). We also engineered the original server using Eclipse Equinox (the Eclipse implementation of OSGi) so that you could use the OSGi extensibility model to contribute server-side resources like web service endpoints, data model definitions, and web UI code.
Over time, we realized that extensibility via shared runtime wasn't going to work so we shifted over to a distributed extensibility model based on RESTful HTTP and RDF. We started an open community to define RESTful data models for team resources called "Open Services for Lifecycle Collaboration" (http://open-services.net/).
Finally, there has even been some influence of Jazz on Eclipse. When I started the Jazz Web UI code, at first I envisioned an extensible web UI much like the Eclipse UI (views, editors, etc.) but quickly pulled back on those ambitions when I realized how much work that would be to do the right way. However, over the years I collaborated with the IBM Eclipse folks talking about how we could achieve component reuse between browser and rich clients (Eclipse IDE, Visual Studio) and we also talked about how nice it would be if there could be a first-class browser story for Eclipse. After an extremely circuitous path, Eclipse.org with IBM's support proposed a new project called Orion (http://www.eclipse.org/orion/) which intends to provide this browser story for Eclipse.
So yes, quite a few relationships between Eclipse and Jazz. :-)
It's a suite of collaboration tools, which are based in a previous research sponsored by IBM.
You can browse the details (and some history) here:
Original project: http://domino.watson.ibm.com/cambridge/research.nsf/99751d8eb5a20c1f852568db004efc90/605fd62cb9a5a54485256e200066adf6!OpenDocument
Products: http://jazz.net/about/about-jazz-products.jsp
I heard about this Jazz Process:
http://www.jazzprocess.com/concept/
there's also a book
http://www.amazon.co.uk/Jazz-Process-Collaboration-Innovation-Agility
it seems interesting
What is the "Jazz Project" or Jazz
based projects?
I think It's a framework for component-based server-side applications, focussing on collaborative software development tools. It's hard to make out through the veil of buzzwords.
what is the role of Eclipse in Jazz based projects?
Presumably a lot of them are developed using Eclipse. You may also have heard them used together because Jazz is envisioned as a kind of "server-side Eclipse", i.e. a platform that aids development and integration of development tools.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
We use Trac as our bug tracking / development / wiki system and I was wondering if anyone has experience and uses some of the Trac Agile/Scrum plugins or functionalities? Anything you'd recommend?
Or would it be better to duplicate Trac tickets as dead-tree user story index cards and a hand-drawn burndown chart?
Note that I found a similar question here. Though it's specifically about Scrum. They recommend Agilo. Has anyone tried Agilo yet?
With a collocated team, I'd always duplicate user stories on index cards. A wall of cards is much more collaborative and simple to use than any software tool. And what's most important, it's in your face.
The same is true for a burn chart. In my experience, a software chart gets online looked at by a small number of people, and typically is a pull medium. A big, handdrawn poster (that changes regularly) gets noticed by everyone, and serves as an incubator for ad hoc discussions.
It's also quite valueable to be able to point at them during your daily scrum meeting.
This is how we use Trac for our scrum like sprints:
We use the milestones in Trac to identify sprints.
There is a default Backlog milestone where we gather all new tickets.
Before each sprint we move tickets from the backlog the current release.
On the milestone page, we can add retrospectives and other info about the sprint using wiki syntax.
So just the default Trac functionality without any plugins for now to keep it lightweight. As we get better we may add features like burndown charts or maybe switch to another tool, but we want to get the proces in place first.
Answering late, but this more of sharing my experience with Trac+Agilo so far.
To quickly answer your question, perhaps Agilo is the best option available for Agile development with Trac.
Now comes to install and usining install was just very easy. We used their latest release 0.7.3.3. It installs flawless on Trac 0.11 and Python 2.5. Don't forget to install libjpeg and python imaging library. It would be useful to note that we used virtualenv which took a made things easier.
Further usage is very simple. For wiki I kind of prefer Trac's old clean look over Agilo's customization. Other than that all things just works.
On thier mailing list I have noticed that they are planning to offer multi-project support in future. In all I recommend Agilo plugin for Trac.
Yep, I installed Agilo on our Trac installation.
Seems very cool, includes nice burndown charts.
Unfortunately I left the company where I installed it before I could get any serious usage out of it.
Installation was a pain (Ubuntu Ibex) - I documented precise steps on the Agilo Google Group.
The problem (as always) is integration into the business end of things that PMs and CEOs like to see (e.g. estimated vs actual hours). There are (as has been mentioned) other products out there that cover this off (FogBugz covers this off I believe), but I (and the team) love Trac so we worked around this.
Oh, one more thing; it looks like it introduces quite a lot of overhead (i.e. you have to spend more time in trac to get the most out of it), but like I say I didn't have an opportunity to really use it in anger.
We used Trac before with a burndown plugin then went to Redmine. We've found Redmine to be miserable for repository viewing and the issue interface. We're actually looking to move back to Trac again.
Bitten is a Trac plugin for continuous integration that can be harnessed to do automatic builds on check-in, which provides a critical part of the Agile process (rapid feedback). I haven't used any other plugins for Trac personally, so I can't comment on them. However, the native Trac functionality of milestones could be leveraged fairly easily, I suspect, to be used as iteration markers (where each milestone represents the end of an iteration). Since milestones can be used to mark a 'due date' for features already, you shouldn't need much in the way of modification to use them as such.
From there, using tickets as user stories, and tying them to milestones (I'm sure this can be done manually at worst) would give you a basic method of tracking velocity and keeping the team aware of progress (and changes that need to be made as well).
We use the Trac wiki for:
List of requirements for each feature
List of technical specs (if any) for the features
List of Releases and their features
Deployed environments, with links to all instances
There's a macro for making web requests, so we can list which version, etc. each env have
(there's a GraphViz plugin which is quite helpful for simple drawings)
There's also a ticket in the ticketing system for each "feature", for keeping a gross backlog and the current/next sprint planned.
Then we write a bunch of cards during sprint planning for each feature.
There's also a more operational side to things. We keep one person each sprint on Ops, so we have one person who's dedicated to be interrupted by people outside the team. The rest of the team can focus on delivering features.
Each bug/ops task gets a ticket, but as soon as we start working on it, it gets a card and starts moving across the board. That way it gets visibility and we don't forget to involve the testers, etc.
Scrum is pretty tactile, so I don't think it would work great to put too much stuff outside of the physical working environment. But in the end your team needs to find a balance that works.
For something completely different, the best way to do Agile Development with Trac may be to simply migrate everything to Redmine. It supports Trac's core features with some extras including multiple projects, Gantt charts, forums, DCVS, etc. though it looks like it's not completely there yet. Some good things in the pipeline.
Daniel Srb (in the comments) has a redmind agile plugin he's been working on that looks promising. You may be able to contact and see if he's planning to release it (was a long time ago).
We've had success using two products in concert in the past, Trac for tickets, xplanner for planning.
Agilo for Scrum rocks, the latest versions are using client side generated charts, so there is no dependency anymore, much easier to install :-) agile42 just release a Pro version that enriches the Agilo experience with a nice and intuitive Planning Board, very cool screencast :-)
We recently started using Scrumban.
Basically a Kanban board, with the daily stand-up meetings covering the classic Agile Scrum questions - what did you work on the previous day? what do you plan to work on today? do you have any blockers?
We do this around a physical Kanban board, it is great for visualizing the work flow and for team synergy, but we also wanted a digital form of our Kanban board to be able to double check trac usage vs. the physical board.
In search for something that would work, I found this clever post on re-creating a digital version of the Kanban board in trac.
It is very straight forward and simple, I was able to easily manipulate this approach for our work flow, and you could probably tailor it to your Agile Scrum iterative approach (or if your able to ditch the time boxed approach, give Scrumban a try).
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
While using Aptana and Eclipse for the first time in my programming life for PHP projects, I am wondering how these projects get funded. There is a lot of activity in the Eclipse community and the IDE itself is very good. I came across various Eclipse IDE sites and I am not able to decide which one is the official site of the Eclipse project. There is also news that the community is also working on dynamic language integration and one Aptana product is already out there.
How the full-time and part-time programmers get funded in these projects? I came to know that Aptana has withdrawn it's PHP support. Will Eclipse continue supporting PHP?
From the Eclipse "About" page:
The Eclipse Foundation is funded by
annual dues from our members and
governed by a Board of Directors.
Strategic Developers and Strategic
Consumers hold seats on this Board, as
do representatives elected by Add-in
Providers and Open Source committers.
The Foundation employs a full-time
professional staff to provide services
to the community but does not employ
the open source developers, called
committers, which actually work on the
Eclipse projects. Eclipse committers
are typically employed by
organizations or are independent
developers that volunteer their time
to work on an open source project.
Support for various languages in Eclipse is through Plugins. There are a number of plugins to provide PHP coding support.
Aptana on the other hand is a for profit company spun out of the Eclipse code base. I believe their current business model is selling hosting and support. They used to sell a "pro" edition of the editor, but I can't seem to find that anymore.
The homepage of the eclipse project is http://www.eclipse.org.
As to the funding: some programmers are paid (for example by IBM which originally started the eclipse project, or companies that use Eclipse as part of their own product or strategy), and as with almost all open-source projects a lot of programmers really just work in their free time on a part.
Eclipse consists of a rather small core, and a lot of plugins, which are all developed by different individuals.
Open source projects get funded because the companies and individuals involved believe that it is in their best interests. For some, it is a matter of building reputation so that they can sell services in other contexts. Some companies fund the Eclipse Foundation in exchange for goodwill, business opportunities, advertising, and whatnot.
Pragmatically, creating and running an open source project is a good way of bring like-minded individuals together to share a development burden. Much of what is created at Eclipse, for example, is infrastructure and frameworks upon which applications can be be built. If you think about it, most of the software we use contains tonnes of functionality that you only really care about if it isn't there. You probably don't use Eclipse because of the fantastic component model (OSGi referenced implementation), or the ability to stack views, manage editors, workbench, etc. However, if all those things weren't there, you probably wouldn't use Eclipse. In general, it's probably the case that upwards of 80% of the functionality in any given application just isn't all that interesting unless it's not there. Some 80% of functionality is "plumbing". So instead of having a dozen separate organizations each spend time and money building infrastructure/plumbing that the end user only cares about if it isn't there, these companies come together in open source to work together on those shared bits of infrastructure that they ultimately use to compete against each other in the marketplace. They do it in open source so as to invite additional like-minded organizations to participate.
Other organizations get involved with open source to help develop a market. If you think of all the millions of people who just use Eclipse. If some small number of them choose to buy a useful plug-in or two, that can turn into a good business.
Some organizations bet their business on the technology. Eclipse RCP, for example, is used by--literally--hundreds of organizations to deliver applications. If an organization depends so much on a technology, it makes sense to invest time, energy, and money in it to make sure that it continues to exist and grow.
Here's an article that I found interesting:
http://news.cnet.com/8301-13505_3-10387512-16.html?tag=mncol;title
There are other reasons, but these are some of my favourite.
Often projects like this are simply people with an interest giving their own time, sweat and tears to produce great software.
Some bigger ones (Mozilla Foundation) form non-profit organisations and may get donations. Mozilla gets millions of $s through their referral to Google in their search bar - every search from that to google counts for cash.
Very occasionally it's in a company's benefit to produce something open source and even pay their workers to work on it. Take Google Chrome for example. It makes sense for Google to make their browser, and indeed pay their employees for it. But to keep people trusting them, and to allow for other developers to play and add to it, they've released the source code in the Chromium project, and anyone can download, compile and use that.
In regards to Aptana - that's a company, and they write open source free plugins to Eclipse etc so that people can write for and use their products. It makes sense for them to contribute as they'll get something back. I can't see any reference to them pulling their support though, but you may well have better sources.
Hope that helps!
They outsource everything to offshore cubicles.