Create kdevelop3 product?

Andreas Pakulat apaku at gmx.de
Sat Jan 24 22:04:25 UTC 2009


On 24.01.09 13:32:25, Matt Rogers wrote:
> 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.

Hmm, ok. We should make sure that there are no open bugs in the components
we remove. If there are we should check wether they're still valid and if
so move them to the right place.
 
> ok, I'll tackle this over the next week or so.

Let me know if you need help.

Andreas

-- 
You'll be called to a post requiring ability in handling groups of people.




More information about the KDevelop-devel mailing list