On Mon, Dec 2, 2019 at 8:07 AM Martin Jansa <[email protected]> wrote:
> Thanks > > It would be nice to delete all branches except master. Only master branch > makes sense now for meta-python2, right? > > " The stable branches were also kept, to make it easier to refer back to prior history and allow developers to use meta-python2 only in their workflow." I can see use cases where a developer may want to replace meta-python with meta-python2 and still be on a "stable" release. It also makes reviewing what existed in which release much easier with cgit or git log --oneline, which I do VERY frequently. If this is contentious then the OE-TSC will make the decision. > On Mon, Dec 2, 2019 at 4:57 PM Tim Orling <[email protected]> wrote: > >> Why? >> ==== >> With the pending EOL (end-of-life) of Python 2 in a month [1], it is time >> to move python2 recipes to a new home. For that reason, meta-python2 [2] >> has been created as the home for legacy python2 recipes. >> >> How? >> ==== >> It was a design goal to keep the original history of meta-python, but only >> the python2 parts. In order to accomplish this git-filter-repo was used >> [3]. The exact steps used can be seen in a gist [4]. After that script was >> run, manual merging of *.inc and *.bb files was performed to make recipe >> maintenance with AUH (auto upgrade helper) and devtool easier. Since this >> layer does not have to support two python versions, the reason for the >> *.bb >> and *.inc split has been eliminated. Commits that upgraded recipes to >> python2-incompatible versions were reverted. Changes to make the recipes >> build and ptests be runnable were also made (to master branch). The stable >> branches were also kept, to make it easier to refer back to prior history >> and allow developers to use meta-python2 only in their workflow. NOTE: The >> stable branches may require work to make them usable, this was outside the >> scope of the immediate effort. >> >> What next? >> ========= >> Python2 recipes from meta-python will be dropped via patches sent to the >> mailing list. Python2 recipes from meta-oe and meta-networking, which have >> already been added to meta-python2, will be dropped via patches to the >> mailing list. Other layers are welcome to do the same. >> >> Recipe upgrades to meta-python2 will also be coming, for instance Django >> 1.11.x LTS is the last version to support Python 2, but we are not at the >> latest release of that series. >> >> The original meta-python will become Python3-only and patches for python2 >> support will be nacked and redirected to meta-python2. >> >> python2 itself will likely be moved from oe-core into meta-python2 >> >> [1] https://www.python.org/doc/sunset-python-2/ >> [2] https://git.openembedded.org/meta-python2/ >> [3] https://github.com/newren/git-filter-repo >> [4] https://gist.github.com/moto-timo/ab70ab96ddbaf5fd1226bd21dbbfec9b >> -- >> _______________________________________________ >> Openembedded-devel mailing list >> [email protected] >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel >> > -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
