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 ma
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 run
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 wor
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 withou
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
; > 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 - updat
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 b
t 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
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 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 lates
@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
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
: 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.
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 w
gt; 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 followin
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
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?
&g
@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
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?
>
> ===
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-0
an 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 tho
>
> Slack or IRC. What day and time would you prefer?
>
> regards
> Stefan Schmidt
>
> > -Original Message-
> > From: Stefan Schmidt
> > Sent: 06 February 2019 13:56
> &g
> > -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 Jonatha
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 m
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 mi
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
> s
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
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. F
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 schedu
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
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 th
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 ne
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
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
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 pe
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 wo
36 matches
Mail list logo
