Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Wed, Dec 29, 2010 at 09:23:26AM +0100, Ulrich Mueller wrote:
> >>>>> On Tue, 28 Dec 2010, Ulrich Mueller wrote:
>
> > So unless there are any last-minute changes (Fauli?), the following
> > commit should be tagged:
>
> There's another trivial update (removal of an unused file, output is
> not affected), so the commit to be tagged is:
> <http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=commit;h=348ea6c695bf7fe079c43e294ddbd06bca3d0cfc>
+1 on 348ea6c695bf7fe079c43e294ddbd06bca3d0cfc as the tagging point.
> > The tag should be called "eapi-4-approved-2010-12-30" if we follow the
> > convention we used for EAPIs 2 and 3.
I'm personally of the opinion that should just be "eapi-4"; the commit
msg can include the approval specifics.
If we need to approve a tweaked version of eapi4 itself- just name it
"eapi-4-v1" or whatever. Jamming the approval date in is annoying
however.
~brian
|
|
