tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard Lewis Ship" <hls...@gmail.com>
Subject Re: Fix versions
Date Wed, 02 Jan 2008 20:56:32 GMT
The roadmap is a good idea, but I have a problem with JIRA's release
note generator, since it generates a line for every bug with the
release number, whether its been fixed, resolved, marked duplicate, or
is still open.

Roadmap is nice, but it really is about "geez, time for a release,
what can we fit in?" :-)

On Jan 2, 2008 12:10 PM, Jesse Kuhnert <jkuhnert@gmail.com> wrote:
> That's what I thought it was supposed to be used for..
>
>
> On Jan 2, 2008 3:08 PM, Kevin Menard <kmenard@servprise.com> wrote:
> > Is there any particular reason for that?  It seems to me that if you defined
> > a fix version you could start using JIRA's roadmap feature.  If the item
> > isn't resolved by the time you want to cut the release, JIRA has an easy
> > means of migrating all remaining issues to another fix version.
> >
> > --
> > Kevin
> >
> >
> > On 1/2/08 2:55 PM, in article 17207629.1199303734246.JavaMail.jira@brutus,
> > "Howard M. Lewis Ship (JIRA)" <dev@tapestry.apache.org> wrote:
> >
> > >
> > >      [
> > > https://issues.apache.org/jira/browse/TAPESTRY-1643?page=com.atlassian.jira.pl
> > > ugin.system.issuetabpanels:all-tabpanel ]
> > >
> > > Howard M. Lewis Ship updated TAPESTRY-1643:
> > > -------------------------------------------
> > >
> > >     Fix Version/s:     (was: 5.0.8)
> > >
> > > We don't define a fix version until a fix is committed.
> > >
> > >> @Mixin should accept parameters
> > >> -------------------------------
> > >>
> > >>                 Key: TAPESTRY-1643
> > >>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1643
> > >>             Project: Tapestry
> > >>          Issue Type: Bug
> > >>          Components: tapestry-core
> > >>    Affects Versions: 5.0.5
> > >>            Reporter: Dan Adams
> > >>
> > >> With @Mixin there is no way to use a mixin that requires parameters within
a
> > >> component. For instance if you have a Confirm mixin that has a required
> > >> parameter you can't use it like this:
> > >> @Mixin
> > >> private Confirm confirm;
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
>
> --
> Jesse Kuhnert
> Tapestry / OGNL / Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>



-- 
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message