openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Curtis <curti...@gmail.com>
Subject Re: release preparations for 2.3.0
Date Tue, 29 Oct 2013 14:59:10 GMT
Sure, I get that case... but I'd bet that many of the JIRAs that are
unresolved, with no committed code, and fix version of 2.3.0 haven't really
been resolved.


On Tue, Oct 29, 2013 at 9:47 AM, Mark Struberg <struberg@yahoo.de> wrote:

> hmmm I'd let the fix version.
> This often happens if a fix got applied committed as part of another JIRA.
> But still the reported issue got fixed.
> The same happens if a unit test shows that the reported bug already got
> fixed in the meantime.
>
> Imo those cases should still get tagged as 'fixed in ...'
>
> LieGrue,
> strub
>
>
>
>
> ----- Original Message -----
> > From: Kevin Sutter <kwsutter@gmail.com>
> > To: dev@openjpa.apache.org
> > Cc:
> > Sent: Tuesday, 29 October 2013, 15:30
> > Subject: Re: release preparations for 2.3.0
> >
> > Yes, you are probably right. If no code has been committed any release or
> > trunk, then there should be no "fix version", just the "affects
> > version".
> >
> >
> >
> > On Tue, Oct 29, 2013 at 9:16 AM, Rick Curtis <curtisr7@gmail.com> wrote:
> >
> >>  Should we just remove the 'Fix Version/s' attribute if it is set to
> > 2.3.0
> >>  when no code has been committed? ie :
> >>  https://issues.apache.org/jira/browse/OPENJPA-1988
> >>
> >>
> >>  On Tue, Oct 29, 2013 at 9:10 AM, Kevin Sutter <kwsutter@gmail.com>
> > wrote:
> >>
> >>  > Thanks, Mark.  I just got rid of three of the JIRAs from your query
> > and
> >>  > working on another one with Jody.  There may be others that should or
> >>  could
> >>  > be cleaned up, but I picked the easy ones first...  :-)  I hate to
> > just
> >>  > carry over JIRAs from one release to another to another...  Some of
> > these
> >>  > should probably just be returned as "won't fix" (similar
> > to the ones I
> >>  did
> >>  > already).  I'll let others take a run through the query and see if
> > there
> >>  > are candidates.
> >>  >
> >>  > Thanks!
> >>  > Kevin
> >>  >
> >>  >
> >>  > On Tue, Oct 29, 2013 at 3:27 AM, Mark Struberg
> > <struberg@yahoo.de>
> >>  wrote:
> >>  >
> >>  > > Hi!
> >>  > >
> >>  > > Could you please walk through the unresolved OpenJPA-2.3.0 issues
> > and
> >>  set
> >>  > > those who you doubt should be fixed already to
> > 'resolved'?
> >>  > >
> >>  > >
> >>  > >
> >>  >
> >>
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENJPA%20AND%20fixVersion%20%3D%20%222.3.0%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> >>  > >
> >>  > > I hope to start with the actual release task either tonight or
> > tomorrow
> >>  > > morning.
> >>  > > Means I gonna  send another mail in 15 hours and then will
> > transit the
> >>  > > still unresolved issues to 2.4.0.
> >>  > >
> >>  > > There is also another thing which I like to do: finally get rid
> > of all
> >>  > the
> >>  > > bad tabs and unused imports in 2.3.x and trunk.
> >>  > > See OPENJPA-2200. I will _not_ change any lines other than tabs
> > and
> >>  > unused
> >>  > > imports so far.
> >>  > > Patches should thus still apply fine even across older versions.
> >>  > >
> >>  > > LieGrue,
> >>  > > strub
> >>  > >
> >>  >
> >>
> >>
> >>
> >>  --
> >>  *Rick Curtis*
> >>
> >
>



-- 
*Rick Curtis*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message