Branching + release management of KDevelop 4.5 - FEATURE FREEZE!

[Morten Volden]

2013/1/12 Morten Volden <mvolden2 at gmail.com>

> 2013/1/12 Milian Wolff <mail at milianw.de>
>
>> On Saturday 12 January 2013 21:48:51 Milian Wolff wrote:
>> > On Saturday 12 January 2013 20:52:02 Morten Volden wrote:
>> > > 2013/1/12 Milian Wolff <mail at milianw.de>
>> > >
>> > > > On Friday 11 January 2013 20:30:16 Morten Volden wrote:
>> > > > > fredag den 11. januar 2013 skrev Milian Wolff :
>> > > > > > On Friday 11 January 2013 17:48:55 Milian Wolff wrote:
>> > > > > > > On Tuesday 18 December 2012 20:43:03 Milian Wolff wrote:
>> > > > > > > > Hey all,
>> > > > > > > >
>> > > > > > > > I think we should branch off 4.5 and emplace a soft feature
>> > > > > > > > freeze
>> > > >
>> > > > -
>> > > >
>> > > > > > > > anyone
>> > > > > > > > against that?
>> > > > > > >
>> > > > > > > I'll now start creating 4.5 branches. The 4.5 branches are
>> then
>> > > > > >
>> > > > > > considered
>> > > > > >
>> > > > > > > feature frozen!
>> > > > > >
>> > > > > > Done now. Any quasi-maintained plugins that I missed?
>> > > > >
>> > > > > Hi milian
>> > > > >
>> > > > > How about the Perforce-plugin? I have added you as a project
>> manager.
>> > > >
>> > > > Is it stable, do you want to take maintainership? Do want it to be
>> > > > released?
>> > > > If so, it should move to kdereview and then merged into
>> KDevplatform.
>> > > >
>> > > > Me and and about 10 other guys use it regularly at work - so I
>> believe
>> > > > it
>> > >
>> > > is stable.
>> > >
>> > > At my own (relatively) slow pace- Yes, I am committed to fix problems
>> and
>> > > feature requests :-)
>> > >
>> > > Yes, I would like it to be released. I just never got round to do it
>> > > because I have no idea what is needed to do so.
>> > >
>> > > Would it be OK to release it separately first, and then move it into
>> > > KDevplatform at a later stage?
>> >
>> > Yes, but you'll have to go through KDE review first no matter what.
>>
>> BTW could it be that your unit test is failling?
>>
>> FAIL!  : PerforcePluginTest::testAdd() 'j->exec()' returned FALSE. ()
>>    Loc: [/home/milian/projects/kde4/kdev-
>> perforce/test/perforceplugintest.cpp(136)]
>>
>> Generally, doesn't look like you got many tests (which is bad).
>>
>> I know (and you are right)
>
> I'll see if I can do something about that tomorrow, and start up a review
> process also.
>
> Just to let you know, I'm still working on this....(Whenever I can find
the time to do it.... :-) )

I think the best way to go here is to create a stub executable of the p4
client and call that during test. There is no sense in writing a unittetst
that can only be performed on my machine.

Cheers

/Morten


> Cheers
>
> /Morten
>
>
>
>> Cheers
>> --
>> Milian Wolff
>> mail at milianw.de
>> http://milianw.de
>>
>
>
>
> --
> - When the split is pulled, mr. Grenade is no longer our friend
>



-- 
- When the split is pulled, mr. Grenade is no longer our friend
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20130123/9d19778c/attachment.html>