Elisa, kdereview and a Release Schedule

[Matthieu Gallien]

Hello,

On mercredi 28 février 2018 20:14:49 CET Alexander Stippich wrote:
> Hello,
> 
> congrats to everyone on being accepted!

Thanks a lot Alex, I had completely forgotten this part in my mail.

> I have zero experience with doing releases, so I will just follow your lead.
> Doing 4 releases per year sounds reasonable in my opinion. And backporting
> fixes to one branch should also be doable.

I will post a blog about this when I have found how to manage this with 
phabricator (I seem to remember hearing about a calendar or something like 
that).

> For a list of features/blockers for a first release, I'd like to merge the
> controls2 branch and add remaining patches for HiDPI.
> Also, I think it is a good idea to finish the transition of some classes
> (e.g. manageAudioPlayer) from Qml to C++ and I think you wanted to make
> some more functions in the models non-blocking (similar to the
> allalbumsmodel). This way we should get a lot of testing for the underlying
> stuff which is then the base going forward.

I am working on the play list model. This is starting to have taken some time 
and I am still unsure about the correct way to do it.

I will give some more time to think about all the feedback and I try to 
quickly send another mail with proposals with dates including the dates of 
string freeze.

> And we should definitely add the icon for the first release.
> 
> Somewhat off-topic, I have some smaller changes still awaiting review :)
> https://phabricator.kde.org/D10643
> https://phabricator.kde.org/D10488

Sorry for them.

> Best regards,
> Alex
> 
> On Dienstag, 27. Februar 2018 22:15:46 CET 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
> 
> _______________________________________________
> Elisa mailing list
> Elisa at kde.org
> https://mail.kde.org/mailman/listinfo/elisa