portage-2.3.0_rc1 and repoman-2.3.0_rc1 are now in the tree.

portage-2.3.0_rc1 is essentially the portage 2.2.28 release with only a
few small patches applied.  It mostly just installs less code, namely
the repoman code.

So, now servers and other systems that do not require repo Q/A ability
will no longer get repoman installed anyway.

repoman-2.3.0_rc1 is the stage2 rewrite code. The checks are now
modular, and using the portage plugin system. The system is not yet
fully plug and play. Those changes will take place in the stage3
re-writes.

The two packages will remain in the same portage git repo, although the
repoman code has been moved into it's own pkg directory.  It is too
tied into portage api's to be on it's own just yet.  An that
is not likely to happen until we get a stable portage API.  This new
system does allow for semi-independant releases for both repoman and
portage.  When important API's change, it will require both to be
release at the same time.  So you can look forward to seeing the minor
version number to get more frequent bumps than it has this last decade.

Currently, the portage ebuild does not RDEPEND on the repoman ebuild.
You will have to explicitly emerge it for it to be installed. It has
been suggested to add a use flag enabled RDEPEND (default on) for the
dev profile.  I will also be adding that to the portage-9999 release
for all profiles in the coming days.

NOTES:  Repoman now depends on lxml for it's xml parsing and error
checking along with now using metadata.xsd.  It now will report a lot
more errors than the previous buggy code everyone has been using.

I want to thank the following people for their help and contributions
to make these releases:

        Zac Medico <zmedico>
        Alexander Bernsten <bernalex>
        Dirkjan Ochtman <djc> for the base xml re-write code
        Michal Gorny <mgorny> for the metadata.xsd changes
        Göktürk Yüksek <gokturk> for the metadata.xml test ebuilds
                patches.
        Mike Gilbert <floppym> for all the testing on the rewite code,
                and a number of gen-b0rk repo test ebuilds.

        Coacher for the recent testing, bug reports and patches.
        And anyone else I missed ;)

So, please report any issues with either the ebuilds or installs, bugs,
etc... you know the drill ;)

Don't forget, please contribute more test case ebuilds to the gen-b0rk
repo.  The better the test ebuild coverage we have, the better our Q/A
tools (like repoman) will be and the less often things will be released
broken.

Thank you
--
Brian Dolbec <dolsen>