Hello. On 24.05.2018 15:37, Mike Blumenkrantz wrote: > I think this argument of not having enough time to review before a release > is a bit questionable. If we lack the resources to perform at least a > cursory review of incoming patches before a release, how can we possibly > have the capability as a project to even execute a quality release? Is the > claim then that we are instead using these resources to review patches > which have reached the repo without review? > > Getting into the habit of, at minimum, glancing at patches and determining > if it's something worthwhile for the current release cycle (e.g., a bug > fix) seems like it would be beneficial overall.
That is very much different from what you wrote in your first mail. Now you are asking for "cursory review" and glancing at patches to see if they should be in the release. In your first mail this sounded very different "I think we should make it a policy going forward that the stabilization period cannot begin until all pending patch submissions have been reviewed." If I take this literally the way you wrote it, something you requested before to do with your mails, this means freeze on hold until the patch queue is empty. You never wrote there that the "review" you mean in this case was glancing over the patches and determine if they are bug fixes that should go into a release. The last one is reasonable and is something I support. In contrast to the first statement where I have to put everything on hold until the whole patch queue is fully reviewed. Its that part I find unrealistic. regards Stefan Schmidt ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
