Movingranges branch

Milian Wolff mail at milianw.de
Thu Aug 5 10:46:10 UTC 2010


On Thursday, 5. August 2010 12:14:56 David Nolden wrote:
> Hi, I'm using the movingranges branche routinely now, and it works
> very good. I haven't seen a crash for a long time, and also most bugs
> seem to be sorted out.
> 
> I think now would be the right time to merge the branch into the main
> devel branch. Then we should stabilize it, and do a release within the
> next months, so we have something that runs nicely with KDE 4.5. We
> don't need to include the SOC branches at that point in the release if
> they're not ready.

I think I'll try it out myself again and see whether I spot any new issues. 
But since you fixed all my previous issues, I think it would be a good thing 
indeed.

I'd personally say: Lets all try it out and see whether we spot any new 
issues. If not, lets merge it (in one or two weeks?), let it stabilize for a 
week and do a first alpha release of KDevelop 4.1. Lets say at the start of 
September?

Regarding GSOC branches: My multilang stuff is getting ready as well, in one or 
two weeks latest I'd hope for a review, esp. from you. Afterwards I think it 
could also be merged, since it should not affect the stable language plugins 
that are released. Otoh this would probably also count as a "we don't have to 
rush to integrate it", as only in addition to the language plugins in Quanta, 
the multilang branch is actually required.

Anyhow, depending on how soon we are confident to release 4.2, I'd be OK with 
delaying my merge after 4.1 is released. I do hope for a first alpha release of 
Quanta this year though, hence 4.2 would have to be released until then.

Bye

PS: once we have sorted out what to merge for 4.1, we could release a first 
beta after everything is merged (i.e. feature freeze) and concentrate on bug 
fixing. Weekly betas (assuming we fix bugs fast enough), one or two RCs then the 
release.

@ Andreas: What time should be set for a string freeze? One month prior to 
release?
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100805/0c462886/attachment.sig>


More information about the KDevelop-devel mailing list