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] 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] 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] 1.22 schedule proposal - updated
On Mon, 18 Feb 2019 09:15:06 + Jonathan Aquilina said: > Hi Raster, > > What about those end users that might want more bleeding edge stuff to test > etc? Currently how often are new tarballs generated prior to a stable release? git master. why do they need bleeding edge tarballs? > Regards, > Jonathan > > On 18/02/2019, 09:34, "Carsten Haitzler" wrote: > > On Mon, 18 Feb 2019 06:07:18 + Jonathan Aquilina > said: > > > 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. > > why weekly releases? that's not going to have any release PROCESS done > other than "make distcheck" or "ninja dist" - i don't see any stabilization > work or QA being done beyond that (it won't be sustainable at that rate > without basically no QA). at that point we have git master itself - so anyone > interested in such things can just use git master. > > > What do you think about this? > > > > Regards, > > Jonathan > > > > -Original Message- > > From: Simon Lees > > Sent: 17 February 2019 23:16 > > To: enlightenment-devel@lists.sourceforge.net > > Subject: Re: [E-devel] 1.22 schedule proposal - updated > > > > > > > > On 16/02/2019 20:24, Jonathan Aquilina wrote: > > > Hi Simon, > > > > > > My idea for that is more for developers to have more frequent > > > snapshots granted there is the repository that one can pull from but > > > that will always be the latest commits you will be pulling from the > > > repo. > > > > > But these snapshots would be different, most developers are following > > the master branch rather then the 1.22 branch that we use for doing > > point releases > > > > -- > > > > 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 > > > > > -- > - Codito, ergo sum - "I code, therefore I am" -- > Carsten Haitzler - ras...@rasterman.com > > > -- - 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 18/02/2019 19:45, Jonathan Aquilina wrote: > Hi Raster, > > What about those end users that might want more bleeding edge stuff to test > etc? Currently how often are new tarballs generated prior to a stable release? > > Regards, > Jonathan Regularly once we get to the Alpha / Beta stage but they are tagged as 1.22.0-alpha1 / 1.22.0- beta1, before 1.22.0 is released. Theyll generally be once a week leading upto the next release. But we haven't done them during the development period as they won't be anymore stable then just running git master which for regularly updating users is easier anyway. -- 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 signature.asc Description: OpenPGP digital signature ___ 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 Raster, What about those end users that might want more bleeding edge stuff to test etc? Currently how often are new tarballs generated prior to a stable release? Regards, Jonathan On 18/02/2019, 09:34, "Carsten Haitzler" wrote: On Mon, 18 Feb 2019 06:07:18 + Jonathan Aquilina said: > 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. why weekly releases? that's not going to have any release PROCESS done other than "make distcheck" or "ninja dist" - i don't see any stabilization work or QA being done beyond that (it won't be sustainable at that rate without basically no QA). at that point we have git master itself - so anyone interested in such things can just use git master. > What do you think about this? > > Regards, > Jonathan > > -Original Message- > From: Simon Lees > Sent: 17 February 2019 23:16 > To: enlightenment-devel@lists.sourceforge.net > Subject: Re: [E-devel] 1.22 schedule proposal - updated > > > > On 16/02/2019 20:24, Jonathan Aquilina wrote: > > Hi Simon, > > > > My idea for that is more for developers to have more frequent snapshots > > granted there is the repository that one can pull from but that will always > > be the latest commits you will be pulling from the repo. > > > But these snapshots would be different, most developers are following the > master branch rather then the 1.22 branch that we use for doing point releases > > -- > > 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 > -- - 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 Mon, 18 Feb 2019 06:07:18 + Jonathan Aquilina said: > 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. why weekly releases? that's not going to have any release PROCESS done other than "make distcheck" or "ninja dist" - i don't see any stabilization work or QA being done beyond that (it won't be sustainable at that rate without basically no QA). at that point we have git master itself - so anyone interested in such things can just use git master. > What do you think about this? > > Regards, > Jonathan > > -Original Message- > From: Simon Lees > Sent: 17 February 2019 23:16 > To: enlightenment-devel@lists.sourceforge.net > Subject: Re: [E-devel] 1.22 schedule proposal - updated > > > > On 16/02/2019 20:24, Jonathan Aquilina wrote: > > Hi Simon, > > > > My idea for that is more for developers to have more frequent snapshots > > granted there is the repository that one can pull from but that will always > > be the latest commits you will be pulling from the repo. > > > But these snapshots would be different, most developers are following the > master branch rather then the 1.22 branch that we use for doing point releases > > -- > > 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 > -- - 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 Mon, 18 Feb 2019 08:46:29 +1030 Simon Lees said: > > > On 16/02/2019 20:24, Jonathan Aquilina wrote: > > Hi Simon, > > > > My idea for that is more for developers to have more frequent snapshots > > granted there is the repository that one can pull from but that will always > > be the latest commits you will be pulling from the repo. > > > But these snapshots would be different, most developers are following > the master branch rather then the 1.22 branch that we use for doing > point releases which means it's better to do more frequent minor releases rather than micro bug-fix releases. (it's more in-line with what is being actually tested and run by developers day to day). having a trimmed down release process would be needed for that to happen though. -- - 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
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. What do you think about this? Regards, Jonathan -Original Message- From: Simon Lees Sent: 17 February 2019 23:16 To: enlightenment-devel@lists.sourceforge.net Subject: Re: [E-devel] 1.22 schedule proposal - updated On 16/02/2019 20:24, Jonathan Aquilina wrote: > Hi Simon, > > My idea for that is more for developers to have more frequent snapshots > granted there is the repository that one can pull from but that will always > be the latest commits you will be pulling from the repo. > But these snapshots would be different, most developers are following the master branch rather then the 1.22 branch that we use for doing point releases -- 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] 1.22 schedule proposal - updated
On 16/02/2019 20:24, Jonathan Aquilina wrote: > Hi Simon, > > My idea for that is more for developers to have more frequent snapshots > granted there is the repository that one can pull from but that will always > be the latest commits you will be pulling from the repo. > But these snapshots would be different, most developers are following the master branch rather then the 1.22 branch that we use for doing point releases -- 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 signature.asc Description: OpenPGP digital signature ___ 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 Simon, My idea for that is more for developers to have more frequent snapshots granted there is the repository that one can pull from but that will always be the latest commits you will be pulling from the repo. -Original Message- From: Simon Lees Sent: 16 February 2019 10:52 To: enlightenment-devel@lists.sourceforge.net Subject: Re: [E-devel] 1.22 schedule proposal - updated On 16/02/2019 14:33, 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. > > Regards, > Jonathan. > Personally I think Monthly point releases are probably more then enough unless we find a major issue. Distro's who are the major users of them probably won't update once a week, I'd also expect that once a release settles we probably wouldn't even see new commits once a week. -- 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] 1.22 schedule proposal - updated
On 16/02/2019 14:33, 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. > > Regards, > Jonathan. > Personally I think Monthly point releases are probably more then enough unless we find a major issue. Distro's who are the major users of them probably won't update once a week, I'd also expect that once a release settles we probably wouldn't even see new commits once a week. -- 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 signature.asc Description: OpenPGP digital signature ___ 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, I thought you were making a few changes to it given we are doing 5 month major releases and then weekly point releases. Regards, Jonathan. -Original Message- From: Stefan Schmidt Sent: 15 February 2019 19:56 To: enlightenment-devel@lists.sourceforge.net Subject: Re: [E-devel] 1.22 schedule proposal - updated Hello Jonathan. On 15.02.19 16:41, Jonathan Aquilina wrote: > Hi Stefan, > > Not to derail the below in terms of the scripts that will be used to generate > the release do you have an ETA for these scripts or will it be sometime next > week? Not sure what you are talking about here. It will be the same release script I used all the time. I pointed you several times to it. Last time when we had or IRC chat. regards Stefan Schmidt > -Original Message- > From: Stefan Schmidt > Sent: 15 February 2019 16:37 > To: enlightenment-devel@lists.sourceforge.net > Subject: Re: [E-devel] 1.22 schedule proposal - updated > > 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. > > If this schedule does not work for you for a good reason speak up now. > > 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 > ___ 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
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. -- 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 signature.asc Description: OpenPGP digital signature ___ 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 Jonathan. On 15.02.19 16:41, Jonathan Aquilina wrote: > Hi Stefan, > > Not to derail the below in terms of the scripts that will be used to generate > the release do you have an ETA for these scripts or will it be sometime next > week? Not sure what you are talking about here. It will be the same release script I used all the time. I pointed you several times to it. Last time when we had or IRC chat. regards Stefan Schmidt > -Original Message- > From: Stefan Schmidt > Sent: 15 February 2019 16:37 > To: enlightenment-devel@lists.sourceforge.net > Subject: Re: [E-devel] 1.22 schedule proposal - updated > > 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. > > If this schedule does not work for you for a good reason speak up now. > > 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 > ___ 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, Not to derail the below in terms of the scripts that will be used to generate the release do you have an ETA for these scripts or will it be sometime next week? -Original Message- From: Stefan Schmidt Sent: 15 February 2019 16:37 To: enlightenment-devel@lists.sourceforge.net Subject: Re: [E-devel] 1.22 schedule proposal - updated 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. If this schedule does not work for you for a good reason speak up now. 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] 1.22 schedule proposal - updated
On Fri, 15 Feb 2019 16:37:06 +0100 Stefan Schmidt said: i think that sounds sensible. > 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. > > If this schedule does not work for you for a good reason speak up now. > > regards > Stefan Schmidt > > > ___ > 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
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. If this schedule does not work for you for a good reason speak up now. 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
Hi Stefan,
Are you available Sunday evening by any chance?
Regards,
Jonathan
On 08/02/2019, 09:34, "Stefan Schmidt" wrote:
Hello.
On 06.02.19 15:33, Jonathan Aquilina wrote:
> I just landed a new job which I start on Monday but I am willing to help
and take over this. I am sure a lot more can be automated for sure.
Have you looked at the wiki page and scripts used for release handling?
Much of the mechanical work of building the tarball and pushing it out
is already scripted. Sure it could get cleaned up and maybe made more
robust, but its there.
What could be further automated is the news generation and addtition to
the wiki, sending out release mails, etc. Could all be done but it never
urged me enough to spend time on it.
>
> I think best place to get this rolling would be to do a conference call
or a chat on slack.
Slack or IRC. What day and time would you prefer?
regards
Stefan Schmidt
> -Original Message-
> From: Stefan Schmidt
> Sent: 06 February 2019 13:56
> To: enlightenment-devel@lists.sourceforge.net; Jonathan Aquilina
> Subject: Re: [E-devel] 1.22 schedule proposal
>
> Hello Jonathan.
>
> On 09.01.19 16:26, Jonathan Aquilina wrote:
>> I'm ready to step and take charge of this but I think we need a bit more
frequent minor release updates both for those in the community that want to Be
on the bleeding edge and those that want to help bug fix more incremental
stable releases.
>
> So, a 1.21.2. We currently have 4 patches pending in the 1.21.x branch
which are not in the 1.21.1 release. When announced that there will be a stable
update we might see more backports coming.
>
>> Stefan do you have any documentation on how release plan works?
>
> I posted this very link to you a couple of times, but I had no feedback
from you if that covers what you asked for.
>
> https://phab.enlightenment.org/w/release_procedure/
>
> Jonathan, are you willing top work on a 1.21.2 stable release?
> I can give you a hand but I would need to know if you are willing, have
the time and the bandwidth to do this.
>
> 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
Hi Stefan, 22:00 is perfect for me we can have a chat on slack regarding this and Azure CI side of things. Thank god for being in the same time zone makes things like this much easier to coordinate. Regards, Jonathan On 08/02/2019, 09:47, "Stefan Schmidt" wrote: Hello. On 08.02.19 09:35, Jonathan Aquilina wrote: > Hi Stefan, > > Are you available Sunday evening by any chance? Sunday is family day. I can offer you something before I go to bed: https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=2&day=10&hour=21&min=0&sec=0&p1=37 22:00 CET timezone. regards Stefan Schmidt > Regards, > Jonathan > > On 08/02/2019, 09:34, "Stefan Schmidt" wrote: > > Hello. > > On 06.02.19 15:33, Jonathan Aquilina wrote: > > I just landed a new job which I start on Monday but I am willing to help and take over this. I am sure a lot more can be automated for sure. > > Have you looked at the wiki page and scripts used for release handling? > Much of the mechanical work of building the tarball and pushing it out > is already scripted. Sure it could get cleaned up and maybe made more > robust, but its there. > > What could be further automated is the news generation and addtition to > the wiki, sending out release mails, etc. Could all be done but it never > urged me enough to spend time on it. > > > > > I think best place to get this rolling would be to do a conference call or a chat on slack. > > Slack or IRC. What day and time would you prefer? > > regards > Stefan Schmidt > > > -Original Message- > > From: Stefan Schmidt > > Sent: 06 February 2019 13:56 > > To: enlightenment-devel@lists.sourceforge.net; Jonathan Aquilina > > Subject: Re: [E-devel] 1.22 schedule proposal > > > > Hello Jonathan. > > > > On 09.01.19 16:26, Jonathan Aquilina wrote: > >> I'm ready to step and take charge of this but I think we need a bit more frequent minor release updates both for those in the community that want to Be on the bleeding edge and those that want to help bug fix more incremental stable releases. > > > > So, a 1.21.2. We currently have 4 patches pending in the 1.21.x branch which are not in the 1.21.1 release. When announced that there will be a stable update we might see more backports coming. > > > >> Stefan do you have any documentation on how release plan works? > > > > I posted this very link to you a couple of times, but I had no feedback from you if that covers what you asked for. > > > > https://phab.enlightenment.org/w/release_procedure/ > > > > Jonathan, are you willing top work on a 1.21.2 stable release? > > I can give you a hand but I would need to know if you are willing, have the time and the bandwidth to do this. > > > > 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
Hello. On 08.02.19 09:35, Jonathan Aquilina wrote: > Hi Stefan, > > Are you available Sunday evening by any chance? Sunday is family day. I can offer you something before I go to bed: https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=2&day=10&hour=21&min=0&sec=0&p1=37 22:00 CET timezone. regards Stefan Schmidt > Regards, > Jonathan > > On 08/02/2019, 09:34, "Stefan Schmidt" wrote: > > Hello. > > On 06.02.19 15:33, Jonathan Aquilina wrote: > > I just landed a new job which I start on Monday but I am willing to > help and take over this. I am sure a lot more can be automated for sure. > > Have you looked at the wiki page and scripts used for release handling? > Much of the mechanical work of building the tarball and pushing it out > is already scripted. Sure it could get cleaned up and maybe made more > robust, but its there. > > What could be further automated is the news generation and addtition to > the wiki, sending out release mails, etc. Could all be done but it never > urged me enough to spend time on it. > > > > > I think best place to get this rolling would be to do a conference call > or a chat on slack. > > Slack or IRC. What day and time would you prefer? > > regards > Stefan Schmidt > > > -Original Message- > > From: Stefan Schmidt > > Sent: 06 February 2019 13:56 > > To: enlightenment-devel@lists.sourceforge.net; Jonathan Aquilina > > > Subject: Re: [E-devel] 1.22 schedule proposal > > > > Hello Jonathan. > > > > On 09.01.19 16:26, Jonathan Aquilina wrote: > >> I'm ready to step and take charge of this but I think we need a bit > more frequent minor release updates both for those in the community that want > to Be on the bleeding edge and those that want to help bug fix more > incremental stable releases. > > > > So, a 1.21.2. We currently have 4 patches pending in the 1.21.x branch > which are not in the 1.21.1 release. When announced that there will be a > stable update we might see more backports coming. > > > >> Stefan do you have any documentation on how release plan works? > > > > I posted this very link to you a couple of times, but I had no feedback > from you if that covers what you asked for. > > > > https://phab.enlightenment.org/w/release_procedure/ > > > > Jonathan, are you willing top work on a 1.21.2 stable release? > > I can give you a hand but I would need to know if you are willing, have > the time and the bandwidth to do this. > > > > 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
Hello. On 06.02.19 15:33, Jonathan Aquilina wrote: > I just landed a new job which I start on Monday but I am willing to help and > take over this. I am sure a lot more can be automated for sure. Have you looked at the wiki page and scripts used for release handling? Much of the mechanical work of building the tarball and pushing it out is already scripted. Sure it could get cleaned up and maybe made more robust, but its there. What could be further automated is the news generation and addtition to the wiki, sending out release mails, etc. Could all be done but it never urged me enough to spend time on it. > > I think best place to get this rolling would be to do a conference call or a > chat on slack. Slack or IRC. What day and time would you prefer? regards Stefan Schmidt > -Original Message- > From: Stefan Schmidt > Sent: 06 February 2019 13:56 > To: enlightenment-devel@lists.sourceforge.net; Jonathan Aquilina > > Subject: Re: [E-devel] 1.22 schedule proposal > > Hello Jonathan. > > On 09.01.19 16:26, Jonathan Aquilina wrote: >> I'm ready to step and take charge of this but I think we need a bit more >> frequent minor release updates both for those in the community that want to >> Be on the bleeding edge and those that want to help bug fix more incremental >> stable releases. > > So, a 1.21.2. We currently have 4 patches pending in the 1.21.x branch which > are not in the 1.21.1 release. When announced that there will be a stable > update we might see more backports coming. > >> Stefan do you have any documentation on how release plan works? > > I posted this very link to you a couple of times, but I had no feedback from > you if that covers what you asked for. > > https://phab.enlightenment.org/w/release_procedure/ > > Jonathan, are you willing top work on a 1.21.2 stable release? > I can give you a hand but I would need to know if you are willing, have the > time and the bandwidth to do this. > > 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
I just landed a new job which I start on Monday but I am willing to help and take over this. I am sure a lot more can be automated for sure. I think best place to get this rolling would be to do a conference call or a chat on slack. -Original Message- From: Stefan Schmidt Sent: 06 February 2019 13:56 To: enlightenment-devel@lists.sourceforge.net; Jonathan Aquilina Subject: Re: [E-devel] 1.22 schedule proposal Hello Jonathan. On 09.01.19 16:26, Jonathan Aquilina wrote: > I'm ready to step and take charge of this but I think we need a bit more > frequent minor release updates both for those in the community that want to > Be on the bleeding edge and those that want to help bug fix more incremental > stable releases. So, a 1.21.2. We currently have 4 patches pending in the 1.21.x branch which are not in the 1.21.1 release. When announced that there will be a stable update we might see more backports coming. > Stefan do you have any documentation on how release plan works? I posted this very link to you a couple of times, but I had no feedback from you if that covers what you asked for. https://phab.enlightenment.org/w/release_procedure/ Jonathan, are you willing top work on a 1.21.2 stable release? I can give you a hand but I would need to know if you are willing, have the time and the bandwidth to do this. 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
Hello Jonathan. On 09.01.19 16:26, Jonathan Aquilina wrote: > I’m ready to step and take charge of this but I think we need a bit more > frequent minor release updates both for those in the community that want to > Be on the bleeding edge and those that want to help bug fix more incremental > stable releases. So, a 1.21.2. We currently have 4 patches pending in the 1.21.x branch which are not in the 1.21.1 release. When announced that there will be a stable update we might see more backports coming. > Stefan do you have any documentation on how release plan works? I posted this very link to you a couple of times, but I had no feedback from you if that covers what you asked for. https://phab.enlightenment.org/w/release_procedure/ Jonathan, are you willing top work on a 1.21.2 stable release? I can give you a hand but I would need to know if you are willing, have the time and the bandwidth to do this. 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
Hey Felipe, If you check out Stefan's more recent mails, there was some feedback on this already and the freeze is being pushed back to February to give people more time to finish things that are currently underway. I would speculate that we might do a freeze around 20 Feb 2019, which would give a bit over a month to continue working on various major tasks. I think there's a lot going on now, and I doubt that there would be much manpower available to work on bug/regression fixing as needed for a release if we attempted to initiate it in the very near future, so it makes sense to postpone this timeline a bit. Mike On Sun, Jan 13, 2019 at 3:07 PM Felipe Magno de Almeida < felipe.m.alme...@gmail.com> wrote: > On Thu, Jan 10, 2019 at 12:22 AM Stefan Schmidt > wrote: > > > > Hello. > > [snip] > > > After 5 full months of development I think we should allow two weeks > > before we freeze to allow everybody to get their work in order. Fixes > > will follow over the next weeks to get it ready. > > > > Here is my release schedule proposal to get us started. Comments? > > I'm not sure 2 weeks will be enough to get C# fully working. Unless > somethings will be considered fixes, instead of features, like missing > constant generation and some manual bindings for Data-Model. > > Regards, > > > === Schedule === > > 2018-08-17 Merge window for 1.22 opens > > 2019-01-18 Notice about soon ending merge window > > 2019-01-23 Merge window is over. Freeze in place. > > * Only bug fixes from this point > > * Alpha release tarball > > * One month stabilization phase starts > > 2019-01-30 Beta1 release tarball > > * Only critical fixes from this point > > 2019-02-06 Beta2 release tarball > > 2019-02-13 EFL 1.22 is out > > > > regards > > Stefan Schmidt > > > -- > Felipe Magno de Almeida > > > ___ > 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
On Mon, 14 Jan 2019 05:05:36 +0900 Felipe Magno de Almeida said: > On Thu, Jan 10, 2019 at 12:22 AM Stefan Schmidt > wrote: > > > > Hello. > > [snip] > > > After 5 full months of development I think we should allow two weeks > > before we freeze to allow everybody to get their work in order. Fixes > > will follow over the next weeks to get it ready. > > > > Here is my release schedule proposal to get us started. Comments? > > I'm not sure 2 weeks will be enough to get C# fully working. Unless > somethings will be considered fixes, instead of features, like missing > constant generation and some manual bindings for Data-Model. Release as-is with bindings still in beta unstable etc. and then punt this to next release. very simple. :) > Regards, > > > === Schedule === > > 2018-08-17 Merge window for 1.22 opens > > 2019-01-18 Notice about soon ending merge window > > 2019-01-23 Merge window is over. Freeze in place. > > * Only bug fixes from this point > > * Alpha release tarball > > * One month stabilization phase starts > > 2019-01-30 Beta1 release tarball > > * Only critical fixes from this point > > 2019-02-06 Beta2 release tarball > > 2019-02-13 EFL 1.22 is out > > > > regards > > Stefan Schmidt > > > -- > Felipe Magno de Almeida > > > ___ > 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
On Thu, Jan 10, 2019 at 12:22 AM Stefan Schmidt wrote: > > Hello. [snip] > After 5 full months of development I think we should allow two weeks > before we freeze to allow everybody to get their work in order. Fixes > will follow over the next weeks to get it ready. > > Here is my release schedule proposal to get us started. Comments? I'm not sure 2 weeks will be enough to get C# fully working. Unless somethings will be considered fixes, instead of features, like missing constant generation and some manual bindings for Data-Model. Regards, > === Schedule === > 2018-08-17 Merge window for 1.22 opens > 2019-01-18 Notice about soon ending merge window > 2019-01-23 Merge window is over. Freeze in place. > * Only bug fixes from this point > * Alpha release tarball > * One month stabilization phase starts > 2019-01-30 Beta1 release tarball > * Only critical fixes from this point > 2019-02-06 Beta2 release tarball > 2019-02-13 EFL 1.22 is out > > regards > Stefan Schmidt -- Felipe Magno de Almeida ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] 1.22 schedule proposal
Hello Jonathan. On 09.01.19 16:26, Jonathan Aquilina wrote: > I’m ready to step and take charge of this but I think we need a bit more > frequent minor release updates both for those in the community that want to > Be on the bleeding edge and those that want to help bug fix more incremental > stable releases. Glad to hear. Happy to have you in the release team. How often do you think we should have minor releases? On y fix schedule or when enough patches have been in? We could look and see if we should do one for the 1.21.X line. That might be a good exercise to get started. You have an interest in working on this (with my help)? > Stefan do you have any documentation on how release plan works? You missed my answer to your other mail (next release)? Here are my notes how I did the releases: https://phab.enlightenment.org/w/release_procedure/ Pretty sure there are many things that are not clear to anyone but me. Feel free to edit the wiki and ask me. If you could get yourself comfortable with the steps involved that would already be a help. For example try to produce some release tarballs on your local machine and see if you run into troubles. regards Stefan Schmidt > Get Outlook for iOS<https://aka.ms/o0ukef> > > > From: Stefan Schmidt > Sent: Wednesday, January 9, 2019 16:22 > To: e > Subject: [E-devel] 1.22 schedule proposal > > Hello. > > Its almost 5 months since we released 1.21 and I stepped down. > > When talking with people I got help offers on the release handling but > no-one stepped up to fully take a lead on this. I start to get the > feeling that this might need to be handled with a smoother transition of > knowledge and work. > > Jonathan and Mike both offered help and others also expressed that they > would be willing to do their share towards a release. I count on you to > make this work :-) > > To get back to time based releases we should get working on 1.22 soon > (and not block ourselves with $FEATURE not being ready right now) > > The 3 months based schedule has been putting to much load onto the > project with release stuff. At least that is my opinion. After 1.22 is > out we should think about increasing this. Maybe 4, 5 or even 6 months? > Up to discussion. > > After 5 full months of development I think we should allow two weeks > before we freeze to allow everybody to get their work in order. Fixes > will follow over the next weeks to get it ready. > > Here is my release schedule proposal to get us started. Comments? > > === Schedule === > 2018-08-17 Merge window for 1.22 opens > 2019-01-18 Notice about soon ending merge window > 2019-01-23 Merge window is over. Freeze in place. > * Only bug fixes from this point > * Alpha release tarball > * One month stabilization phase starts > 2019-01-30 Beta1 release tarball > * Only critical fixes from this point > 2019-02-06 Beta2 release tarball > 2019-02-13 EFL 1.22 is out > > 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 > ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] 1.22 schedule proposal
Hello. On 10.01.19 10:24, Simon Lees wrote: > > > On 10/01/2019 01:51, Stefan Schmidt wrote: >> Hello. >> >> Its almost 5 months since we released 1.21 and I stepped down. >> >> When talking with people I got help offers on the release handling but >> no-one stepped up to fully take a lead on this. I start to get the >> feeling that this might need to be handled with a smoother transition of >> knowledge and work. >> >> Jonathan and Mike both offered help and others also expressed that they >> would be willing to do their share towards a release. I count on you to >> make this work :-) >> >> To get back to time based releases we should get working on 1.22 soon >> (and not block ourselves with $FEATURE not being ready right now) >> >> The 3 months based schedule has been putting to much load onto the >> project with release stuff. At least that is my opinion. After 1.22 is >> out we should think about increasing this. Maybe 4, 5 or even 6 months? >> Up to discussion. > > From a distro perspective i'd tend to agree that longer would be better, > especially with the amount that needs to be repackaged every release on > our end due to eo changes. When we get to a point were no one is > breaking eo anymore either because its done or people just aren't > working on it anymore then going back to 3 monthly is probably more > manageable. Fair enough. Let's go for a longer cycle and see how that works for all parties and we can refine later. 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
Hello. On 09.01.19 16:21, Stefan Schmidt wrote: > Hello. > > Its almost 5 months since we released 1.21 and I stepped down. > > When talking with people I got help offers on the release handling but > no-one stepped up to fully take a lead on this. I start to get the > feeling that this might need to be handled with a smoother transition of > knowledge and work. > > Jonathan and Mike both offered help and others also expressed that they > would be willing to do their share towards a release. I count on you to > make this work :-) > > To get back to time based releases we should get working on 1.22 soon > (and not block ourselves with $FEATURE not being ready right now) > > The 3 months based schedule has been putting to much load onto the > project with release stuff. At least that is my opinion. After 1.22 is > out we should think about increasing this. Maybe 4, 5 or even 6 months? > Up to discussion. > > After 5 full months of development I think we should allow two weeks > before we freeze to allow everybody to get their work in order. Fixes > will follow over the next weeks to get it ready. > > Here is my release schedule proposal to get us started. Comments? I have a comment myself. :-) Seems I was a bit to eager to get this all back on track. Some feedback I got showed that this came as surprise to some and might not be the best timing to give only a two weeks notice to gets things in order just after season holidays for many. Its a fair point. As much as I want to decouple features from releases its unfair to force this on people when we did not talk about it for 5 months. Additionally there is FOSDEM coming up which means travel and less time for work for some. Taken that into account and slept over this we should push the freeze back to February. Any input on this? Any other dates I should take into account? If nothing else comes up I will come up with a new schedule next week. regards Stefan Schmidt > === Schedule === > 2018-08-17 Merge window for 1.22 opens > 2019-01-18 Notice about soon ending merge window > 2019-01-23 Merge window is over. Freeze in place. > * Only bug fixes from this point > * Alpha release tarball > * One month stabilization phase starts > 2019-01-30 Beta1 release tarball > * Only critical fixes from this point > 2019-02-06 Beta2 release tarball > 2019-02-13 EFL 1.22 is out > > 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] 1.22 schedule proposal
On 10/01/2019 01:51, Stefan Schmidt wrote: > Hello. > > Its almost 5 months since we released 1.21 and I stepped down. > > When talking with people I got help offers on the release handling but > no-one stepped up to fully take a lead on this. I start to get the > feeling that this might need to be handled with a smoother transition of > knowledge and work. > > Jonathan and Mike both offered help and others also expressed that they > would be willing to do their share towards a release. I count on you to > make this work :-) > > To get back to time based releases we should get working on 1.22 soon > (and not block ourselves with $FEATURE not being ready right now) > > The 3 months based schedule has been putting to much load onto the > project with release stuff. At least that is my opinion. After 1.22 is > out we should think about increasing this. Maybe 4, 5 or even 6 months? > Up to discussion. >From a distro perspective i'd tend to agree that longer would be better, especially with the amount that needs to be repackaged every release on our end due to eo changes. When we get to a point were no one is breaking eo anymore either because its done or people just aren't working on it anymore then going back to 3 monthly is probably more manageable. -- 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] 1.22 schedule proposal
This seems like a sensible schedule overall. Thanks, Stefan for helping out with the release process once again! On Wed, Jan 9, 2019 at 10:22 AM Stefan Schmidt wrote: > Hello. > > Its almost 5 months since we released 1.21 and I stepped down. > > When talking with people I got help offers on the release handling but > no-one stepped up to fully take a lead on this. I start to get the > feeling that this might need to be handled with a smoother transition of > knowledge and work. > > Jonathan and Mike both offered help and others also expressed that they > would be willing to do their share towards a release. I count on you to > make this work :-) > > To get back to time based releases we should get working on 1.22 soon > (and not block ourselves with $FEATURE not being ready right now) > > The 3 months based schedule has been putting to much load onto the > project with release stuff. At least that is my opinion. After 1.22 is > out we should think about increasing this. Maybe 4, 5 or even 6 months? > Up to discussion. > > After 5 full months of development I think we should allow two weeks > before we freeze to allow everybody to get their work in order. Fixes > will follow over the next weeks to get it ready. > > Here is my release schedule proposal to get us started. Comments? > > === Schedule === > 2018-08-17 Merge window for 1.22 opens > 2019-01-18 Notice about soon ending merge window > 2019-01-23 Merge window is over. Freeze in place. > * Only bug fixes from this point > * Alpha release tarball > * One month stabilization phase starts > 2019-01-30 Beta1 release tarball > * Only critical fixes from this point > 2019-02-06 Beta2 release tarball > 2019-02-13 EFL 1.22 is out > > 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] 1.22 schedule proposal
I’m ready to step and take charge of this but I think we need a bit more frequent minor release updates both for those in the community that want to Be on the bleeding edge and those that want to help bug fix more incremental stable releases. Stefan do you have any documentation on how release plan works? Get Outlook for iOS<https://aka.ms/o0ukef> From: Stefan Schmidt Sent: Wednesday, January 9, 2019 16:22 To: e Subject: [E-devel] 1.22 schedule proposal Hello. Its almost 5 months since we released 1.21 and I stepped down. When talking with people I got help offers on the release handling but no-one stepped up to fully take a lead on this. I start to get the feeling that this might need to be handled with a smoother transition of knowledge and work. Jonathan and Mike both offered help and others also expressed that they would be willing to do their share towards a release. I count on you to make this work :-) To get back to time based releases we should get working on 1.22 soon (and not block ourselves with $FEATURE not being ready right now) The 3 months based schedule has been putting to much load onto the project with release stuff. At least that is my opinion. After 1.22 is out we should think about increasing this. Maybe 4, 5 or even 6 months? Up to discussion. After 5 full months of development I think we should allow two weeks before we freeze to allow everybody to get their work in order. Fixes will follow over the next weeks to get it ready. Here is my release schedule proposal to get us started. Comments? === Schedule === 2018-08-17 Merge window for 1.22 opens 2019-01-18 Notice about soon ending merge window 2019-01-23 Merge window is over. Freeze in place. * Only bug fixes from this point * Alpha release tarball * One month stabilization phase starts 2019-01-30 Beta1 release tarball * Only critical fixes from this point 2019-02-06 Beta2 release tarball 2019-02-13 EFL 1.22 is out 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
[E-devel] 1.22 schedule proposal
Hello. Its almost 5 months since we released 1.21 and I stepped down. When talking with people I got help offers on the release handling but no-one stepped up to fully take a lead on this. I start to get the feeling that this might need to be handled with a smoother transition of knowledge and work. Jonathan and Mike both offered help and others also expressed that they would be willing to do their share towards a release. I count on you to make this work :-) To get back to time based releases we should get working on 1.22 soon (and not block ourselves with $FEATURE not being ready right now) The 3 months based schedule has been putting to much load onto the project with release stuff. At least that is my opinion. After 1.22 is out we should think about increasing this. Maybe 4, 5 or even 6 months? Up to discussion. After 5 full months of development I think we should allow two weeks before we freeze to allow everybody to get their work in order. Fixes will follow over the next weeks to get it ready. Here is my release schedule proposal to get us started. Comments? === Schedule === 2018-08-17 Merge window for 1.22 opens 2019-01-18 Notice about soon ending merge window 2019-01-23 Merge window is over. Freeze in place. * Only bug fixes from this point * Alpha release tarball * One month stabilization phase starts 2019-01-30 Beta1 release tarball * Only critical fixes from this point 2019-02-06 Beta2 release tarball 2019-02-13 EFL 1.22 is out regards Stefan Schmidt ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
