From: Marius Mauch <genone@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] naming scheme
Date: Thu, 16 Sep 2004 22:50:04 +0200 [thread overview]
Message-ID: <20040916225004.250a588f@andy.genone.homeip.net> (raw)
In-Reply-To: <200409162209.13596.list@hoenig.cc>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On 09/16/04 Christian Hoenig wrote:
> Aloah,
>
> > > Why is portage using such a strange naming scheme? Why are we
> > > only increasing ´build numbers´? As this seems to be a major
> > > release, why don´t we make a 2.1 out of it?
> >
> > I don't think this is a "major" release as in "major version" but
> > more as in "big deal". From what I've heard, a major version change
> > will be reserved for a complete rewrite of Portage.
>
> You mean, it needs a complete rewrite for a 2.1?
> If thats the case, why don´t we simply drop the ´2´? ;-)
3.x will be a complete rewrite.
2.1 will bring structural changes to vardb and the new API
2.0.52 will probably be the last version of the 2.0 branch
Marius
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-16 20:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 18:08 [gentoo-portage-dev] Portage .51 features Sven Vermeulen
2004-09-16 19:57 ` [gentoo-portage-dev] naming scheme (was: Portage .51 features) Christian Hoenig
2004-09-16 20:03 ` [gentoo-portage-dev] naming scheme Andrew Gaffney
2004-09-16 20:08 ` Michael Stewart
2004-09-16 20:30 ` Andrew Gaffney
2004-09-16 20:09 ` Christian Hoenig
2004-09-16 20:50 ` Marius Mauch [this message]
2004-09-16 20:51 ` Anthony Gorecki
2004-09-16 21:07 ` Marius Mauch
2004-09-19 22:05 ` Roman Gaufman
2004-09-16 21:13 ` Christian Hoenig
2004-09-17 8:46 ` [gentoo-portage-dev] Portage .51 features Sven Vermeulen
2004-09-17 11:27 ` Jason Stubbs
2004-09-18 11:56 ` Sven Vermeulen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040916225004.250a588f@andy.genone.homeip.net \
--to=genone@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox