Releasing KDevelop 4.7

[Aleix Pol]

On Tue, Jul 1, 2014 at 12:37 AM, Milian Wolff <mail at milianw.de> wrote:

> On Wednesday 25 June 2014 15:36:15 Aleix Pol wrote:
> > On Wed, Jun 25, 2014 at 1:53 PM, Milian Wolff <mail at milianw.de> wrote:
> > > On Wednesday 25 June 2014 12:39:28 Milian Wolff wrote:
> > > > On Saturday 14 June 2014 19:06:49 Milian Wolff wrote:
> > > > > Hey all,
> > > > >
> > > > > as discussed with Aleix and Kevin during QtCS, we want to release
> > >
> > > KDevelop
> > >
> > > > > 4.7 asap. There are a few blockers still in master which I want to
> > >
> > > look at
> > >
> > > > > now. Here's my list, please comment on what regressions you
> notices:
> > > > >
> > > > > - assistant focus management
> > > > > sometimes, the assistant gets focus while it should not, e.g. in
> the
> > > > > middle
> > > > > of typing which leads to a very awkward workflow
> > > > >
> > > > > - project manager view focus management
> > > > > sometimes, instead of copying code from the editor, one copies the
> > > > > file
> > > > > from the project manager view. On paste, one then inserts the URL
> to
> > >
> > > said
> > >
> > > > > fail. Again, very awkward
> > > > >
> > > > > - cannot show multiple toolviews
> > > > > this used to work (see mailing thread about that from a few
> days/weeks
> > > > > ago).
> > > > >
> > > > > Once that's in, I think we can release master more or less as-is.
> > >
> > > Please
> > >
> > > > > take a minute to review your recent changes and make sure to polish
> > >
> > > them.
> > >
> > > > > I'll branch off master into 1.7/4.7 branches next week. We could
> then
> > >
> > > also
> > >
> > > > > release the first beta, hopefully. The final release should then
> > >
> > > happen in
> > >
> > > > > July, lets say on the 20th at the latest?
> > > >
> > > > I've now branched of 4.7/1.7 - these branches are now feature &
> string
> > > > frozen. The translators are notified about this. I'll prepare a first
> > >
> > > beta
> > >
> > > > release now and hope to then push a final version out in about a
> month.
> > >
> > > If
> > >
> > > > we find any serious issues, we can always release a second beta or
> move
> > >
> > > the
> > >
> > > > scheduled final release.
> > >
> > > Can someone please start a release announcement for 4.7 beta 1 on the
> > > wiki?
> > >
> > > Bye
> >
> > There you go:
> > http://community.kde.org/KDevelop/4.7
>
> I've now added some text, can someone proof-read it and extend it if
> necessary?
>
> Also, since writing a release note is always a burden to me and usually
> delays
> our releases, I'd like suggestions on how to improve this situation in the
> future. Maybe we should introduce the usage of some keyword in commit
> messages
> for noteworthy changes?
>
> Bye
>

I just skimmed through it, I changed a couple of small things. I think that
it's easier to read if we offer the changes in bullet-points rather than
text, which I guess looks more professional, but feels a bit like a school
composition and, in this case, we're dealing with hackers afterall.

Regarding keywords, I think it can be interesting, to do some of this,
maybe [1] using DIGEST could help us know which are interesting. On the
other hand sometimes many small commits make up for a mention in the
release announcement, and I'm unsure how we could cover those cases, I
guess some manual edition is always needed.

Aleix

[1] http://community.kde.org/Sysadmin/GitKdeOrgManual#Commit_hook_keywords
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20140701/8ac89f16/attachment-0001.html>