Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 85820 invoked by uid 500); 13 Aug 2002 18:29:05 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 85809 invoked from network); 13 Aug 2002 18:29:04 -0000 Date: Tue, 13 Aug 2002 11:29:09 -0700 From: Aaron Bannert To: dev@apr.apache.org Subject: Re: cvs commit: apr-site versioning.html Message-ID: <20020813182909.GX9080@clove.org> Mail-Followup-To: Aaron Bannert , dev@apr.apache.org References: <20020813181757.GW9080@clove.org> <200208131824.OAA25106@devsys.jaguNET.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200208131824.OAA25106@devsys.jaguNET.com> User-Agent: Mutt/1.4i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > > Can we plan on doing this for 1.1 once we have the versioning in > > place and a solid release? > > As long as we remain transparent. If not, then we should do it > right in 1.0 (IMO). My main concern is that if we go down that path now then it may be a long time before we become stable again, and it will take time for our dependent projects to sync up too. It seems that we are at a point that we could call stable now, and if we want to redo the time interfaces at some later date we can do so on our own schedule, and call it 1.1 or 2.0 depending on what it takes to change it and how it fits with our versioning rules. -aaron