[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ivy-dev
Subject:    Re: 2.0.0 alpha 2 release
From:       "Tjeerd Verhagen" <tjeerd.verhagen () gmail ! com>
Date:       2007-07-10 12:14:06
Message-ID: 4d7c4c4b0707100514i266c0693m79c87774324a6f02 () mail ! gmail ! com
[Download RAW message or body]


Sorry, I see, I've been reading to fast over the previous text.

On 7/10/07, Xavier Hanin <xavier.hanin@gmail.com> wrote:
>
> On 7/10/07, Tjeerd Verhagen <tjeerd.verhagen@gmail.com> wrote:
> >
> > Some Jira tips:
> >
> > When resolving a issue, you can also use the resolution:
> > - Won't fix
> > - Duplicate
> > Or simmular, in that case it also usual to not add a fix-version.
> >
> > When having a duplicate, create a link (duplicated by) to the other
> issue.
> >
> > When a issue is fixed in multiple branches, just use (ctrl-click) to
> mark
> > multple versions for which the issue is fixed.
>
>
> Thanks for the tips. For the issues discussed here, I think we have
> followed
> these tips. So it seems it makes sense to let ivy-433 and ivy-519 fixed
> without a version. Any other opinion?
>
> Xavier
>
> On 7/10/07, Xavier Hanin <xavier.hanin@gmail.com> wrote:
> > >
> > > On 7/10/07, Scheper, Erik-Berndt <erik-berndt.scheper@sogeti.nl>
> wrote:
> > > >
> > > > Hi,
> > > >
> > > > I noticed that two issues are also marked as fixed, but not assigned
> > to
> > > > alpha-2 (ivy-433 and ivy-519).
> > >
> > >
> > > IVY-433 is a duplicate of IVY-404 which has been resolved in
> > 2.0.0-alpha-1
> > > .
> > > I don't know the best practice about assigning fixed version for
> > > duplicates.
> > > If we assign it to the version in which the original has been fixed,
> it
> > > changes the changelogs of the version after its release...
> > > IVY-519 is a false issue. Should we consider fixed in one version,
> while
> > > it
> > > has probably never been a real issue?
> > >
> > > Also, three issues are marked for release 1.4.2 (of which 2 are marked
> > > > as fixed).
> > > > What about these? Are they also fixed in 2.0-alpha-2?
> > >
> > >
> > > They are also fixed in 2.0-alpha-1, but the issues are clean on this
> > > matter
> > > (marked as fixed both on 1.4.2 and 2.0-alpha-1).
> > >
> > > I presume there will never be a 1.4.2 release, right?
> > >
> > >
> > > I'm not sure. Both issues are fixed on the 1.4.x branch. This branch
> > will
> > > never be released at apache (old package names and so on). And
> jayasoft
> > > won't release it either (no more web site to announce and host it). So
> > if
> > > the community asks for a 1.4.2, the community will have to release it.
> > But
> > > the branch is present in our code base.
> > >
> > > Xavier
> > >
> > > Regards,
> > > >
> > > > Erik-Berndt Scheper
> > > >
> > > >
> > > > -----Oorspronkelijk bericht-----
> > > > Van: Xavier Hanin [mailto:xavier.hanin@gmail.com]
> > > > Verzonden: maandag 9 juli 2007 19:47
> > > > Aan: ivy-dev@incubator.apache.org
> > > > Onderwerp: 2.0.0 alpha 2 release
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I'm happy to say that all issues planned for 2.0 alpha 2 are
> resolved!
> > > > The last task is to update the release notes and cut the release.
> I'll
> > > > do that tomorrow morning and start a vote if nobody's object before
> > > > (you'll still have time to object during the vote :-)). The purpose
> of
> > > > this release is to provide a checkpoint about our progress in the
> > > > development of 2.0. This version still not has an emphasis on
> quality.
> > > >
> > > > Xavier
> > > > --
> > > > Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/
> > > > http://incubator.apache.org/ivy/ http://www.xoocode.org/
> > > >
> > > > Disclaimer:
> > > > This message contains information that may be privileged or
> > confidential
> > > > and is the property of Sogeti Nederland B.V. or its Group members.
> It
> > is
> > > > intended only for the person to whom it is addressed. If you are not
> > the
> > > > intended recipient, you are not authorized to read, print, retain,
> > copy,
> > > > disseminate, distribute, or use this message or any part thereof. If
> > you
> > > > receive this message in error, please notify the sender immediately
> > and
> > > > delete all copies of this message.
> > > >
> > >
> > >
> > >
> > > --
> > > Xavier Hanin - Independent Java Consultant
> > > http://xhab.blogspot.com/
> > > http://incubator.apache.org/ivy/
> > > http://www.xoocode.org/
> > >
> >
>
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://incubator.apache.org/ivy/
> http://www.xoocode.org/
>


[prev in list] [next in list] [prev in thread] [next in thread]