FEATURE FREEZE, for a short time

FEATURE FREEZE, for a short time

[Carsten Dominik]

Dear all,

I would like to ask for a feature freeze for the Org-mode master branch
until about July 18.

During the period I would like to ask the committers to only
process bug fixes (and only reasonably simple ones) and
release-related stuff like Makefile issues, doc fixes, typos etc.   
Please
also check the issue tracker if you want to help fix a small issue,  
there
is also documentation stuff that needs to be done.

This will give me the breezing space to put together the 7.01 release.

Of course, in a git environment, this does not at all mean that  
development
has to stop - it only means that new features will not be merged into  
master
during that period.

One the 18th, I would like to release 7.01 and shortly thereafter  
install it into
the Emacs repository.

Thanks a bunch.

- Carsten

P.S.  Eric and Dan, please decide yourself how to get to
a good and stable state in this time frame, babel integration
is by far the biggest thing in this release.

Re: FEATURE FREEZE, for a short time

[Eric Schulte]

Carsten Dominik <carsten.dominik@gmail.com> writes:

[...]
> 
> P.S.  Eric and Dan, please decide yourself how to get to
> a good and stable state in this time frame, babel integration
> is by far the biggest thing in this release.

Hi Carsten,

I'm looking forward to a feature-quiet period of stabilization.  There
is one more large Babel change before 7.0, namely the integration of the
safety measures currently living in the "safety-babel" branch [1].  I
think that it would be best if these are merged into Org-mode at the
start of this feature freeze so that they can be tested during this
period.  Please let me know if this sounds good to you, and if so I will
send out one last email alerting Babel users to the requirement for a
configuration change [2], and then merge in these two new commits.

Thanks -- Eric

Footnotes: 
[1]  http://repo.or.cz/w/org-mode.git/shortlog/refs/heads/safety-babel

[2]  I do apologize for the number of configuration breaking changes
     that have been made to Babel recently.  I know the pain of starting
     up Emacs, running into an unexpected failure, and then having to
     make time to trouble-shoot before you can actually get any work
     done.

     Once this merge is over I see many months of smooth Babel sailing
     on the horizon.