Scott Lawrence wrote:
> > We now have a couple more new tools available: Crucible and FishEye;
> > they are integrated and both at the same host:
> >
> > http://code.sipfoundry.org/
Damian Krzeminski asked:
> Do we want to try to use crucible as a basic way of sending patches.
> Instead of attaching them in JIRA?
There are a number of very cool looking features that do more powerful
integration of Crucible/FishEye with Jira, including opening new
Crucible reviews directly from the Jira issue. Those features have not
yet been enabled because they are harder to set up correctly with
multiple Jira projects.
This will be fixed shortly: we will be merging the sipXconfig and
sipXecs projects in the tracker so that we can start using the
integration (and incidentally, it will make it easier to get some
reports and filters that display the full status of the project).
The merger will renumber all the issues: they will all become 'XX-nnnn',
but Jira remembers the old numbers, so they will redirect to the correct
issue - old links will continue to work.
To help preserve the ability to look at different parts of the project
(and the teams that work on them), a new field has been added to all
issues: the Area field is a multi-checkbox field (so that issues can be
in more than one area, but this is expected to be rare) that has 4
values:
* Management
The management application and interfaces - essentially
the former sipXconfig project
* Operation
The rest of the code that runs in the product - all the
non-sipXconfig services - essentially the existing
sipXecs project.
* Documentation
The production of documentation.
* Testing
System test development and execution activities.
Existing issues will get this field set (hopefully mostly correctly) in
the process of moving (not until after the 'retirement' of old issues
announced earlier [1], because setting this field would Update the
issues and so nothing would be eligible for retirement).
The new sipXecs project has been created, but is closed (permissions set
so that nothing can be done with it yet). My plan is to move all issues
from the existing projects to the new merged one beginning some time
Friday afternoon or Saturday morning (EDT), and then close the existing
projects (which will then be empty anyway). The tracker will
essentially be unavailable during the move, but I expect it to only take
a couple of hours at most.
[1] http://list.sipfoundry.org/archive/sipx-dev/msg17522.html
and http://list.sipfoundry.org/archive/sipx-dev/msg17529.html
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
