Redundant, but you would never have questions whether versions of
project x are compatible with wicket y.

On 2/26/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> so what hapens when we release lets say 1.3. are we going to bump the
> version up on all of those even though there is no difference ( if that part
> of wicket remained the same) ?
> -Igor
>
>
>
>  On 2/26/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> >
> > >  [ x ]    all packages from the wicket core project should have the
> > > same major/minor release numbers
> > >  [   ]    all extraneous projects have their own release schedule, and
> > > hence their own release numbers
> >
> > This doesn't go for the wicket-stuff projects, but for the wicket core
> > projects, it makes sense to have the same release numbers. They don't
> > have to be exactly in sync (core might be 1.2.1 and auth 1.2.4), but
> > in general I think it is easier to find for people if we use the same
> > numberings.
> >
> > Eelco
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> > that extends applications into web and mobile media. Attend the live
> webcast
> > and join the prime developer group breaking into this new coding
> territory!
> >
> http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
> > _______________________________________________
> > Wicket-develop mailing list
> > [email protected]
> >
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
> >
>
>


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop

Reply via email to