this is an update to a couple of upcoming changes this git repository. These
changes will break workflows that currently depend on cloning this repository
directory and using the master branch. As such I'm giving a one week notice for
everyone to have a chance to update their scripts.
As Python2 official support is quickly coming to an end as well as our
development focus having largely moved to the next branch we'll be:
* deprecating the current master branch where Python2 XML recipe code currently
lives. We'll create a new 'legacy-py2' branch and the current revision will
tagged with v14, this will be the final release of LNST that works on Python2
and uses XML based recipes.
* The 'master-py3' branch will be renamed to 'legacy-py3' and the current
revision will be tagged with v15.
* If needed we might provide or accept bug fixes to these branches and might tag
new minor releases tagged v14.y or v15.y. There will be no more features or
test recipes developed on these branches, this is basically the current state
anyway so it shouldn't be a surprise.
* We'll work on packaging both versions as rpms for Fedora this week, after that
the minor updates to v15 might get rpm updates but only until v16 has been
* The current next branch will be renamed to 'master' and any feature or test
recipe development will happen on this branch. The first release will be
tagged v16 and will happen once we're satisfied with the stability of the
basic tester facing APIs so that we can ensure their future compatibility.
In my opinion the current state of the next branch is good enough for basic
usage and some APIs are probably good enough to call stable. However as we
develop some of our old test set with the new APIs, small changes may happen and
some new features might appear.
I expect that in the 'near future' of let's say 6 months we'll actively
started reviewing and marking some APIs as stable. Once the basic minimum of
features has been marked as stable we'll tag the first release of the redesigned
LNST with python recipes.
If you have any concerns/questions/suggestions or any generic comments for
discussion please feel free to reply to this email.