Hello, 2012/3/9 Alex Fiestas <afies...@kde.org>: > Hi there > > At Active sprint we've used a lunch break for talking about some > "Workflow Issues" we find with the current way of using git in the > workspace, just for mention a few discussed things from the top of m > head: > > - People merge things not ready to be merged (aka using git as we did svn) > - We don't want to change to a 3 month release (or something like that). > - Reviewboard is not the perfect tool for big changes > - Current time schedule has its benefits > > The resulting workflow if we take into account all of that is: > > - Keep the 6 month release period > - Keep the current schedule (soft freeze, hard freeze...) > - Move to a review based workflow before hard freeze (we need gerrit). > - Once we are on hard freeze, open merge for everyone so we can > continue fixing things easily.
As many of you might know, I have been a strong advocate of such a thing for quite some time and I cannot be more in agreement with Alex here. I think we should really improve the way our reviews are handled, and enforce more control over the quality of our code. > > Putting manpower aside, I think that this would be a good tentative > attempt for moving to a different thing, we keep a lot of the good > things we have right now and it will allow us to explore the benefits > of the merge based workflow. > > What do you think of it? > > BTW don't mention what we don't have enough reviewers, that's > something that can be work on later, ATM let's just assume we have > infinite man power ;p > _______________________________________________ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel