Create kdevelop3 product?

[Matt Rogers]

On Saturday 24 January 2009 04:57:31 Andreas Pakulat wrote:
> On 23.01.09 20:40:43, Matt Rogers wrote:
> > On Friday 23 January 2009 19:12:52 Andreas Pakulat wrote:
> > > Hi,
> > >
> > > to cleanup the mess in the kdevelop product I thought it could help to
> > > move all stuff that doesn't exist in kdevelop4 into a new product
> > > "kdevelop3". I'm currently already closing unmaintained stuff, but the
> > > component list is still pretty long.
> > >
> > > What do you think?
> >
> > Which components need to be closed?
>
> What implications does "close" have?
>
> > I don't see how making a kdevelop3 product really solves any of this. I'd
> > rather just close the unnecessary components.
>
> See above, what happens with the reports? We could of course move all of
> them to a "kdevelop3.x unmaintained" component.
>

that's what I would do, since you can only remove them, you can't hide them.

> From a quick look the components that should probably be closed now:
> all build tools
> all editors
> bookmarks part
> qeditor
> doctreeview
> kdevelop2.x
> UI:all modes
> UI:childframe
> UI:IDEAL
> UI:tabbed
> UI:toplevel
>

ok, I'll tackle this over the next week or so.

> Basically thats the stuff that doesn't make sense for kdev3 or kdev4 and
> (AFAIK) none of them has any open bugs.
>
> When we release KDevelop4 I'd like to think again about closing all
> KDevelop3-only components (i.e. partexplorer, distpart,
> clearcase/perforce etc). Reason: Don't make users think anything in
> these components gets ever fixed. I'm assuming here that we can re-open
> the component later on.
>
> Andreas

-- 
Matt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090124/89767999/attachment.sig>