Do we have to do any bureaucratize to register as having passed the TCK? Or is it:
* Generate release artifacts. * VOTE on release. * VOTE on Attic. * Publish. * Make project read-only. Hen On Mon, Dec 31, 2012 at 3:11 PM, Henri Yandell <flame...@gmail.com> wrote: > What exactly is left to do the release? Not having a permissively > licensed JSTL 1.2 is a shame when the code is there. Even if we put it > in the Attic, I'd love to say "And here is a 1.2 compliant version, > good luck" rather than "sorry, get it from SVN". > > I'd be happy to put in the effort to do the votes/website. I'd need to > hit the site anyway as a part of sending it to the Attic. > > Is it 100% good on the TCK, nothing more needed? > > Hen > > On Mon, Nov 26, 2012 at 4:44 PM, Jeremy Boynes <jboy...@apache.org> wrote: >> +0 >> >> It's perhaps not surprising that there is not much activity as there has >> been no update to the JSR in many years. The JSTL code in trunk does pass >> the 1.2 TCK and could be released if someone had the energy to fix the >> website and rustle up votes. >> >> On Oct 13, 2012, at 10:58 AM, Henri Yandell wrote: >> >>> Hard to argue against it. I've no energy for Taglibs coding. I wish >>> we'd got a JSTL 1.2 released, but c'est la vie. >>> >>> All the steps listed sound good except removing the website. >>> Historically on the Attic side we've kept the websites up with a >>> notice that the project is dead, rather than going dark on people. >>> >>> Hen >>> >>> On Mon, Oct 1, 2012 at 12:55 AM, Henri Gomez <henri.go...@gmail.com> wrote: >>>> If there is no activity, it make sense. >>>> >>>> +0 >>>> >>>> 2012/10/1 Mark Thomas <ma...@apache.org>: >>>>> In the two+ years since Taglibs moved to the Tomcat project there have >>>>> been a few short bursts of activity totalling just over 200 commits but >>>>> no releases. There has also been no progress towards a migration to >>>>> svnpubsub for the taglibs part of the web site. >>>>> >>>>> Given the lack of progress I would propose that Taglibs is moved to our >>>>> archive. This would mean: >>>>> >>>>> - removing the Taglibs link from tomcat.a.o >>>>> - removing the Taglibs web pages >>>>> - moving the tomcat/tagslibs svn tree to tomcat/archive/taglibs >>>>> - making the Taglibs BZ project read-only >>>>> - moving the Taglibs committers to emeritus status >>>>> - removing the Taglibs from Gump >>>>> >>>>> There is nothing to remove from dist.a.o since there have been no releases >>>>> >>>>> Note: This is intended as a discussion topic - not a formal proposal/vote. >>>>> >>>>> Thoughts? >>>>> >>>>> Mark >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >>>>> For additional commands, e-mail: dev-h...@tomcat.apache.org >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >>>> For additional commands, e-mail: dev-h...@tomcat.apache.org >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: dev-h...@tomcat.apache.org >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: dev-h...@tomcat.apache.org >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
