Re: [E-devel] Temp github repository, was: phab down ?
So, You can find the repository at: https://github.com/Enlightenment/efl-tmp Once the efl infra is back on track, we can continue to work there, until there, we *can* work there. If someone wants to have access, and has access to e.org, please contact me, i can add your github account to the repository. - CI is enabled on that repository - Issues are disabled as they will be a pain to sync up later - Please use PRs if you want to propose any changes. Once e.org is back, I (or anyone else) will merge the difference of the master onto the efl.git repo, if there are new commits in that time on the efl.git repo we can rebase the github master ontop of it. PRs must be re-added by the author which seems easy enough. Greetings, bu5hm4n On 2/19/19 4:48 PM, Carsten Haitzler (The Rasterman) wrote: > On Tue, 19 Feb 2019 10:59:16 +0100 Marcel Hollerbach said: > >> >> >> On 2/19/19 10:52 AM, Carsten Haitzler (The Rasterman) wrote: >>> On Tue, 19 Feb 2019 09:16:13 +0100 Marcel Hollerbach said: >>> Due to the fact that we don't know how long this will stay, what do you think that we just use github for the time our infra is down ? We already have efl there, and can just fork another time, I can add the github accounts of the people that want to merge something. For the time being on github we can use PRs, when e.org is back up, the authors can migrate back to phab. However, i would not do that with the issues as this is annoying to migrate. This would at least enable us to move forward, and not have complete grinding halt. >>> >>> waiting on beber. i mailed him about 24h ago already. i can't do anything - >>> don't have access (the host machine doesn't allow me in and the vm's are not >>> responding to ssh). it's in beber's hands at this point. he may be busy. not >>> sure. >>> >> >> Sure, my reply was not meant as blame or anything, rather just as an tmp >> solution, so we can move on ... (we are heading towards an release) :) > > not a blame - it's just current status so everyone knows that we know, the > info > has been passed on and we're waiting on that. > Greetings, bu5hm4n On 2/18/19 6:55 PM, Davide Andreoli wrote: > Also the website is down from at least 10 hours > > Il giorno lun 18 feb 2019 alle ore 07:59 Vincent Torri < > vincent.to...@gmail.com> ha scritto: > >> hello >> >> i can't use arc diff and when loading a phab diff, i get an error >> >> Vincent >> >> >> ___ >> enlightenment-devel mailing list >> enlightenment-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > >>> >>> > > pEpkey.asc Description: application/pgp-keys ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] phab down ?
On Tue, 19 Feb 2019 10:59:16 +0100 Marcel Hollerbach said: > > > On 2/19/19 10:52 AM, Carsten Haitzler (The Rasterman) wrote: > > On Tue, 19 Feb 2019 09:16:13 +0100 Marcel Hollerbach said: > > > >> Due to the fact that we don't know how long this will stay, > >> what do you think that we just use github for the time our infra is down > >> ? We already have efl there, and can just fork another time, I can add > >> the github accounts of the people that want to merge something. For the > >> time being on github we can use PRs, when e.org is back up, the authors > >> can migrate back to phab. However, i would not do that with the issues > >> as this is annoying to migrate. > >> This would at least enable us to move forward, and not have complete > >> grinding halt. > > > > waiting on beber. i mailed him about 24h ago already. i can't do anything - > > don't have access (the host machine doesn't allow me in and the vm's are not > > responding to ssh). it's in beber's hands at this point. he may be busy. not > > sure. > > > > Sure, my reply was not meant as blame or anything, rather just as an tmp > solution, so we can move on ... (we are heading towards an release) :) not a blame - it's just current status so everyone knows that we know, the info has been passed on and we're waiting on that. > >> Greetings, > >>bu5hm4n > >> > >> On 2/18/19 6:55 PM, Davide Andreoli wrote: > >>> Also the website is down from at least 10 hours > >>> > >>> Il giorno lun 18 feb 2019 alle ore 07:59 Vincent Torri < > >>> vincent.to...@gmail.com> ha scritto: > >>> > hello > > i can't use arc diff and when loading a phab diff, i get an error > > Vincent > > > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > >>> > >>> ___ > >>> 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 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] 1.22 schedule proposal - updated
On 19/02/2019 18:52, Stefan Schmidt wrote: > Hello. > > On 18.02.19 07:07, Jonathan Aquilina wrote: >> Morning Simon, >> >> What I am thinking is the master branch would have the weekly releases for >> developers and stable releases would be once a month. > > No, sorry. I don't think that makes sense. We don't need a tarball > packaged from git without any extra work. People who want bleeding edge > stay on git. If we would provide snapshots people would expect some > extra testing on them which would simply not happen. > >> What do you think about this? > > I think we should stick with what we talked about and not mix in other > things every day. > > 1) Try a 5 months release schedule to see if that works better and lifts > some pressure form the 3 months cycle. > > 2) For stable updates we will have a cron job running that checks every > Monday if there are new patches in the stable branches compared to the > last stable update. If there are we trigger the process to do a new release. > Checking every Monday is fine but my original point was potentially having point releases every week won't be that useful because as packagers we are likely not going to want to put through an update once a week. In my opinion something like this would work better Check Every Monday: If a Serious / Critical / showstopper bug has been fixed -> Release If more then X fixes haven't been released yet -> Release (Lets call X 10 for now) If the oldest fix has been waiting 4 or more weeks -> Release Otherwise reassess the following week. This way Important fixes get out quickly but people don't start ignoring releases because the last 3 releases have just had one minor fix for something they don't care about. If point releases were just weekly if we have a commit over a 5 month release cycle we could easily get between 10-20 point releases which in my opinion is too much. Cheers -- Simon Lees (Simotek)http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] phab down ?
On 2/19/19 10:52 AM, Carsten Haitzler (The Rasterman) wrote: > On Tue, 19 Feb 2019 09:16:13 +0100 Marcel Hollerbach said: > >> Due to the fact that we don't know how long this will stay, >> what do you think that we just use github for the time our infra is down >> ? We already have efl there, and can just fork another time, I can add >> the github accounts of the people that want to merge something. For the >> time being on github we can use PRs, when e.org is back up, the authors >> can migrate back to phab. However, i would not do that with the issues >> as this is annoying to migrate. >> This would at least enable us to move forward, and not have complete >> grinding halt. > > waiting on beber. i mailed him about 24h ago already. i can't do anything - > don't have access (the host machine doesn't allow me in and the vm's are not > responding to ssh). it's in beber's hands at this point. he may be busy. not > sure. > Sure, my reply was not meant as blame or anything, rather just as an tmp solution, so we can move on ... (we are heading towards an release) :) >> Greetings, >>bu5hm4n >> >> On 2/18/19 6:55 PM, Davide Andreoli wrote: >>> Also the website is down from at least 10 hours >>> >>> Il giorno lun 18 feb 2019 alle ore 07:59 Vincent Torri < >>> vincent.to...@gmail.com> ha scritto: >>> hello i can't use arc diff and when loading a phab diff, i get an error Vincent ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >>> >>> ___ >>> enlightenment-devel mailing list >>> enlightenment-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >>> > > pEpkey.asc Description: application/pgp-keys ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] phab down ?
On Tue, 19 Feb 2019 09:16:13 +0100 Marcel Hollerbach said: > Due to the fact that we don't know how long this will stay, > what do you think that we just use github for the time our infra is down > ? We already have efl there, and can just fork another time, I can add > the github accounts of the people that want to merge something. For the > time being on github we can use PRs, when e.org is back up, the authors > can migrate back to phab. However, i would not do that with the issues > as this is annoying to migrate. > This would at least enable us to move forward, and not have complete > grinding halt. waiting on beber. i mailed him about 24h ago already. i can't do anything - don't have access (the host machine doesn't allow me in and the vm's are not responding to ssh). it's in beber's hands at this point. he may be busy. not sure. > Greetings, >bu5hm4n > > On 2/18/19 6:55 PM, Davide Andreoli wrote: > > Also the website is down from at least 10 hours > > > > Il giorno lun 18 feb 2019 alle ore 07:59 Vincent Torri < > > vincent.to...@gmail.com> ha scritto: > > > >> hello > >> > >> i can't use arc diff and when loading a phab diff, i get an error > >> > >> Vincent > >> > >> > >> ___ > >> enlightenment-devel mailing list > >> enlightenment-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > >> > > > > ___ > > 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 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] 1.22 schedule proposal - updated
Hi Stefan, Sorry about the changes to the plan that wasn’t my intention. I am in complete agreement with you on the below points. When ever you are ready with the script let me know and we can get things going with the infrastructure with a linode I have and at least get the release out and running. Regards, Jonathan On 19/02/2019, 09:23, "Stefan Schmidt" wrote: Hello. On 18.02.19 07:07, Jonathan Aquilina wrote: > Morning Simon, > > What I am thinking is the master branch would have the weekly releases for developers and stable releases would be once a month. No, sorry. I don't think that makes sense. We don't need a tarball packaged from git without any extra work. People who want bleeding edge stay on git. If we would provide snapshots people would expect some extra testing on them which would simply not happen. > What do you think about this? I think we should stick with what we talked about and not mix in other things every day. 1) Try a 5 months release schedule to see if that works better and lifts some pressure form the 3 months cycle. 2) For stable updates we will have a cron job running that checks every Monday if there are new patches in the stable branches compared to the last stable update. If there are we trigger the process to do a new release. In practice that would mean we do it really "on-demand", as in, some fix was seen worthwhile backporting. I would imagine that will give us weekly updates for the first few weeks after a major release and after that only occasionally an update. regards Stefan Schmidt ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Goodbye
Hey Derek, Wishing you all the best in the future. As with everyone else, thanks for all the work you have done. On Tue, Feb 19, 2019 at 6:04 AM cnook wrote: > Hey I am sorry for losing chance working with you any more. I have loved > your elegant words and lines in the EFL world. Thank you for having that > kind of delight. I hope you find your own great way leading to happiness. > Good luck and God bless you! > > Sincerely > Shinwoo Kim > > > > 2019년 2월 19일 (화) 오전 11:25에 Hermet Park 님이 작성: > > > Derek, > > > > Though it's shame that your're leaving the community, > > But I believe you have a better opportunity for your way. > > > > Thanks for your huge contribution for years. > > > > Good Luck! > > > > Best Regards, > > > > On Sat, Feb 16, 2019 at 12:48 AM Stephen Houston > > wrote: > > > > > Thank you for all of your valuable contributions. It was a privilege > to > > > work with you and get to know you. Best of luck in your future > > endeavors! > > > > > > Stephen > > > > > > On Thu, Feb 14, 2019 at 10:00 PM Derek Foreman < > > > derek.foreman.sams...@gmail.com> wrote: > > > > > > > As some of you already know, today is my last day working for > Samsung, > > > and > > > > I no longer have a financial incentive to contribute to EFL. > > > > > > > > One of my primary reasons for leaving this position is that it was > tied > > > to > > > > a continued requirement to work on EFL, and I've grown weary of doing > > > that, > > > > so I won't be lingering as a community developer. > > > > > > > > Over the years there have been times when I've felt EFL was on the > cusp > > > of > > > > outgrowing its hobby project roots and making a shift towards > grown-up > > > > standards (incorporating peer review, CI, a push for better > > > documentation), > > > > followed by events that felt like major setbacks on that path. Some > > days > > > > it felt like we were reducing the insurmountable mountain of > technical > > > > debt, and other days hopelessly watching it increase. > > > > > > > > EFL is currently in a situation where leadership is frequently at > odds > > > with > > > > the majority of contributors, and this leads to developers finding > > > > themselves worrying that work they've been paid to do (and maybe > > > sometimes > > > > have even done well) will be unilaterally reverted, possibly with > > threats > > > > of commit right revocation. This makes contributing pointlessly > > > stressful, > > > > and drives developers away. > > > > > > > > I hope I've left my small corners of the project a little better > than I > > > > found them, and I thank you all for an opportunity to contribute. > I've > > > met > > > > some excellent people in my time here, and hope to keep in touch. > I'll > > > > still be around on all the regular IRC servers, feel free to contact > > me*. > > > > > > > > Best of luck, > > > > Derek > > > > > > > > * Just not about EFL. Ever. Seriously. > > > > > > > > ___ > > > > enlightenment-devel mailing list > > > > enlightenment-devel@lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > > > > > > ___ > > > enlightenment-devel mailing list > > > enlightenment-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > > > > > -- > > Regards, Hermet > > > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] 1.22 schedule proposal - updated
Hello. On 16.02.19 00:37, Simon Lees wrote: > > > On 16/02/2019 02:07, Stefan Schmidt wrote: >> Hello. >> >> We pushed back on the initial schedule to not get everyone caught by >> surprise of a freeze. >> >> We had some extra weeks now and I wonder if the following updated >> schedule would work? >> >> === Schedule === >> 2018-08-17 Merge window for 1.22 opens >> 2019-02-20 Notice about soon ending merge window >> 2019-02-28 Merge window is over. Freeze in place. >> * Only bug fixes from this point >> * Alpha release tarball >> * One month stabilization phase starts >> 2019-03-07 Beta1 release tarball >> * Only critical fixes from this point >> 2019-03-14 Beta2 release tarball >> 2019-03-21 EFL 1.22 is out >> >> As a sidenote I would consider this the last release with autotools. We >> will also have a meson based tarball ready at that point which we would >> appreciate testing from packagers. After the release is out we should >> remove autotools support from master to focus on one build system only. >> Autotools will only be kept use in the 1.22.x releases for maintenance. >> > > Id be happy to test a meson tarball whenever there is one available. Perfect. I will try that we have some with the alpha and beta releases for 1.22. regards Stefan Schmidt ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] 1.22 schedule proposal - updated
Hello. On 18.02.19 07:07, Jonathan Aquilina wrote: > Morning Simon, > > What I am thinking is the master branch would have the weekly releases for > developers and stable releases would be once a month. No, sorry. I don't think that makes sense. We don't need a tarball packaged from git without any extra work. People who want bleeding edge stay on git. If we would provide snapshots people would expect some extra testing on them which would simply not happen. > What do you think about this? I think we should stick with what we talked about and not mix in other things every day. 1) Try a 5 months release schedule to see if that works better and lifts some pressure form the 3 months cycle. 2) For stable updates we will have a cron job running that checks every Monday if there are new patches in the stable branches compared to the last stable update. If there are we trigger the process to do a new release. In practice that would mean we do it really "on-demand", as in, some fix was seen worthwhile backporting. I would imagine that will give us weekly updates for the first few weeks after a major release and after that only occasionally an update. regards Stefan Schmidt ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] 1.22 schedule proposal - updated
Hello. On 16.02.19 05:03, Jonathan Aquilina wrote: > Hi Stefan, > > I thought you were making a few changes to it given we are doing 5 month > major releases and then weekly point releases. There is nothing in the script that would encode the release schedule. regards Stefan Schmidt ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] phab down ?
Due to the fact that we don't know how long this will stay, what do you think that we just use github for the time our infra is down ? We already have efl there, and can just fork another time, I can add the github accounts of the people that want to merge something. For the time being on github we can use PRs, when e.org is back up, the authors can migrate back to phab. However, i would not do that with the issues as this is annoying to migrate. This would at least enable us to move forward, and not have complete grinding halt. Greetings, bu5hm4n On 2/18/19 6:55 PM, Davide Andreoli wrote: > Also the website is down from at least 10 hours > > Il giorno lun 18 feb 2019 alle ore 07:59 Vincent Torri < > vincent.to...@gmail.com> ha scritto: > >> hello >> >> i can't use arc diff and when loading a phab diff, i get an error >> >> Vincent >> >> >> ___ >> enlightenment-devel mailing list >> enlightenment-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > pEpkey.asc Description: application/pgp-keys ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
