Elisa, kdereview and a Release Schedule

[Matthieu Gallien]

On jeudi 1 mars 2018 20:06:10 CET Alexander Stippich wrote:
> Hello,
> 
> On Mittwoch, 28. Februar 2018 22:59:53 CET Matthieu Gallien wrote:
> > On mercredi 28 février 2018 19:03:48 CET Diego Gangl wrote:
> > > Hi,
> > > 
> > > That schedule sounds quite reasonable. Does that feature freeze include
> > > a
> > > string freeze too?
> > > 
> > > As for blockers, I think the tasks currently in progress in the
> > > workboard
> > > are a good list. IMO I would add replay gain support too, fiddling with
> > > the
> > > volume all the time gets tiring :)
> > 
> > I agree with the lack of replay gain support being annoying. Alexander, is
> > this one of the tags you plan to add ?
> 
> I haven't really looked at it yet, but I think this needs some more work and
> testing in KFileMetaData because there is no real standard. Since I'm
> currently looking into that area, I'm willing to do that but it will
> probably take some time. Same goes for the cover art support. So I don't
> know if we should wait for those depending on when the first release should
> happen.

OK, if everybody agrees, let's make a release branch now with a string freeze 
in two weeks and a release in 4 weeks.
I am quite busy this week end. I may do the branching only monday. After that, 
let's polish the first release and push big changes to master only.

I will act on that if evrybody is OK with the plan.

> Best regards,
> Alex
> 
> > > Cheers!
> > > 
> > > On martes, 27 de febrero de 2018 18:15:46 -03 Matthieu Gallien wrote:
> > > > Hello,
> > > > 
> > > > Given that Elisa is now officially a KDE project, we should aim to
> > > > release
> > > > a first stable release and also agree on a release rhythm.
> > > > 
> > > > I am a bit short on time today but do you have suggestions or ideas
> > > > for
> > > > the
> > > > schedule of the first release ?
> > > > 
> > > > We should also list as soon as possible a list of release blocking
> > > > points.
> > > > For example, I would like to get the new icon before the release.
> > > > 
> > > > I would like to have a release rhythm of 3 months with a feature
> > > > freeze
> > > > after one and half month and with one and half months of bugfix
> > > > support.
> > > > That would give something like that:
> > > > 
> > > > T0 + 1.5 months: we create 0.1 branch where only bug fix and polishing
> > > > is
> > > > allowed. New features land in master branch.
> > > > T0 + 3 months we release 0.1
> > > > T0 + 4.5 months we close the 0.1 branch and we no longer push bug fix
> > > > to
> > > > it
> > > > and at the same time, we create 0.2 branch where we have a feature
> > > > freeze.
> > > > 
> > > > We would have only two parallel branches and that may already be too
> > > > much
> > > > given the size of the team.
> > > > 
> > > > What do you think ?
> > > > 
> > > > Best regards
> > > > 
> > > > --
> > > > Matthieu Gallien
> > > 
> > > ---
> > > Diego Gangl
> > > sinestesia.co
> > > 
> > > 
> > > _______________________________________________
> > > Elisa mailing list
> > > Elisa at kde.org
> > > https://mail.kde.org/mailman/listinfo/elisa
> > 
> > _______________________________________________
> > Elisa mailing list
> > Elisa at kde.org
> > https://mail.kde.org/mailman/listinfo/elisa
> 
> _______________________________________________
> Elisa mailing list
> Elisa at kde.org
> https://mail.kde.org/mailman/listinfo/elisa