Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On Wed, 23 May 2018 07:07:04 +0100 Stefan Schmidt said: > Hello. > > On 17.05.2018 18:47, Mike Blumenkrantz wrote: > > I think we should make it a policy going forward that the stabilization > > period cannot begin until all pending patch submissions have been reviewed. > > There are still a ton of patches out there which haven't been looked at, > > and "I didn't feel like reviewing patches" should never be a reason why > > patches don't make it into a release. > > > > This doesn't mean that all patches need to be merged, but patches submitted > > during a release cycle should at least be reviewed during that cycle. > > My take on this is that we should aim for encouraging people to look at > patches and do reviews. This encouragement should not come by a policy > forcing them to do it. > > And if we want to go back to time based releases this would not fly. > Holding up the release for patches to be reviewed is basically the same > as holding it up for a feature to be merged. Both require developer time > that might or might not be available at the time for the release. i'd like to see regular timed releases again. they don't have to be spot-on time. a few weeks here or there won't hurt, so if we wait a week or 2 for something to land, then that may be ok, but only if it realistically is going to do that. i don't think a policy of "all patches submitted must be reviewed 9where review may even be just a cursory glance" works with a schedule. people have many things to do and things of varying priority and perhaps things of higher priority are needing doing before a release. -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On Thu, 24 May 2018 12:29:21 -0400 Mike Blumenkrantz wrote: > > To restate and completely define every term used: my proposal is that > every patch submitted during a release cycle must be reviewed prior > to the release deployment. The intention maybe more clear to say View and Comment or Acknowledge. Where as; View + Comment == Review That seems to be what Mike is saying below essentially. Not a simple "Thank you for your submission" comment. Some comment of substance to acknowledge the work has been "reviewed" or committed, rejected, etc. That should not take long to at least skim something submitted and make an initial comment. If actionable, that may take more time. > Definitions of terms used: ... > REVIEWED: someone in the commiters project group ( > https://phab.enlightenment.org/tag/committers/) must comment on a > patch, either rejecting it (entirely or because it requires changes), > accepting it (stating intent to merge during the release cycle, > intent to merge after the release cycle, or as a conceptual approval > of a patch which needs subsequent and more in-depth review by someone > else), or simply commenting on it to indicate whether it is a > beneficial change which should eventually be accepted -- William L. Thomson Jr. pgp4nw3BxfLSP.pgp Description: OpenPGP digital signature -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
Thanks for your reply, I think you've raised some good points. I will attempt to address them below, in full. I suppose I could have been more clear in defining what "review" means, but this confusion seems to (in my mind) largely be the result of not having a patch review culture or mindset within the project. Patch review does not always require spending hours poring over every line of code: it can, and frequently should, begin with someone briefly checking the patch to see if it's even something beneficial to the project. If someone submits a patch to remove all authors from the AUTHORS file, I would not need to review the content of the patch in order to reject it. Similarly, if someone submits a large patch implementing a much-requested feature then I would know that the eventual result of the patch should be worthwhile even without reviewing its content; the first version may not be acceptable upon in-depth review, but giving an initial response at least allows the author to know that their work is both seen and appreciated. To restate and completely define every term used: my proposal is that every patch submitted during a release cycle must be reviewed prior to the release deployment. Definitions of terms used: PATCH: any change to the efl repo submitted for review in the project's patch review system (currently phabricator) SUBMITTED DURING: the date on the post of the phabricator patch is during the release cycle RELEASE CYCLE: any major release development time period including both the feature and feature freeze sections of the period, excluding the time which begins 48h prior to the scheduled "final" release time, where the 'scheduled "final" release time' is defined as 'the time set as of the deployment of the last pre-release prior to the "final"' MUST: this is a requirement for the release to be deployed REVIEWED: someone in the commiters project group ( https://phab.enlightenment.org/tag/committers/) must comment on a patch, either rejecting it (entirely or because it requires changes), accepting it (stating intent to merge during the release cycle, intent to merge after the release cycle, or as a conceptual approval of a patch which needs subsequent and more in-depth review by someone else), or simply commenting on it to indicate whether it is a beneficial change which should eventually be accepted PRIOR: any point in time before the release is deployed RELEASE DEPLOYMENT: the point at which mails are sent for the announcements of the tarballs I've added to this proposal an explicit 48h gap prior to the release in order to ensure that the release is not unnecessarily delayed by individuals submitting huge numbers of patches immediately prior to the scheduled release time. Patches submitted after the defined 'release cycle' time period are considered as submitted during the next release cycle. The delay of a release (e.g., due to a newly-discovered showstopper bug) after the last pre-release would not affect the 48h time point as it applies to the time as scheduled at the time of the last pre-release deployment; once this point has been reached, all patches submitted are considered part of the next release cycle and are not required to be reviewed prior to deploying the release. A simple way to check the open patch submissions is to use a query like this: https://phab.enlightenment.org/differential/query/gIFEVr3jmk.q/#R Going forward, all committers group members on phabricator are automatically added to all patch submisisons for the efl repo which should further increase patch visibility. If any part of this needs further elaboration, please let me know. On Thu, May 24, 2018 at 10:05 AM Stefan Schmidt wrote: > 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 t
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
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. On Wed, May 23, 2018 at 2:07 AM Stefan Schmidt wrote: > Hello. > > On 17.05.2018 18:47, Mike Blumenkrantz wrote: > > I think we should make it a policy going forward that the stabilization > > period cannot begin until all pending patch submissions have been > reviewed. > > There are still a ton of patches out there which haven't been looked at, > > and "I didn't feel like reviewing patches" should never be a reason why > > patches don't make it into a release. > > > > This doesn't mean that all patches need to be merged, but patches > submitted > > during a release cycle should at least be reviewed during that cycle. > > My take on this is that we should aim for encouraging people to look at > patches and do reviews. This encouragement should not come by a policy > forcing them to do it. > > And if we want to go back to time based releases this would not fly. > Holding up the release for patches to be reviewed is basically the same > as holding it up for a feature to be merged. Both require developer time > that might or might not be available at the time for the release. > > 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 > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
Hello. On 17.05.2018 18:47, Mike Blumenkrantz wrote: > I think we should make it a policy going forward that the stabilization > period cannot begin until all pending patch submissions have been reviewed. > There are still a ton of patches out there which haven't been looked at, > and "I didn't feel like reviewing patches" should never be a reason why > patches don't make it into a release. > > This doesn't mean that all patches need to be merged, but patches submitted > during a release cycle should at least be reviewed during that cycle. My take on this is that we should aim for encouraging people to look at patches and do reviews. This encouragement should not come by a policy forcing them to do it. And if we want to go back to time based releases this would not fly. Holding up the release for patches to be reviewed is basically the same as holding it up for a feature to be merged. Both require developer time that might or might not be available at the time for the release. 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On May 18, 2018 2:18 AM, Stefan Schmidt wrote: > On 18.05.2018 06:45, Carsten Haitzler (The Rasterman) wrote: > > On Thu, 17 May 2018 13:14:48 +0200 Stefan Schmidt ste...@datenfreihafen.org > > said: > > > On 08.05.2018 21:41, Stefan Schmidt wrote: > > > > On 04/27/2018 01:38 PM, Stefan Schmidt wrote: > > > > There sadly has not been as much progress as hoped for. > > > > I still wait for the following items: > > > > > > > > o Cedric's last branch to be merged (lifecycle?). What is the status > > > > here? > > > > Maybe its to massive to get landed for 1.21? I have been told it would > > > > be > > > > merged like 10 days ago. > > > > > > This is the one getting me stomachache. It keeps postponing with new > > > problems being found. And surely there will be more problems showing up > > > when merged into master. > > > > i suspected it'd be like this just because of the nature of the beast here, > > which is why i aired the "maybe this needs to go after release". i see you > > are > > probably on that bandwagon too, and i'm hoping to see a general feeling on > > this. > > I am not at the point yet where I would require a postpone, but I am > worried. I wanted Cedric to ahve enough time to look at problems when it > it merged into master. I now have Enlightenment and Terminology running. The last bug I am chasing as far as I have seen is in the fileselector/genlist. Not sure exactly where, but likely a copy/paste mistake in my branch, shouldn't be hard to figure out. The main thing I have discovered while working on this is that we had a lot of work around our past lifecycle which I wasn't so aware of. With our old lifecycle, you can write code in a binding that would actually lead to a segfault due to this hack while they shouldn't. While fixing this lifecycle issue, I stumble also on bugs that would have been triggered by normal use of the API. Basically I really think this branch should land. I am thinking I should be able to fix the fileselector/genlist bug by sometime Sunday and will be able to push the branch on Monday morning. Cedric -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
Hello On 18.05.2018 06:45, Carsten Haitzler (The Rasterman) wrote: > On Thu, 17 May 2018 13:14:48 +0200 Stefan Schmidt > said: > >> Hello. >> >> Another update on this. >> >> On 08.05.2018 21:41, Stefan Schmidt wrote: >>> >>> On 04/27/2018 01:38 PM, Stefan Schmidt wrote: >>> >>> There sadly has not been as much progress as hoped for. >>> I still wait for the following items: >>> >>> o Cedric's last branch to be merged (lifecycle?). What is the status here? >>> Maybe its to massive to get landed for 1.21? I have been told it would be >>> merged like 10 days ago. >> >> This is the one getting me stomachache. It keeps postponing with new >> problems being found. And surely there will be more problems showing up >> when merged into master. > > i suspected it'd be like this just because of the nature of the beast here, > which is why i aired the "maybe this needs to go after release". i see you > are > probably on that bandwagon too, and i'm hoping to see a general feeling on > this. I am not at the point yet where I would require a postpone, but I am worried. I wanted Cedric to ahve enough time to look at problems when it it merged into master. >> Cedric, you think you can get this in until Tuesday? I wanted to start >> the freeze end of next week, more below. >> >>> o https://phab.enlightenment.org/D5908 needs review >> >> Merged now. >> >>> o https://phab.enlightenment.org/D6046 needs review >> >> Still in progress. Raster, could you check if the added comment >> addressed your concern? > > yup. that's one of those i have flagged. i have a lot of flags... ok, but its on your agenda >>> o Comments on the flat theme from Raster >> >> We talked about it again and this will keep going in parallel with the >> hopes to have it ready and merged into master before the release. I am >> willing to have an exception here as the theme should be isolated enough >> to not cause to much trouble when being merged late. We still should >> make a call if we have it in or not two weeks before the release (beta2 >> time). > > agreed on this. > >>> Once we have these sorted we can start with the stabilization phase. >>> As we have no date for this yet I can only give a rough schedule to give >>> people an idea. This needs to be updated once we start with the alpha. >> >> Besides the lifecycle branch I think we are in shape now to start the >> stabilization. Nothing else besides the ones above have been brought up. >> >> It seems time to get into the huge backlog of bugs to get them fixed. :-) >> >> The idea is now to have the freeze starting end of next week. The items >> from above have been mentioned early enough that I might be ok to have >> them slip in after the alpha, but don't count on it. Instead try to make >> sure you get them in until Monday or Tuesday. >> >> Here is an updated schedule I put up for discussion. Speak up NOW if you >> have problems with it. >> >> === Schedule === >> 2018-05-24 Merge window is over. (handled by Stefan) >> * Only bug fixes from this point >> * Alpha release tarball >> * We really need to sort out if we have bigger issues lingering around >> due to all the last minute rush >> 2018-06-18 Beta1 release tarball (handled by Raster) >> * Only critical fixes from this point >> 2018-06-25 Beta2 release tarball (handled by Raster) >> 2018-07-02 Beta3 release tarball (handled by Raster) >> 2018-07-09 EFL 1.21 is out (handled by Stefan) > > this sounds sensible... but i suspect we're going to have a lot more betas as > we will be fixing many more bugs... :) Could be, hard to tell. I adjusted for more time for bug fixing already but this was a long cycle with a lot of changes. I will take my round through the bug tracker when we are hitting the freeze. Mike and Stephen already started to tag regressions and show stoppers. Thanks for that! 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On Thu, 17 May 2018 13:47:18 -0400 Mike Blumenkrantz said: > I think we should make it a policy going forward that the stabilization > period cannot begin until all pending patch submissions have been reviewed. > There are still a ton of patches out there which haven't been looked at, > and "I didn't feel like reviewing patches" should never be a reason why > patches don't make it into a release. > > This doesn't mean that all patches need to be merged, but patches submitted > during a release cycle should at least be reviewed during that cycle. that's going to add months then to this. there are a lot of patches out there. as a policy 4 in general this would hold releases hostage to patches and their review. if there just are a lot of them submitted or there already, or take time for review (some patches are trivial and take minutes, some take hours). holding a release hostage to this is IMHO a very bad idea. > On Thu, May 17, 2018 at 10:32 AM Al Poole wrote: > > > Beautiful. > > > > On Thu, May 17, 2018 at 12:14 PM, Stefan Schmidt < > > ste...@datenfreihafen.org> > > wrote: > > > > > Hello. > > > > > > Another update on this. > > > > > > On 08.05.2018 21:41, Stefan Schmidt wrote: > > > > > > > > On 04/27/2018 01:38 PM, Stefan Schmidt wrote: > > > > > > > > There sadly has not been as much progress as hoped for. > > > > I still wait for the following items: > > > > > > > > o Cedric's last branch to be merged (lifecycle?). What is the status > > > here? Maybe its to massive to get landed for 1.21? I have been told it > > > > would be merged like 10 days ago. > > > > > > This is the one getting me stomachache. It keeps postponing with new > > > problems being found. And surely there will be more problems showing up > > > when merged into master. > > > > > > Cedric, you think you can get this in until Tuesday? I wanted to start > > > the freeze end of next week, more below. > > > > > > > o https://phab.enlightenment.org/D5908 needs review > > > > > > Merged now. > > > > > > > o https://phab.enlightenment.org/D6046 needs review > > > > > > Still in progress. Raster, could you check if the added comment > > > addressed your concern? > > > > > > > o Comments on the flat theme from Raster > > > > > > We talked about it again and this will keep going in parallel with the > > > hopes to have it ready and merged into master before the release. I am > > > willing to have an exception here as the theme should be isolated enough > > > to not cause to much trouble when being merged late. We still should > > > make a call if we have it in or not two weeks before the release (beta2 > > > time). > > > > > > > Once we have these sorted we can start with the stabilization phase. > > > > As we have no date for this yet I can only give a rough schedule to > > give > > > people an idea. > > > > This needs to be updated once we start with the alpha. > > > > > > Besides the lifecycle branch I think we are in shape now to start the > > > stabilization. Nothing else besides the ones above have been brought up. > > > > > > It seems time to get into the huge backlog of bugs to get them fixed. :-) > > > > > > The idea is now to have the freeze starting end of next week. The items > > > from above have been mentioned early enough that I might be ok to have > > > them slip in after the alpha, but don't count on it. Instead try to make > > > sure you get them in until Monday or Tuesday. > > > > > > Here is an updated schedule I put up for discussion. Speak up NOW if you > > > have problems with it. > > > > > > === Schedule === > > > 2018-05-24 Merge window is over. (handled by Stefan) > > > * Only bug fixes from this point > > > * Alpha release tarball > > > * We really need to sort out if we have bigger issues lingering around > > > due to all the last minute rush > > > 2018-06-18 Beta1 release tarball (handled by Raster) > > > * Only critical fixes from this point > > > 2018-06-25 Beta2 release tarball (handled by Raster) > > > 2018-07-02 Beta3 release tarball (handled by Raster) > > > 2018-07-09 EFL 1.21 is out (handled by Stefan) > > > > > > This would basically bring it down to a 6 weeks stabilization window. > > > > > > Thoughts? > > > > > > 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 > > > enlightenment-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > > > -- > > 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 > > enlig
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On Thu, 17 May 2018 13:14:48 +0200 Stefan Schmidt said: > Hello. > > Another update on this. > > On 08.05.2018 21:41, Stefan Schmidt wrote: > > > > On 04/27/2018 01:38 PM, Stefan Schmidt wrote: > > > > There sadly has not been as much progress as hoped for. > > I still wait for the following items: > > > > o Cedric's last branch to be merged (lifecycle?). What is the status here? > > Maybe its to massive to get landed for 1.21? I have been told it would be > > merged like 10 days ago. > > This is the one getting me stomachache. It keeps postponing with new > problems being found. And surely there will be more problems showing up > when merged into master. i suspected it'd be like this just because of the nature of the beast here, which is why i aired the "maybe this needs to go after release". i see you are probably on that bandwagon too, and i'm hoping to see a general feeling on this. > Cedric, you think you can get this in until Tuesday? I wanted to start > the freeze end of next week, more below. > > > o https://phab.enlightenment.org/D5908 needs review > > Merged now. > > > o https://phab.enlightenment.org/D6046 needs review > > Still in progress. Raster, could you check if the added comment > addressed your concern? yup. that's one of those i have flagged. i have a lot of flags... > > o Comments on the flat theme from Raster > > We talked about it again and this will keep going in parallel with the > hopes to have it ready and merged into master before the release. I am > willing to have an exception here as the theme should be isolated enough > to not cause to much trouble when being merged late. We still should > make a call if we have it in or not two weeks before the release (beta2 > time). agreed on this. > > Once we have these sorted we can start with the stabilization phase. > > As we have no date for this yet I can only give a rough schedule to give > > people an idea. This needs to be updated once we start with the alpha. > > Besides the lifecycle branch I think we are in shape now to start the > stabilization. Nothing else besides the ones above have been brought up. > > It seems time to get into the huge backlog of bugs to get them fixed. :-) > > The idea is now to have the freeze starting end of next week. The items > from above have been mentioned early enough that I might be ok to have > them slip in after the alpha, but don't count on it. Instead try to make > sure you get them in until Monday or Tuesday. > > Here is an updated schedule I put up for discussion. Speak up NOW if you > have problems with it. > > === Schedule === > 2018-05-24 Merge window is over. (handled by Stefan) > * Only bug fixes from this point > * Alpha release tarball > * We really need to sort out if we have bigger issues lingering around > due to all the last minute rush > 2018-06-18 Beta1 release tarball (handled by Raster) > * Only critical fixes from this point > 2018-06-25 Beta2 release tarball (handled by Raster) > 2018-07-02 Beta3 release tarball (handled by Raster) > 2018-07-09 EFL 1.21 is out (handled by Stefan) this sounds sensible... but i suspect we're going to have a lot more betas as we will be fixing many more bugs... :) > This would basically bring it down to a 6 weeks stabilization window. > > Thoughts? > > 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 > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
I think we should make it a policy going forward that the stabilization period cannot begin until all pending patch submissions have been reviewed. There are still a ton of patches out there which haven't been looked at, and "I didn't feel like reviewing patches" should never be a reason why patches don't make it into a release. This doesn't mean that all patches need to be merged, but patches submitted during a release cycle should at least be reviewed during that cycle. On Thu, May 17, 2018 at 10:32 AM Al Poole wrote: > Beautiful. > > On Thu, May 17, 2018 at 12:14 PM, Stefan Schmidt < > ste...@datenfreihafen.org> > wrote: > > > Hello. > > > > Another update on this. > > > > On 08.05.2018 21:41, Stefan Schmidt wrote: > > > > > > On 04/27/2018 01:38 PM, Stefan Schmidt wrote: > > > > > > There sadly has not been as much progress as hoped for. > > > I still wait for the following items: > > > > > > o Cedric's last branch to be merged (lifecycle?). What is the status > > here? Maybe its to massive to get landed for 1.21? I have been told it > > > would be merged like 10 days ago. > > > > This is the one getting me stomachache. It keeps postponing with new > > problems being found. And surely there will be more problems showing up > > when merged into master. > > > > Cedric, you think you can get this in until Tuesday? I wanted to start > > the freeze end of next week, more below. > > > > > o https://phab.enlightenment.org/D5908 needs review > > > > Merged now. > > > > > o https://phab.enlightenment.org/D6046 needs review > > > > Still in progress. Raster, could you check if the added comment > > addressed your concern? > > > > > o Comments on the flat theme from Raster > > > > We talked about it again and this will keep going in parallel with the > > hopes to have it ready and merged into master before the release. I am > > willing to have an exception here as the theme should be isolated enough > > to not cause to much trouble when being merged late. We still should > > make a call if we have it in or not two weeks before the release (beta2 > > time). > > > > > Once we have these sorted we can start with the stabilization phase. > > > As we have no date for this yet I can only give a rough schedule to > give > > people an idea. > > > This needs to be updated once we start with the alpha. > > > > Besides the lifecycle branch I think we are in shape now to start the > > stabilization. Nothing else besides the ones above have been brought up. > > > > It seems time to get into the huge backlog of bugs to get them fixed. :-) > > > > The idea is now to have the freeze starting end of next week. The items > > from above have been mentioned early enough that I might be ok to have > > them slip in after the alpha, but don't count on it. Instead try to make > > sure you get them in until Monday or Tuesday. > > > > Here is an updated schedule I put up for discussion. Speak up NOW if you > > have problems with it. > > > > === Schedule === > > 2018-05-24 Merge window is over. (handled by Stefan) > > * Only bug fixes from this point > > * Alpha release tarball > > * We really need to sort out if we have bigger issues lingering around > > due to all the last minute rush > > 2018-06-18 Beta1 release tarball (handled by Raster) > > * Only critical fixes from this point > > 2018-06-25 Beta2 release tarball (handled by Raster) > > 2018-07-02 Beta3 release tarball (handled by Raster) > > 2018-07-09 EFL 1.21 is out (handled by Stefan) > > > > This would basically bring it down to a 6 weeks stabilization window. > > > > Thoughts? > > > > 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 > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > -- > 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 > -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
Beautiful. On Thu, May 17, 2018 at 12:14 PM, Stefan Schmidt wrote: > Hello. > > Another update on this. > > On 08.05.2018 21:41, Stefan Schmidt wrote: > > > > On 04/27/2018 01:38 PM, Stefan Schmidt wrote: > > > > There sadly has not been as much progress as hoped for. > > I still wait for the following items: > > > > o Cedric's last branch to be merged (lifecycle?). What is the status > here? Maybe its to massive to get landed for 1.21? I have been told it > > would be merged like 10 days ago. > > This is the one getting me stomachache. It keeps postponing with new > problems being found. And surely there will be more problems showing up > when merged into master. > > Cedric, you think you can get this in until Tuesday? I wanted to start > the freeze end of next week, more below. > > > o https://phab.enlightenment.org/D5908 needs review > > Merged now. > > > o https://phab.enlightenment.org/D6046 needs review > > Still in progress. Raster, could you check if the added comment > addressed your concern? > > > o Comments on the flat theme from Raster > > We talked about it again and this will keep going in parallel with the > hopes to have it ready and merged into master before the release. I am > willing to have an exception here as the theme should be isolated enough > to not cause to much trouble when being merged late. We still should > make a call if we have it in or not two weeks before the release (beta2 > time). > > > Once we have these sorted we can start with the stabilization phase. > > As we have no date for this yet I can only give a rough schedule to give > people an idea. > > This needs to be updated once we start with the alpha. > > Besides the lifecycle branch I think we are in shape now to start the > stabilization. Nothing else besides the ones above have been brought up. > > It seems time to get into the huge backlog of bugs to get them fixed. :-) > > The idea is now to have the freeze starting end of next week. The items > from above have been mentioned early enough that I might be ok to have > them slip in after the alpha, but don't count on it. Instead try to make > sure you get them in until Monday or Tuesday. > > Here is an updated schedule I put up for discussion. Speak up NOW if you > have problems with it. > > === Schedule === > 2018-05-24 Merge window is over. (handled by Stefan) > * Only bug fixes from this point > * Alpha release tarball > * We really need to sort out if we have bigger issues lingering around > due to all the last minute rush > 2018-06-18 Beta1 release tarball (handled by Raster) > * Only critical fixes from this point > 2018-06-25 Beta2 release tarball (handled by Raster) > 2018-07-02 Beta3 release tarball (handled by Raster) > 2018-07-09 EFL 1.21 is out (handled by Stefan) > > This would basically bring it down to a 6 weeks stabilization window. > > Thoughts? > > 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 > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
Hello. Another update on this. On 08.05.2018 21:41, Stefan Schmidt wrote: > > On 04/27/2018 01:38 PM, Stefan Schmidt wrote: > > There sadly has not been as much progress as hoped for. > I still wait for the following items: > > o Cedric's last branch to be merged (lifecycle?). What is the status here? > Maybe its to massive to get landed for 1.21? I have been told it > would be merged like 10 days ago. This is the one getting me stomachache. It keeps postponing with new problems being found. And surely there will be more problems showing up when merged into master. Cedric, you think you can get this in until Tuesday? I wanted to start the freeze end of next week, more below. > o https://phab.enlightenment.org/D5908 needs review Merged now. > o https://phab.enlightenment.org/D6046 needs review Still in progress. Raster, could you check if the added comment addressed your concern? > o Comments on the flat theme from Raster We talked about it again and this will keep going in parallel with the hopes to have it ready and merged into master before the release. I am willing to have an exception here as the theme should be isolated enough to not cause to much trouble when being merged late. We still should make a call if we have it in or not two weeks before the release (beta2 time). > Once we have these sorted we can start with the stabilization phase. > As we have no date for this yet I can only give a rough schedule to give > people an idea. > This needs to be updated once we start with the alpha. Besides the lifecycle branch I think we are in shape now to start the stabilization. Nothing else besides the ones above have been brought up. It seems time to get into the huge backlog of bugs to get them fixed. :-) The idea is now to have the freeze starting end of next week. The items from above have been mentioned early enough that I might be ok to have them slip in after the alpha, but don't count on it. Instead try to make sure you get them in until Monday or Tuesday. Here is an updated schedule I put up for discussion. Speak up NOW if you have problems with it. === Schedule === 2018-05-24 Merge window is over. (handled by Stefan) * Only bug fixes from this point * Alpha release tarball * We really need to sort out if we have bigger issues lingering around due to all the last minute rush 2018-06-18 Beta1 release tarball (handled by Raster) * Only critical fixes from this point 2018-06-25 Beta2 release tarball (handled by Raster) 2018-07-02 Beta3 release tarball (handled by Raster) 2018-07-09 EFL 1.21 is out (handled by Stefan) This would basically bring it down to a 6 weeks stabilization window. Thoughts? 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On Wed, 9 May 2018 17:19:43 +0930 Simon Lees wrote: > > Besides the idea that I'm still not sure about the whole idea of a new > theme landing for a efl release, for people using the default theme > not even upgrading e and getting a completely different theme seems > slightly weird, personally I think it would be better to coordinate > it somehow with the e23 release if timing ends up being near right. I can understand the perspective that one is still running the same version of E, upgrades EFL and now they have a new theme/look to E. That said, I think the same applies to GTK, Qt and likely others. Those have to be themed for any application. I do not run Gnome, so do I not get a theme from GTK? Or since I do not run KDE no theme for Qt? Those still have some default them that comes from within the toolkit. We think of themes as belong to the desktop, UI, but they really belong to the toolkit. I think most tend to try to coordinate a new theme with a new desktop UI release as to not surprise users. Maybe a new release of E would help there. New major version at same time as EFL, and then no surprise. Are you all planning to keep the current theme available? Or is the flat theme replacing that, such that one cannot switch? If the current theme can remain as is, with the flat theme being a new default. Then that would ease the problem of anyone running the current theme. That would not switch per their settings. Well maybe the default would switch, but they could switch back to the old theme if they liked. Likely easiest to just do a new release of E along with EFL. Then its not a surprised and people should expect changes. -- William L. Thomson Jr. pgpJDxhDAIkvO.pgp Description: OpenPGP digital signature -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On May 8, 2018 11:34 PM, Marcel Hollerbach wrote: > On 05/09/2018 03:51 AM, Cedric Bail wrote: > > On May 8, 2018 12:41 PM, Stefan Schmidt ste...@osg.samsung.com wrote: > > > On 04/27/2018 01:38 PM, Stefan Schmidt wrote: > > > > Its been a while. About to get our act together and get everything in > > > > place so we can start the 1.21 stabilization phase. > > > > > > > > We had this brought up at the two IRC meetings we had and I wanted to > > > > reach out here as well to understand what pieces people here are > > > > working on that need finishing before we can go start stabilization. > > > > > > > > I know from Cedric that he still has two branches he wants to get > > > > merged (a third one was going in already). Supposedly this should happen > > > > this week. > > > > > > > > What else is it that we are working on? If you have something, speak up > > > > NOW! > > > > > > There sadly has not been as much progress as hoped for. > > > I still wait for the following items: > > > > > > o Cedric's last branch to be merged (lifecycle?). What is the status > > > here? Maybe its to massive to get landed for 1.21? I have been told it > > > would be merged like 10 days ago. > > > > Yes, I have found much more mistake than anticipated and some hack that I > > didn't know we had. I have fixed all the hack. I am now reviewing all the > > warning that elementary tests suite is triggering and see if they are > > genuine or unrelated. I know there is still a problem during shutdown with > > how focus expect the parent object to always be there during destructor. > > The branch can already run enlightenment, terminology and the C# bindings > > fine. I am hoping to land this as soon as possible, but I don't want to > > rush it either. > > > > It is difficult to say how much more work around our inconsistent previous > > lifecycle I might discover and need to untangle, but hopefully I will be > > done very soon (a matter of days). > > The focus stuff is fixed and there are phab revisions for this, which > are waiting for your review. Oh, I missed that new patch. Will take a look during the day. > A bit more: Not focus is the problem here, the problem is, that > composition is setting the parent of the attached object to the object > where you are attaching to, thus this attached object now is destroyed > when the object is invalidated (before destructor). Before it was > destructed when the destructor chain got to the efl.object class. > What this means is, this is not the mistake of the focus code, you > changed how the deletion of those objects are working, you have to do > basically the same on every object that uses composition, thats efl_net, > efl_ui_text, efl_ui_tags, efl_ui_video [...] Sorry I didn't want to specifically blame you or anyone on this. So let me clarify, as it was a common missunderstanding that people used when building their widget with the new API, that they expected the parent relationship to always be there during destructor. This was true to a certain extent with C and simple reference pattern, but if you where to do : efl_ref(obj); efl_del(obj); efl_unref(obj);, it would have resulted in the exact same problem. This would be more visible for some bindings that use efl_ref/efl_unref heavily. The main change is to enforce consistency in behavior and give guarantee to developpers about what to really expect in each context. If you are in the destructor, you have no parent (compared to the most likely having one, but maybe not of before) and now invalidate will always be triggered at the time when you loose your parent. So invalidate will always have a valid parent. That is also guaranteed. Cedric -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On Wed, May 9, 2018 at 3:50 AM Simon Lees wrote: > > > On 09/05/18 11:04, Carsten Haitzler (The Rasterman) wrote: > > On Wed, 02 May 2018 16:38:07 + Stephen Houston < > smhousto...@gmail.com> said: > > > > Here's my take. it makes it or it doesn't. Releasing on time is all > about that. > > So sure, make a concerted effort, but don't delay if it doesn't make it. > We can > > "cut corners" like don't bother doing the colroclass recoloring > (requires code > > in elm to load/save/edit/configure color class config files, anmd then > choose > > the right one and apply it). can possibly cut corners on scalability > (though > > more important than color classes because colors is a preference, > scaling is > > nercessary, so it'd have to basically scale but we could skip making it > scale > > "beautifully")... i'm open for suggestions on how and what to cut to > make the > > timeline... > > > > I'd just like to say that timed releases is not about big milestones for > every > > release. It's about a steady flow of updates and improvements small or > large, > > rather than large gaps. So let's say we do have a "headline feature" this > > release, and maybe another the next release. We'll be stuck with none the > > release after etc. and so this will be common. Some releases will get big > > headline things, some may get multiple, some may get none and just small > > changes. It's life with timed releases. :) > > > > The problem with cutting back and taking shortcuts to make the timeline > is that inevitably after the release people will get busy on other > things and won't get around to going back and fixing all the things that > weren't done. So personally I'd go with no shortcuts and if its not done > its not done and can wait for the next release. > > Besides the idea that I'm still not sure about the whole idea of a new > theme landing for a efl release, for people using the default theme not > even upgrading e and getting a completely different theme seems slightly > weird, personally I think it would be better to coordinate it somehow > with the e23 release if timing ends up being near right. > That's just how themes work. There have been fewer than 200 patches to Enlightenment since the previous release, and the majority of them have already shipped in stable releases. It's unlikely that there would be a need for an Enlightenment release in the near future unless it's solely for the purpose of bumping the version number. > > >> Raster this is more of a question for you. You know my thoughts on > theme > >> being a pressing issue. Is this something we as the community can band > >> together during stabilization and have flat ready to go for 1.21 or is > this > >> something that we will have to put off yet again for a later release? > >> > >> My thoughts are that introducing the flat theme could be the headlining > pop > >> that this 1.21 release needs... i.e. a selling point for the release to > be > >> more attractive to users other than just being mostly a big fix release > >> with just a preview of the interfaces work. So we could say the big > >> milestone for the 1.21 release is the new theme and the big milestone > for > >> 1.22 is interfaces rather than somewhat blandly saying this is a big fix > >> release with a tech preview of interfaces and then saying 1.22 has two > big > >> introductions the theme and interfaces. That would also help with > >> stabilization and release process for 1.22 as we wouldn't be having to > >> focus on two new large introductions- flat and interfaces in the same > >> release. > >> > >> Just my thoughts here, and obviously not something worth having a knock > >> down drag out debate over. > >> > >> Stephen > >> > >> On Wed, May 2, 2018, 11:27 AM 조재현 wrote: > >> > >>> 5908 and D5988. (D6008 has been submitted already.) > >>> D5988 is for tab pager. > >>> > >>> Thank you > >>> > >>> > >>> 네이버 메일 앱에서 보냈습니다. > >>> -Original Message- > >>> 보낸사람: "조재현" > >>> 받는사람: "Enlightenment developer list" < > >>> enlightenment-devel@lists.sourceforge.net> > >>> 날짜: 2018.05.02 오후 08:05:04 > >>> 제목: Re: [E-devel] Heads up on upcoming 1.21 stabilization phase > >>> > >>> 1.21 freeze, there are two patc
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On 09/05/18 11:04, Carsten Haitzler (The Rasterman) wrote: > On Wed, 02 May 2018 16:38:07 + Stephen Houston > said: > > Here's my take. it makes it or it doesn't. Releasing on time is all about > that. > So sure, make a concerted effort, but don't delay if it doesn't make it. We > can > "cut corners" like don't bother doing the colroclass recoloring (requires code > in elm to load/save/edit/configure color class config files, anmd then choose > the right one and apply it). can possibly cut corners on scalability (though > more important than color classes because colors is a preference, scaling is > nercessary, so it'd have to basically scale but we could skip making it scale > "beautifully")... i'm open for suggestions on how and what to cut to make the > timeline... > > I'd just like to say that timed releases is not about big milestones for every > release. It's about a steady flow of updates and improvements small or large, > rather than large gaps. So let's say we do have a "headline feature" this > release, and maybe another the next release. We'll be stuck with none the > release after etc. and so this will be common. Some releases will get big > headline things, some may get multiple, some may get none and just small > changes. It's life with timed releases. :) > The problem with cutting back and taking shortcuts to make the timeline is that inevitably after the release people will get busy on other things and won't get around to going back and fixing all the things that weren't done. So personally I'd go with no shortcuts and if its not done its not done and can wait for the next release. Besides the idea that I'm still not sure about the whole idea of a new theme landing for a efl release, for people using the default theme not even upgrading e and getting a completely different theme seems slightly weird, personally I think it would be better to coordinate it somehow with the e23 release if timing ends up being near right. >> Raster this is more of a question for you. You know my thoughts on theme >> being a pressing issue. Is this something we as the community can band >> together during stabilization and have flat ready to go for 1.21 or is this >> something that we will have to put off yet again for a later release? >> >> My thoughts are that introducing the flat theme could be the headlining pop >> that this 1.21 release needs... i.e. a selling point for the release to be >> more attractive to users other than just being mostly a big fix release >> with just a preview of the interfaces work. So we could say the big >> milestone for the 1.21 release is the new theme and the big milestone for >> 1.22 is interfaces rather than somewhat blandly saying this is a big fix >> release with a tech preview of interfaces and then saying 1.22 has two big >> introductions the theme and interfaces. That would also help with >> stabilization and release process for 1.22 as we wouldn't be having to >> focus on two new large introductions- flat and interfaces in the same >> release. >> >> Just my thoughts here, and obviously not something worth having a knock >> down drag out debate over. >> >> Stephen >> >> On Wed, May 2, 2018, 11:27 AM 조재현 wrote: >> >>> 5908 and D5988. (D6008 has been submitted already.) >>> D5988 is for tab pager. >>> >>> Thank you >>> >>> >>> 네이버 메일 앱에서 보냈습니다. >>> -Original Message- >>> 보낸사람: "조재현" >>> 받는사람: "Enlightenment developer list" < >>> enlightenment-devel@lists.sourceforge.net> >>> 날짜: 2018.05.02 오후 08:05:04 >>> 제목: Re: [E-devel] Heads up on upcoming 1.21 stabilization phase >>> >>> 1.21 freeze, there are two patches to be submitted as follows. >>> >>> https://phab.enlightenment.org/D5908 >>> https://phab.enlightenment.org/D6008 >>> >>> D5908 is for slider widget and D6008 is for tab pager widget in efl ui >>> interface. >>> >>> Those patches are necessary widgets for the new efl ui interface and they >>> are still being updated and also under reviewing. >>> >>> >>> Best regards, >>> Jaehyun Cho. >>> >>> 네이버 메일 앱에서 보냈습니다. >>> -Original Message- >>> 보낸사람: "Stefan Schmidt" >>> 받는사람: "Enlightenment developer list" < >>> enlightenment-devel@lists.sourceforge.net> >>> 날짜: 2018.04.27 오후 08:38:01 >>> 제목: [E-devel] Heads up on upcoming 1.21 stabilization
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On 05/09/2018 03:51 AM, Cedric Bail wrote: On May 8, 2018 12:41 PM, Stefan Schmidt wrote: On 04/27/2018 01:38 PM, Stefan Schmidt wrote: Its been a while. About to get our act together and get everything in place so we can start the 1.21 stabilization phase. We had this brought up at the two IRC meetings we had and I wanted to reach out here as well to understand what pieces people here are working on that need finishing before we can go start stabilization. I know from Cedric that he still has two branches he wants to get merged (a third one was going in already). Supposedly this should happen this week. What else is it that we are working on? If you have something, speak up NOW! There sadly has not been as much progress as hoped for. I still wait for the following items: o Cedric's last branch to be merged (lifecycle?). What is the status here? Maybe its to massive to get landed for 1.21? I have been told it would be merged like 10 days ago. Yes, I have found much more mistake than anticipated and some hack that I didn't know we had. I have fixed all the hack. I am now reviewing all the warning that elementary tests suite is triggering and see if they are genuine or unrelated. I know there is still a problem during shutdown with how focus expect the parent object to always be there during destructor. The branch can already run enlightenment, terminology and the C# bindings fine. I am hoping to land this as soon as possible, but I don't want to rush it either. It is difficult to say how much more work around our inconsistent previous lifecycle I might discover and need to untangle, but hopefully I will be done very soon (a matter of days). The focus stuff is fixed and there are phab revisions for this, which are waiting for your review. A bit more: Not focus is the problem here, the problem is, that composition is setting the parent of the attached object to the object where you are attaching to, thus this attached object *now* is destroyed when the object is invalidated (before destructor). *Before* it was destructed when the destructor chain got to the efl.object class. What this means is, this is not the mistake of the focus code, you changed how the deletion of those objects are working, you have to do basically the same on every object that uses composition, thats efl_net, efl_ui_text, efl_ui_tags, efl_ui_video [...] o https://phab.enlightenment.org/D5908 needs review o https://phab.enlightenment.org/D6046 needs review o Comments on the flat theme from Raster Once we have these sorted we can start with the stabilization phase. As we have no date for this yet I can only give a rough schedule to give people an idea. This needs to be updated once we start with the alpha. === Schedule === Day X Merge window is over. - Only bug fixes from this point - Alpha release tarball - We really need to sort out if we have bigger issues lingering around due to all the last minute rush Day X+14 Beta1 release tarball - Only critical fixes from this point Day X+21 Beta2 release tarball Day X+28 Beta3 release tarball Day X+35 Beta4 release tarball Day X+42 EFL 1.20 is out As you can see I would expect more time for stabilization this time. Its a huge release with many, many changes and some last minute rush. I also expect all the folks brining in the big changes to stand by and fix the bugs introduced. Sounds like a good plan to me. Cedric -- 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 -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On Wed, 02 May 2018 16:38:07 + Stephen Houston said: Here's my take. it makes it or it doesn't. Releasing on time is all about that. So sure, make a concerted effort, but don't delay if it doesn't make it. We can "cut corners" like don't bother doing the colroclass recoloring (requires code in elm to load/save/edit/configure color class config files, anmd then choose the right one and apply it). can possibly cut corners on scalability (though more important than color classes because colors is a preference, scaling is nercessary, so it'd have to basically scale but we could skip making it scale "beautifully")... i'm open for suggestions on how and what to cut to make the timeline... I'd just like to say that timed releases is not about big milestones for every release. It's about a steady flow of updates and improvements small or large, rather than large gaps. So let's say we do have a "headline feature" this release, and maybe another the next release. We'll be stuck with none the release after etc. and so this will be common. Some releases will get big headline things, some may get multiple, some may get none and just small changes. It's life with timed releases. :) > Raster this is more of a question for you. You know my thoughts on theme > being a pressing issue. Is this something we as the community can band > together during stabilization and have flat ready to go for 1.21 or is this > something that we will have to put off yet again for a later release? > > My thoughts are that introducing the flat theme could be the headlining pop > that this 1.21 release needs... i.e. a selling point for the release to be > more attractive to users other than just being mostly a big fix release > with just a preview of the interfaces work. So we could say the big > milestone for the 1.21 release is the new theme and the big milestone for > 1.22 is interfaces rather than somewhat blandly saying this is a big fix > release with a tech preview of interfaces and then saying 1.22 has two big > introductions the theme and interfaces. That would also help with > stabilization and release process for 1.22 as we wouldn't be having to > focus on two new large introductions- flat and interfaces in the same > release. > > Just my thoughts here, and obviously not something worth having a knock > down drag out debate over. > > Stephen > > On Wed, May 2, 2018, 11:27 AM 조재현 wrote: > > > 5908 and D5988. (D6008 has been submitted already.) > > D5988 is for tab pager. > > > > Thank you > > > > > > 네이버 메일 앱에서 보냈습니다. > > -Original Message- > > 보낸사람: "조재현" > > 받는사람: "Enlightenment developer list" < > > enlightenment-devel@lists.sourceforge.net> > > 날짜: 2018.05.02 오후 08:05:04 > > 제목: Re: [E-devel] Heads up on upcoming 1.21 stabilization phase > > > > 1.21 freeze, there are two patches to be submitted as follows. > > > > https://phab.enlightenment.org/D5908 > > https://phab.enlightenment.org/D6008 > > > > D5908 is for slider widget and D6008 is for tab pager widget in efl ui > > interface. > > > > Those patches are necessary widgets for the new efl ui interface and they > > are still being updated and also under reviewing. > > > > > > Best regards, > > Jaehyun Cho. > > > > 네이버 메일 앱에서 보냈습니다. > > -Original Message- > > 보낸사람: "Stefan Schmidt" > > 받는사람: "Enlightenment developer list" < > > enlightenment-devel@lists.sourceforge.net> > > 날짜: 2018.04.27 오후 08:38:01 > > 제목: [E-devel] Heads up on upcoming 1.21 stabilization phase > > > > Hello. > > > > > > Its been a while. About to get our act together and get everything in > > place so we can start the 1.21 stabilization phase. > > > > We had this brought up at the two IRC meetings we had and I wanted to > > reach out here as well to understand what pieces people here are > > working on that need finishing before we can go start stabilization. > > > > I know from Cedric that he still has two branches he wants to get merged > > (a third one was going in already). Supposedly this should happen > > this week. > > > > > > What else is it that we are working on? If you have something, speak up > > NOW! > > > > > > I will look into the situation again on Wednesday next week. Hopefully > > will all items being in and come up with a potential schedule. > > > > Raster agreed to help around this time with some release duties which is > > very much appreciated, especially as I wil
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On Tue, 8 May 2018 21:41:03 +0200 Stefan Schmidt said: > Hello. > > > On 04/27/2018 01:38 PM, Stefan Schmidt wrote: > > Hello. > > > > > > Its been a while. About to get our act together and get everything in place > > so we can start the 1.21 stabilization phase. > > > > We had this brought up at the two IRC meetings we had and I wanted to reach > > out here as well to understand what pieces people here are working on that > > need finishing before we can go start stabilization. > > > > I know from Cedric that he still has two branches he wants to get merged (a > > third one was going in already). Supposedly this should happen this week. > > > > > > What else is it that we are working on? If you have something, speak up NOW! > > > > > > There sadly has not been as much progress as hoped for. > I still wait for the following items: > > o Cedric's last branch to be merged (lifecycle?). What is the status here? > Maybe its to massive to get landed for 1.21? I have been told it would be > merged like 10 days ago. i smell that given the size and nature of this that it may be better postponed, but let's see what happens. > o https://phab.enlightenment.org/D5908 needs review > o https://phab.enlightenment.org/D6046 needs review i am just starting on this. > o Comments on the flat theme from Raster just did that. > Once we have these sorted we can start with the stabilization phase. > As we have no date for this yet I can only give a rough schedule to give > people an idea. This needs to be updated once we start with the alpha. > > === Schedule === > Day X Merge window is over. > * Only bug fixes from this point > * Alpha release tarball > * We really need to sort out if we have bigger issues lingering around due to > all the last minute rush Day X+14 Beta1 release tarball > * Only critical fixes from this point > Day X+21 Beta2 release tarball > Day X+28 Beta3 release tarball > Day X+35 Beta4 release tarball > Day X+42 EFL 1.20 is out > > > As you can see I would expect more time for stabilization this time. Its a > huge release with many, many changes and some last minute rush. I also expect > all the folks brining in the big changes to stand by and fix the bugs > introduced. > > 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 > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On May 8, 2018 12:41 PM, Stefan Schmidt wrote: > On 04/27/2018 01:38 PM, Stefan Schmidt wrote: > > Its been a while. About to get our act together and get everything in place > > so we can start the 1.21 stabilization phase. > > > > We had this brought up at the two IRC meetings we had and I wanted to reach > > out here as well to understand what pieces people here are > > working on that need finishing before we can go start stabilization. > > > > I know from Cedric that he still has two branches he wants to get merged (a > > third one was going in already). Supposedly this should happen > > this week. > > > > What else is it that we are working on? If you have something, speak up NOW! > > There sadly has not been as much progress as hoped for. > I still wait for the following items: > > o Cedric's last branch to be merged (lifecycle?). What is the status here? > Maybe its to massive to get landed for 1.21? I have been told it > would be merged like 10 days ago. Yes, I have found much more mistake than anticipated and some hack that I didn't know we had. I have fixed all the hack. I am now reviewing all the warning that elementary tests suite is triggering and see if they are genuine or unrelated. I know there is still a problem during shutdown with how focus expect the parent object to always be there during destructor. The branch can already run enlightenment, terminology and the C# bindings fine. I am hoping to land this as soon as possible, but I don't want to rush it either. It is difficult to say how much more work around our inconsistent previous lifecycle I might discover and need to untangle, but hopefully I will be done very soon (a matter of days). > o https://phab.enlightenment.org/D5908 needs review > o https://phab.enlightenment.org/D6046 needs review > o Comments on the flat theme from Raster > > Once we have these sorted we can start with the stabilization phase. > As we have no date for this yet I can only give a rough schedule to give > people an idea. > This needs to be updated once we start with the alpha. > > === Schedule === > > Day X Merge window is over. > - Only bug fixes from this point > - Alpha release tarball > - We really need to sort out if we have bigger issues lingering around due > to all the last minute rush > Day X+14 Beta1 release tarball > - Only critical fixes from this point > Day X+21 Beta2 release tarball > Day X+28 Beta3 release tarball > Day X+35 Beta4 release tarball > Day X+42 EFL 1.20 is out > > As you can see I would expect more time for stabilization this time. Its > a huge release with many, many changes and some last minute rush. I also > expect all the folks brining in the big changes to stand by and fix the bugs > introduced. Sounds like a good plan to me. Cedric -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
Hello. On 04/27/2018 01:38 PM, Stefan Schmidt wrote: > Hello. > > > Its been a while. About to get our act together and get everything in place > so we can start the 1.21 stabilization phase. > > We had this brought up at the two IRC meetings we had and I wanted to reach > out here as well to understand what pieces people here are > working on that need finishing before we can go start stabilization. > > I know from Cedric that he still has two branches he wants to get merged (a > third one was going in already). Supposedly this should happen > this week. > > > What else is it that we are working on? If you have something, speak up NOW! > > There sadly has not been as much progress as hoped for. I still wait for the following items: o Cedric's last branch to be merged (lifecycle?). What is the status here? Maybe its to massive to get landed for 1.21? I have been told it would be merged like 10 days ago. o https://phab.enlightenment.org/D5908 needs review o https://phab.enlightenment.org/D6046 needs review o Comments on the flat theme from Raster Once we have these sorted we can start with the stabilization phase. As we have no date for this yet I can only give a rough schedule to give people an idea. This needs to be updated once we start with the alpha. === Schedule === Day X Merge window is over. * Only bug fixes from this point * Alpha release tarball * We really need to sort out if we have bigger issues lingering around due to all the last minute rush Day X+14 Beta1 release tarball * Only critical fixes from this point Day X+21 Beta2 release tarball Day X+28 Beta3 release tarball Day X+35 Beta4 release tarball Day X+42 EFL 1.20 is out As you can see I would expect more time for stabilization this time. Its a huge release with many, many changes and some last minute rush. I also expect all the folks brining in the big changes to stand by and fix the bugs introduced. 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
I found one ABI break issue on elm object item cursor by applying efl ui interface. https://phab.enlightenment.org/D6046 there must be nicer solution then my patch, but I don't want massive fixes would make it unstable. please fallows upon issue also before release. 2018년 5월 3일 (목) 오전 10:30, William L. Thomson Jr. < wlt...@obsidian-studios.com>님이 작성: > On Wed, 02 May 2018 16:38:07 + > Stephen Houston wrote: > > > Raster this is more of a question for you. You know my thoughts on > > theme being a pressing issue. Is this something we as the community > > can band together during stabilization and have flat ready to go for > > 1.21 or is this something that we will have to put off yet again for > > a later release? > > > > My thoughts are that introducing the flat theme could be the > > headlining pop that this 1.21 release needs... i.e. a selling point > > for the release to be more attractive to users other than just being > > mostly a big fix release with just a preview of the interfaces work. > > +1 > > I think there also needs to be some UI to control spacing, colors, etc. > One other thing that would be nice I may have to help code is to be > able to swap position of top window elements, move close, minimize, > maximize, from right to left. > > That is one nice aspect I liked of KDE/Plasma/Kwin. I stopped using > custom themes and just went with modified default via their theme > customization UIs. Allowed me to set the colors I liked, swap location > of title bar elements, etc. Making something along those lines for E. > > That maybe something more for 1.22 than 1.21. With 1.21 having the new > flat theme, and 1.22 having the UI for user styling etc. > > -- > William L. Thomson Jr. > > -- > 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 > -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
On Wed, 02 May 2018 16:38:07 + Stephen Houston wrote: > Raster this is more of a question for you. You know my thoughts on > theme being a pressing issue. Is this something we as the community > can band together during stabilization and have flat ready to go for > 1.21 or is this something that we will have to put off yet again for > a later release? > > My thoughts are that introducing the flat theme could be the > headlining pop that this 1.21 release needs... i.e. a selling point > for the release to be more attractive to users other than just being > mostly a big fix release with just a preview of the interfaces work. +1 I think there also needs to be some UI to control spacing, colors, etc. One other thing that would be nice I may have to help code is to be able to swap position of top window elements, move close, minimize, maximize, from right to left. That is one nice aspect I liked of KDE/Plasma/Kwin. I stopped using custom themes and just went with modified default via their theme customization UIs. Allowed me to set the colors I liked, swap location of title bar elements, etc. Making something along those lines for E. That maybe something more for 1.22 than 1.21. With 1.21 having the new flat theme, and 1.22 having the UI for user styling etc. -- William L. Thomson Jr. pgpL2Hic9LbIO.pgp Description: OpenPGP digital signature -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
Raster this is more of a question for you. You know my thoughts on theme being a pressing issue. Is this something we as the community can band together during stabilization and have flat ready to go for 1.21 or is this something that we will have to put off yet again for a later release? My thoughts are that introducing the flat theme could be the headlining pop that this 1.21 release needs... i.e. a selling point for the release to be more attractive to users other than just being mostly a big fix release with just a preview of the interfaces work. So we could say the big milestone for the 1.21 release is the new theme and the big milestone for 1.22 is interfaces rather than somewhat blandly saying this is a big fix release with a tech preview of interfaces and then saying 1.22 has two big introductions the theme and interfaces. That would also help with stabilization and release process for 1.22 as we wouldn't be having to focus on two new large introductions- flat and interfaces in the same release. Just my thoughts here, and obviously not something worth having a knock down drag out debate over. Stephen On Wed, May 2, 2018, 11:27 AM 조재현 wrote: > 5908 and D5988. (D6008 has been submitted already.) > D5988 is for tab pager. > > Thank you > > > 네이버 메일 앱에서 보냈습니다. > -Original Message- > 보낸사람: "조재현" > 받는사람: "Enlightenment developer list" < > enlightenment-devel@lists.sourceforge.net> > 날짜: 2018.05.02 오후 08:05:04 > 제목: Re: [E-devel] Heads up on upcoming 1.21 stabilization phase > > 1.21 freeze, there are two patches to be submitted as follows. > > https://phab.enlightenment.org/D5908 > https://phab.enlightenment.org/D6008 > > D5908 is for slider widget and D6008 is for tab pager widget in efl ui > interface. > > Those patches are necessary widgets for the new efl ui interface and they > are still being updated and also under reviewing. > > > Best regards, > Jaehyun Cho. > > 네이버 메일 앱에서 보냈습니다. > -Original Message- > 보낸사람: "Stefan Schmidt" > 받는사람: "Enlightenment developer list" < > enlightenment-devel@lists.sourceforge.net> > 날짜: 2018.04.27 오후 08:38:01 > 제목: [E-devel] Heads up on upcoming 1.21 stabilization phase > > Hello. > > > Its been a while. About to get our act together and get everything in > place so we can start the 1.21 stabilization phase. > > We had this brought up at the two IRC meetings we had and I wanted to > reach out here as well to understand what pieces people here are > working on that need finishing before we can go start stabilization. > > I know from Cedric that he still has two branches he wants to get merged > (a third one was going in already). Supposedly this should happen > this week. > > > What else is it that we are working on? If you have something, speak up > NOW! > > > I will look into the situation again on Wednesday next week. Hopefully > will all items being in and come up with a potential schedule. > > Raster agreed to help around this time with some release duties which is > very much appreciated, especially as I will be away the whole June. > > > From 1.22 I would suggest a round robin change of release manager duties. > This should a) help to reduce the pain doing it and b) spread the > knowledge throughout the developer team. > > > 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 > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > -- > 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 > > -- > 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 > -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
5908 and D5988. (D6008 has been submitted already.) D5988 is for tab pager. Thank you 네이버 메일 앱에서 보냈습니다. -Original Message- 보낸사람: "조재현" 받는사람: "Enlightenment developer list" 날짜: 2018.05.02 오후 08:05:04 제목: Re: [E-devel] Heads up on upcoming 1.21 stabilization phase 1.21 freeze, there are two patches to be submitted as follows. https://phab.enlightenment.org/D5908 https://phab.enlightenment.org/D6008 D5908 is for slider widget and D6008 is for tab pager widget in efl ui interface. Those patches are necessary widgets for the new efl ui interface and they are still being updated and also under reviewing. Best regards, Jaehyun Cho. 네이버 메일 앱에서 보냈습니다. -Original Message- 보낸사람: "Stefan Schmidt" 받는사람: "Enlightenment developer list" 날짜: 2018.04.27 오후 08:38:01 제목: [E-devel] Heads up on upcoming 1.21 stabilization phase Hello. Its been a while. About to get our act together and get everything in place so we can start the 1.21 stabilization phase. We had this brought up at the two IRC meetings we had and I wanted to reach out here as well to understand what pieces people here are working on that need finishing before we can go start stabilization. I know from Cedric that he still has two branches he wants to get merged (a third one was going in already). Supposedly this should happen this week. What else is it that we are working on? If you have something, speak up NOW! I will look into the situation again on Wednesday next week. Hopefully will all items being in and come up with a potential schedule. Raster agreed to help around this time with some release duties which is very much appreciated, especially as I will be away the whole June. From 1.22 I would suggest a round robin change of release manager duties. This should a) help to reduce the pain doing it and b) spread the knowledge throughout the developer team. 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- 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 -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
1.21 freeze, there are two patches to be submitted as follows. https://phab.enlightenment.org/D5908 https://phab.enlightenment.org/D6008 D5908 is for slider widget and D6008 is for tab pager widget in efl ui interface. Those patches are necessary widgets for the new efl ui interface and they are still being updated and also under reviewing. Best regards, Jaehyun Cho. 네이버 메일 앱에서 보냈습니다. -Original Message- 보낸사람: "Stefan Schmidt" 받는사람: "Enlightenment developer list" 날짜: 2018.04.27 오후 08:38:01 제목: [E-devel] Heads up on upcoming 1.21 stabilization phase Hello. Its been a while. About to get our act together and get everything in place so we can start the 1.21 stabilization phase. We had this brought up at the two IRC meetings we had and I wanted to reach out here as well to understand what pieces people here are working on that need finishing before we can go start stabilization. I know from Cedric that he still has two branches he wants to get merged (a third one was going in already). Supposedly this should happen this week. What else is it that we are working on? If you have something, speak up NOW! I will look into the situation again on Wednesday next week. Hopefully will all items being in and come up with a potential schedule. Raster agreed to help around this time with some release duties which is very much appreciated, especially as I will be away the whole June. From 1.22 I would suggest a round robin change of release manager duties. This should a) help to reduce the pain doing it and b) spread the knowledge throughout the developer team. 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- 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
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
Hello Sanghyeon. On 04/27/2018 03:07 PM, SangHyeon Lee wrote: > hello. > > About the release plan... > my patch D5861 is planned to be submitted before the 1.22 release. > https://phab.enlightenment.org/D5861 > > This is about new efl.ui.list for interface and I supposed it ready for > landing but only wait for cedric's final confirm. > l've test multiple times with test and example builds and there are no > problem detect as fat as I see, but if there are something wrong on your > view, please let me know. I'll fix it ASAP. Thanks for letting me know. I added this to the list of items that need to land before we start the stabilization. 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 enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Heads up on upcoming 1.21 stabilization phase
hello. About the release plan... my patch D5861 is planned to be submitted before the 1.22 release. https://phab.enlightenment.org/D5861 This is about new efl.ui.list for interface and I supposed it ready for landing but only wait for cedric's final confirm. l've test multiple times with test and example builds and there are no problem detect as fat as I see, but if there are something wrong on your view, please let me know. I'll fix it ASAP. @cedric can you final confirm on my efl.ui.list patch? thank you all. Best Regards, Sanghyeon Jade Lee 2018년 4월 27일 (금) 오후 8:38, Stefan Schmidt 님이 작성: > Hello. > > > Its been a while. About to get our act together and get everything in > place so we can start the 1.21 stabilization phase. > > We had this brought up at the two IRC meetings we had and I wanted to > reach out here as well to understand what pieces people here are > working on that need finishing before we can go start stabilization. > > I know from Cedric that he still has two branches he wants to get merged > (a third one was going in already). Supposedly this should happen > this week. > > > What else is it that we are working on? If you have something, speak up > NOW! > > > I will look into the situation again on Wednesday next week. Hopefully > will all items being in and come up with a potential schedule. > > Raster agreed to help around this time with some release duties which is > very much appreciated, especially as I will be away the whole June. > > > From 1.22 I would suggest a round robin change of release manager duties. > This should a) help to reduce the pain doing it and b) spread the > knowledge throughout the developer team. > > > 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 > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- 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
