Aloha,
So seriously .. Thursday next week we will release RC2. This means a
commit freeze for all but build fixes and README commits starting
Monday evening. Also with RC2 any feature additions, regardless of how
small, will no longer be allowed (when in doubt if a patch is a
feature addition or a bug fix, ask one of the RMs). We are looking to
really wrap things up quickly now. So if necessary expect an RC3
within 2 weeks after RC2. And we will continue with this cycle until
we have a final release.
regards,
Lukas Kahwe Smith
mls@pooteeweet.org
So seriously .. Thursday next week we will release RC2. This means a
commit freeze for all but build fixes and README commits starting
Monday evening. Also with RC2 any feature additions, regardless of
how small, will no longer be allowed (when in doubt if a patch is a
feature addition or a bug fix, ask one of the RMs). We are looking
to really wrap things up quickly now. So if necessary expect an RC3
within 2 weeks after RC2. And we will continue with this cycle until
we have a final release.
Ok, so what is missing before we can make a commit freeze starting
Tuesday morning?
regards,
Lukas Kahwe Smith
mls@pooteeweet.org
hi Lukas,
The re3c bug (8k bug) for one.
Cheers,
So seriously .. Thursday next week we will release RC2. This means a
commit freeze for all but build fixes and README commits starting Monday
evening. Also with RC2 any feature additions, regardless of how small, will
no longer be allowed (when in doubt if a patch is a feature addition or a
bug fix, ask one of the RMs). We are looking to really wrap things up
quickly now. So if necessary expect an RC3 within 2 weeks after RC2. And we
will continue with this cycle until we have a final release.Ok, so what is missing before we can make a commit freeze starting Tuesday
morning?regards,
Lukas Kahwe Smith
mls@pooteeweet.org--
--
Pierre
hi Lukas,
The re3c bug (8k bug) for one.
yeah .. well it seems we will not have a fix for this (and a release
today). however johannes and I both agree that testers need to get
their hands on a more recent version of our code, since RC1 was
released so long ago. especially in the light of the testfest. so we
both think there is value in releasing the RC2 this week, even if that
means we will surely need an RC3. i then expect this RC3 to come out 2
weeks after RC2. until then we need to make sure we can get that re2c
bug fixed and a new release out. this might require reducing the bus
factor on re2c. so anyone interested please get in contact with Nuno
as Marcus is understandably quite busy with private matters atm.
regards,
Lukas Kahwe Smith
mls@pooteeweet.org
until then we need to
make sure we can get that re2c bug fixed and a new release out. this might
require reducing the bus factor on re2c.
A good starting point for re2c internals is the following paper:
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.27.1624
It looks like feasible to add the EOF feature to re2c (which means
switching to states depending of their depth (to ensure to not read
ahead), and becoming ungreedy on regexps like "foo"+ when their is no
additional chars (to unsure to match a token without having to see an
other char next to it)).
Is anyone working on it already ? (or any thought on this ?)
Regards,
Arnaud
Aloha,
So seriously .. Thursday next week we will release RC2. This means a
commit freeze for all but build fixes and README commits starting
Monday evening. Also with RC2 any feature additions, regardless of
how small, will no longer be allowed (when in doubt if a patch is a
feature addition or a bug fix, ask one of the RMs). We are looking
to really wrap things up quickly now. So if necessary expect an RC3
within 2 weeks after RC2. And we will continue with this cycle until
we have a final release.
Just as a reminder, we are now in a commit freeze until we have tagged
RC2. If all goes well we will have the tag done sometime tomorrow.
Please until then only do commits that are very well tested and that
address build fixes. Commits to README's etc are also still legit.
When in doubt talk to Johannes and Pierre pr proxy your requests
through me (though I am not the one to make technical decisions).
regards,
Lukas Kahwe Smith
mls@pooteeweet.org