Movingranges branch

[Aleix Pol]

On Thu, Aug 5, 2010 at 12:46 PM, Milian Wolff <mail at milianw.de> wrote:

> 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
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
>
I think that if you (David) think that the branch is ready you should merge.
It's you who have coded it and who have to feel confident with it.

About releasing a 4.1, I'd say it's a little premature but given the big
changes that happened in Kate Part we probably want to release now but for
now the best would be, IMO, to get all the new code to trunk so that it can
be tested by us and we can provide a schedule from that.

Aleix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100805/190c558f/attachment.html>