Hi all,

I finally copied all Bugs and Feature Requests from Sourceforge to our
new Bugzilla.

What we now need to do is consolidate these bugs. See if there are
duplicates or things we don't want to do at all. I think David, Stephane
or Boris should do this. Also it would be great if you guys could set a)
a target milestone for each bug, and b) the priority.

Pavol Rusnak:
> How about splitting CenterIM product into two: CenterIM4 and CenterIM5
> products? (For example Protocols components will be totally unrelated -
> as 4 uses internal and 5 will use libpurple, probably the same for Core
> component).
This is possible w/o problems. But I think we still have
protocol-issues. At least rss is not supported by libpurple, so we will
probably have our own implementation there. In addition to that we will
get bug reports about protocol issues. It's our job then to direct these
bugs upstream and maybe even fix them. So having "Protocols" as
component is still valid for CIM5. That's why I didn't split the products.

TigerP!:
> I don't know everything of bugzilla, but will it then also be possible
> to 'specify' (or move or whatever) that a bug will be solved in
> centerim5?
That's done via Target Milestones. These are product-wide specified. But
it would be no problem to have a target ms 5.0.0 for botch products
"CenterIM4" and "CenterIM5".

So far
-Sascha-

PS: If anyone thinks I should have done sth different, please say so and
we can discuss these things!
PPS: I added a Changelog-Update as blocker for 4.23.0 (assigned to me) -
If anyone has another blocker for 4.23.0 please add it asap. Otherwise I
think we could release after the Changelog is updated (OTR remains
disabled by default and is delayed to 4.24.0).
Maybe the "Release" could also be 4.22.2 and OTR delayed to 4.23.0 -
that would depend on our versioning policy. Discussion about that is
welcome!

-- 
_______________________________________________
Centerim-devel mailing list
[email protected]
http://centerim.org/mailman/listinfo/centerim-devel
http://www.centerim.org/

Reply via email to