Return-Path: Delivered-To: apmail-jakarta-taglibs-dev-archive@apache.org Received: (qmail 42089 invoked from network); 13 Sep 2002 12:05:00 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 13 Sep 2002 12:05:00 -0000 Received: (qmail 23659 invoked by uid 97); 13 Sep 2002 12:05:33 -0000 Delivered-To: qmlist-jakarta-archive-taglibs-dev@jakarta.apache.org Received: (qmail 23628 invoked by uid 97); 13 Sep 2002 12:05:32 -0000 Mailing-List: contact taglibs-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tag Libraries Developers List" Reply-To: "Tag Libraries Developers List" Delivered-To: mailing list taglibs-dev@jakarta.apache.org Received: (qmail 23616 invoked by uid 98); 13 Sep 2002 12:05:31 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D81D4BA.9060308@mail.more.net> Date: Fri, 13 Sep 2002 07:06:18 -0500 From: Glenn Nielsen Organization: MOREnet User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.0) Gecko/20020909 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tag Libraries Developers List Subject: Re: [String] stablizing release References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Henri Yandell wrote: > Hey Glenn, > > I'm not planning the JSTL stuff immediately, just some refactoring of tags > and a few additions, so I'd like to go and make a stable release of the > CVS soon. My sandbox is starting to get quite different. Do you think a > milestone as Shawn suggested, or a beta? > A milestone means that not all features have been implemented. A beta means that all features are implemented but the release isn't considered production quality yet. So it depends on the state of the String taglib. You could do a 1.0 beta release of the String taglib with its current features, then if there are no bugs do an official 1.0 release a few weeks later. Any new features for the String taglib could be in a 1.1 release. We really need to get better at having official stable releases of the taglibs. Many won't consider using something if it hasn't had an official release. > Basically I aim to have a stable jar built, placed in the releases dir, > hooked up to the site, and then I'll throw a bunch of tags out of > CVS and merge them. A kind of tag-name normalisation. > > What's the process with Taglib deploying? Do you admin them and handle the > builds, or is it easier for you if I learn how to do so? > Follow the instructions at: http://jakarta.apache.org/taglibs/addtaglib.html This will help you get the taglib ready for release, I can do the final steps to build and publish the release. Regards, Glenn > Thanks, > > Hen > > On Wed, 11 Sep 2002, Glenn Nielsen wrote: > > >>I would suggest a beta release of the current code. I can help do this. >>Once commons-lang is released we can do the final release. >> >>JSTL requires JSP 1.2, the current String taglib works in JSP 1.1, right? >> >>I would suggest a new String taglib, perhaps STLString which adds >>support for JSTL and requires JSP 1.2. And leave the current String >>taglib as a JSP 1.1 compatible version. >> >>That would work better within the current build system. >> >>Regards, >> >>Glenn >> >>Henri Yandell wrote: >> >>>I'm at a touch of a quandry. >>> >>>String taglib is dependent on Commons Lang, and I want to avoid releasing >>>String until there is a Lang release. >>> >>>So lots of users are dependent on the nightly build of String. >>> >>>I want to make some, not massive, but substantial changes to the taglib's >>>API, and also to make an attempt at adding JEL to it. I don't want to >>>'break' on customers though. >>> >>>What I'm considering is some form of stable release, calling it a beta >>>feels bad, but that's what it would be, a 1.0-b1, prior to making changes >>>for a 1.0-b2, which would then hopefully mature to a 1.0 release. >>> >>>Before I call a vote on it, does anyone have any advice about other ways >>>to do this etc? >>> >>>Hen >>> >>> >>>-- >>>To unsubscribe, e-mail: >>>For additional commands, e-mail: >> >> >> >> >>-- >>To unsubscribe, e-mail: >>For additional commands, e-mail: >> >> > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: