Proposal to combine issue trackers

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Proposal to combine issue trackers

Mark S White
Hello community members,

We are currently evaluating a proposal to merge the issue trackers
in the open-esb and open-jbi-components projects into one. Frequently
in the past, issues have been filed in the wrong issue tracker, causing
some delay in getting those issues addressed. If we consolidate into one
issue tracker this will simplify things for everyone - developers, users,
and the QA teams.

Going forward we would like to use the open-esb issue tracker for all
issues with both the JBI runtime and the components. Existing issues in
the open-jbi-components issue tracker would not be moved, but all new
issues would be filed in the open-esb issue tracker. In order to make this
happen, all of the components and sub-components currently defined in
the open-jbi-components issue tracker will need to be defined in the
open-esb issue tracker. Once that has been completed, the switch can
be made.

If there are components/sub-components that should not be there, or that
need to be added, please let us know.

We welcome feedback on this proposal. We would like to make the change
effective September 8 if there are no strong objections.

Thanks!


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Proposal to combine issue trackers

Louis Polycarpou
Mark,

Will this / can this also be extended to include components such as RSS BC / XMPP BC which, being subprojects, currently have their own trackers?

Thanks,
Louis

Mark S White wrote:
Hello community members,

We are currently evaluating a proposal to merge the issue trackers
in the open-esb and open-jbi-components projects into one. Frequently
in the past, issues have been filed in the wrong issue tracker, causing
some delay in getting those issues addressed. If we consolidate into one
issue tracker this will simplify things for everyone - developers, users,
and the QA teams.

Going forward we would like to use the open-esb issue tracker for all
issues with both the JBI runtime and the components. Existing issues in
the open-jbi-components issue tracker would not be moved, but all new
issues would be filed in the open-esb issue tracker. In order to make this
happen, all of the components and sub-components currently defined in
the open-jbi-components issue tracker will need to be defined in the
open-esb issue tracker. Once that has been completed, the switch can
be made.

If there are components/sub-components that should not be there, or that
need to be added, please let us know.

We welcome feedback on this proposal. We would like to make the change
effective September 8 if there are no strong objections.

Thanks!


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



--
Louis Polycarpou
Sun Microsystems SOA/BI FAST
Email: [hidden email]
Skype: <a href="skype:lpolycarpou">lpolycarpou
My blog Project Open ESB
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Proposal to combine issue trackers

Frank Kieviet
Administrator
In reply to this post by Mark S White
See https://open-esb.dev.java.net/IssueTracker.html . We would have two
trackers, one for the runtime and its components, and one for the design
time.


> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Mark S
> White
> Sent: Tuesday, September 02, 2008 17:09
> To: [hidden email]; [hidden email]; dev@open-jbi-
> components.dev.java.net; [hidden email]
> Subject: Proposal to combine issue trackers
>
> Hello community members,
>
> We are currently evaluating a proposal to merge the issue trackers
> in the open-esb and open-jbi-components projects into one. Frequently
> in the past, issues have been filed in the wrong issue tracker, causing
> some delay in getting those issues addressed. If we consolidate into one
> issue tracker this will simplify things for everyone - developers, users,
> and the QA teams.
>
> Going forward we would like to use the open-esb issue tracker for all
> issues with both the JBI runtime and the components. Existing issues in
> the open-jbi-components issue tracker would not be moved, but all new
> issues would be filed in the open-esb issue tracker. In order to make this
> happen, all of the components and sub-components currently defined in
> the open-jbi-components issue tracker will need to be defined in the
> open-esb issue tracker. Once that has been completed, the switch can
> be made.
>
> If there are components/sub-components that should not be there, or that
> need to be added, please let us know.
>
> We welcome feedback on this proposal. We would like to make the change
> effective September 8 if there are no strong objections.
>
> Thanks!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Proposal to combine issue trackers

Mark S White-2
In reply to this post by Louis Polycarpou
There were already sub-components in the open-jbi-components issue tracker for both of those, and all the
others as well, so I defined them in the open-esb issue tracker too.

Louis Polycarpou wrote:
Mark,

Will this / can this also be extended to include components such as RSS BC / XMPP BC which, being subprojects, currently have their own trackers?

Thanks,
Louis

Mark S White wrote:
Hello community members,

We are currently evaluating a proposal to merge the issue trackers
in the open-esb and open-jbi-components projects into one. Frequently
in the past, issues have been filed in the wrong issue tracker, causing
some delay in getting those issues addressed. If we consolidate into one
issue tracker this will simplify things for everyone - developers, users,
and the QA teams.

Going forward we would like to use the open-esb issue tracker for all
issues with both the JBI runtime and the components. Existing issues in
the open-jbi-components issue tracker would not be moved, but all new
issues would be filed in the open-esb issue tracker. In order to make this
happen, all of the components and sub-components currently defined in
the open-jbi-components issue tracker will need to be defined in the
open-esb issue tracker. Once that has been completed, the switch can
be made.

If there are components/sub-components that should not be there, or that
need to be added, please let us know.

We welcome feedback on this proposal. We would like to make the change
effective September 8 if there are no strong objections.

Thanks!


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



--
Louis Polycarpou
Sun Microsystems SOA/BI FAST
Email: [hidden email]
Skype: <a moz-do-not-send="true" href="skype:lpolycarpou">lpolycarpou
My blog Project Open ESB
  

-- 
Open ESB Community (http://open-esb.org)
Check out my blog (http://blogs.sun.com/mwhite)
--------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email]
Loading...