Hi,
following up on the Monday LNST upstream meeting discussions, I'm
announcing that in 2 weeks time (30th of September 2016) we will stop
accepting code implementing new features for the current master branch
of LNST. If you have any features in development that you'd like to be
included into upstream or you have any features that you'd like
requested for LNST that still supports XML recipes voice them on the
mailing list until the mentioned deadline.
The reason for this is the recent creation of the 'next' branch
introducing a first Proof of Concept implementation of Python recipes.
We want to move on with further development on this branch which will
also include quite a lot of internal code refactorization and cleanup.
Because of this porting/cherry-picking new features from the current
'master' branch will become costly and we'd rather spend our time on
getting the 'next' branch to a good state as quickly as possible.
After the feature freeze, the master branch will continue to be
maintained and will receive bug fixes. I'm also planning to tag at least
one more versioned release of LNST that I'll package for Fedora and
EPEL{6,7}.
We'll remain in this state while we continue development on the 'next'
branch until we're satisfied with the user/test facing interfaces and
consider them stable. Once we reach that point we'll rename the current
'master' branch to something like 'old' and rename the 'next'
branch to
'master' after which we'll also do a new versioned release that will be
completely incompatible with previous versions.
This is a rough guideline of our plan for LNST for the next couple of
months, suggestions and comments are of course welcome and we reserve
the right to change the plan at any point (obligatory disclaimer :)).
-Ondrej
Show replies by date