On 06/08/2018 01:51 PM, Mike Blumenkrantz wrote:
I think it's valuable to bring up possible points of confusion like this
when they exist, so thanks for bringing it up. There's no harm in asking
questions or requesting more details!
If everyone is in agreement with this proposal, I think it might be a good
idea to document it somewhere (
https://phab.enlightenment.org/w/release_roadmap/ seems like a good place,
but it's not very discoverable,
IMO, that sounds like the proper place. Anyone wondering about releases,
release schedule, or release procedures would likely be able to find
that page...
Cheers,
Chris
and
https://www.enlightenment.org/contrib/devs/start.md is a bit too high
level...) so that it can be referred to or modified in the future?
On Fri, Jun 8, 2018 at 1:44 PM Christopher Michael <cp.mich...@samsung.com>
wrote:
On 06/08/2018 12:57 PM, Derek Foreman wrote:
On 2018-06-08 11:44 AM, Christopher Michael wrote:
On 06/08/2018 11:17 AM, Mike Blumenkrantz wrote:
Hello,
Stefan is off for this entire month, so let's try organizing the
release a
bit while he's gone!
We had previously agreed to start the freeze "after Cedric's branches
merged". That branch was merged some time ago, and it seems we are
already
in bug fixing mode.
After speaking a bit with bu5hm4n/Marcel, who has been handling a lot
of
the bug fixing, I propose the following:
* We consider the freeze to have started as of last Friday (1 June
2018),
and proceed from there.
* During the freeze period, all newly-submitted features (ie. anything
submitted on or after the freeze start date) must go through patch
review
and receive 2+ approvals from core developers; if employed by Samsung,
the
developers must not work for the same office.
I was under the impression that one of the points of a freeze is that no
new features could be added and we can focus on bug fixes. Your mention
of newly-submitted features "after the freeze start date" is a little
misleading....
I read that as a way to handle any potential features already in the
review queue that didn't beat the retro-active freeze date.
Though, there was one time when I've had to add API during freeze to fix
a major wayland related bug.
My opinion, fwiw, is that features proposed after June 1 would need a
very strong justification at this point, and anything after today would
have to be an exceptional situation (absolutely required to fix a bug or
massive oversight, a showstopper).
Thanks,
Derek
Exactly. I just didn't want any new people to be confused as the
statement was a tad misleading ;)
Cheers,
Chris
* Feature patches submitted prior to the freeze date which are still
under
review and have received review comments prior to the freeze date can
be
merged/landed through normal patch review.
Marcel has also been working on improvements to our bug handling
workflow
which will be explained in a forthcoming mail. I believe that these
methods
should enable us to be in a good position to execute a release on or
near
the time of Stefan's return.
If nobody disagrees with the basic premise of beginning the freeze,
https://phab.enlightenment.org/T6926 is a great place to start looking
for
things to work on.
No disagreements here.
Cheers,
Chris
regards,
Mike
------------------------------------------------------------------------------
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
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
