[prev in list] [next in list] [prev in thread] [next in thread] 

List:       enlightenment-devel
Subject:    Re: [E-devel] 1 Week Remaining
From:       Mike Blumenkrantz <michael.blumenkrantz () gmail ! com>
Date:       2018-08-09 21:22:01
Message-ID: CAHwmOzd3q_7-QTefwJ2aL02M83XYGt7sxhDghO12Hpy7u7SA_w () mail ! gmail ! com
[Download RAW message or body]

There is still some confusion related to the feature proposal query on
phabricator: in order to appear in the query, the ticket must have the
'efl-1.22' tag as well as EITHER 'major_change' OR 'refactoring'. If it
does not meet both of these requirements (i.e., if (A && (B || C))) then it
will not appear in the sidebar query.

On Thu, Aug 9, 2018 at 5:06 PM Mike Blumenkrantz <
michael.blumenkrantz@gmail.com> wrote:

> Hello,
>
> It seems we are closing in on the final release for 1.21. If we do not
> encounter any major issues, then it's probable we will see the release
> happen next week.
>
> Given the proximity of the release, and the lack of any alternate
> proposals or negative feedback related to the (only) existing proposal,
> this means we will continue on according to the schedule as in
> https://phab.enlightenment.org/T7169, with members of the
> #efl_release_team project jointly handling all matters related to the
> release as an organized committee with no single person in charge.
>
> According to the schedule, this will be the agenda for roughly the next 5
> weeks:
> * We will continue adding feature proposals through the end of this week.
> A feature proposal must be created for any "major change" to the repo; note
> that trivial new features do not need proposals. If you are unsure whether
> your work item needs a proposal, there is no harm in creating one and
> having the community decide.
> * On Monday, a vote will be created on phabricator by the release team
> with each existing proposal at that time attached, and a tracking ticket
> will be created for the vote.
>   - Voting in this case means "voting to defer or reject this proposal";
> all votes must be accompanied by comments ON THE CORRESPONDING TICKET
> justifying the vote so that discussion can occur, and the author of the
> proposal can defend it. Comments should not be added on the vote itself, as
> this will only record the results of the vote.
> * As of the following Monday, the vote will end.
>   - Any proposal with 5 or more votes from #committers members will be
> deferred and cannot be merged
> * Development will progress for 4 weeks, after which there will be another
> week of voting
>
>
> A quick note on the comments for the vote: let's try to be professional
> and courteous about this. If you disagree with a proposal then you should
> provide a technical, fact-based argument against it.
>
>
> 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
[prev in list] [next in list] [prev in thread] [next in thread]