You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Alexis Midon <mi...@intalio.com> on 2009/04/17 03:23:19 UTC
Preparing release 1.3.1
Hi everyone,
we currently have 119 closed or resolved issues [1], I think it's time we
prepare a release of the 1.X branch, that would be the release 1.3.1.
Before going further we need to do some trillage in the jira issues i.e.
closing the resolved issues [2], moving the opened issues [3] to the next
version, 1.3.2. In this process your help would be appreciated for the
issues you're familiar with.
Of course, feel free to speak up if you have concerns, objections, blockers,
etc
Alexis
[1]
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=5&status=6&fixfor=12313680&sorter/field=issuekey&sorter/order=ASC&sorter/field=summary&sorter/order=ASC&sorter/field=status&sorter/order=DESC
[2]
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=5&fixfor=12313680&sorter/field=issuekey&sorter/order=DESC
[3]
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=1&status=3&status=4&fixfor=12313680&sorter/field=issuekey&sorter/order=DESC
Re: Preparing release 1.3.1
Posted by Ciaran <ci...@gmail.com>.
Awesome, thanks :)
-cj,
On Sat, Apr 18, 2009 at 12:06 AM, Alexis Midon <mi...@intalio.com> wrote:
> https://issues.apache.org/jira/browse/ODE-580 fixed.
>
> On Fri, Apr 17, 2009 at 7:51 AM, Alex Boisvert <bo...@intalio.com>
> wrote:
>
> > Agreed. I think we should address both ODE-580 and ODE-576 before we
> > release
> > 1.3.1.
> >
> > alex
> >
> >
> > 2009/4/16 Ciaran <ci...@gmail.com>
> >
> > > Ok, so I'm horribly biased, but if ODE-580 & ODE-576 (neither one of
> > which
> > > appears on list 3 as they don't have a Fix/Versions set) were able to
> > make
> > > it into 1.3.1 I'd actually be able to use that release ;) (Without them
> I
> > > lose memory on long running executions and they do currently have
> patches
> > > against them to resolve these leaks)
> > >
> > > (Obviously I appreciate the name of the game is *Reducing* the set of
> all
> > > things going into 1.3.1, but it would be nice to get a version out with
> > no
> > > memory leaks ? :)
> > >
> > > Sry!
> > > - Cj.
> > >
> > >
> > > On Fri, Apr 17, 2009 at 2:48 AM, Matthieu Riou <
> matthieu.riou@gmail.com
> > > >wrote:
> > >
> > > > On Thu, Apr 16, 2009 at 6:23 PM, Alexis Midon <mi...@intalio.com>
> > wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > we currently have 119 closed or resolved issues [1], I think it's
> > time
> > > we
> > > > > prepare a release of the 1.X branch, that would be the release
> 1.3.1.
> > > > > Before going further we need to do some trillage in the jira issues
> > > i.e.
> > > > > closing the resolved issues [2], moving the opened issues [3] to
> the
> > > next
> > > > > version, 1.3.2. In this process your help would be appreciated for
> > the
> > > > > issues you're familiar with.
> > > > >
> > > > > Of course, feel free to speak up if you have concerns, objections,
> > > > > blockers,
> > > > > etc
> > > > >
> > > >
> > > > Thanks a lot for taking over the release :)
> > > >
> > > >
> > > > >
> > > > > Alexis
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=5&status=6&fixfor=12313680&sorter/field=issuekey&sorter/order=ASC&sorter/field=summary&sorter/order=ASC&sorter/field=status&sorter/order=DESC
> > > > > [2]
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=5&fixfor=12313680&sorter/field=issuekey&sorter/order=DESC
> > > > > [3]
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=1&status=3&status=4&fixfor=12313680&sorter/field=issuekey&sorter/order=DESC
> > > > >
> > > >
> > >
> >
>
Re: Preparing release 1.3.1
Posted by Alexis Midon <mi...@intalio.com>.
https://issues.apache.org/jira/browse/ODE-580 fixed.
On Fri, Apr 17, 2009 at 7:51 AM, Alex Boisvert <bo...@intalio.com> wrote:
> Agreed. I think we should address both ODE-580 and ODE-576 before we
> release
> 1.3.1.
>
> alex
>
>
> 2009/4/16 Ciaran <ci...@gmail.com>
>
> > Ok, so I'm horribly biased, but if ODE-580 & ODE-576 (neither one of
> which
> > appears on list 3 as they don't have a Fix/Versions set) were able to
> make
> > it into 1.3.1 I'd actually be able to use that release ;) (Without them I
> > lose memory on long running executions and they do currently have patches
> > against them to resolve these leaks)
> >
> > (Obviously I appreciate the name of the game is *Reducing* the set of all
> > things going into 1.3.1, but it would be nice to get a version out with
> no
> > memory leaks ? :)
> >
> > Sry!
> > - Cj.
> >
> >
> > On Fri, Apr 17, 2009 at 2:48 AM, Matthieu Riou <matthieu.riou@gmail.com
> > >wrote:
> >
> > > On Thu, Apr 16, 2009 at 6:23 PM, Alexis Midon <mi...@intalio.com>
> wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > we currently have 119 closed or resolved issues [1], I think it's
> time
> > we
> > > > prepare a release of the 1.X branch, that would be the release 1.3.1.
> > > > Before going further we need to do some trillage in the jira issues
> > i.e.
> > > > closing the resolved issues [2], moving the opened issues [3] to the
> > next
> > > > version, 1.3.2. In this process your help would be appreciated for
> the
> > > > issues you're familiar with.
> > > >
> > > > Of course, feel free to speak up if you have concerns, objections,
> > > > blockers,
> > > > etc
> > > >
> > >
> > > Thanks a lot for taking over the release :)
> > >
> > >
> > > >
> > > > Alexis
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=5&status=6&fixfor=12313680&sorter/field=issuekey&sorter/order=ASC&sorter/field=summary&sorter/order=ASC&sorter/field=status&sorter/order=DESC
> > > > [2]
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=5&fixfor=12313680&sorter/field=issuekey&sorter/order=DESC
> > > > [3]
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=1&status=3&status=4&fixfor=12313680&sorter/field=issuekey&sorter/order=DESC
> > > >
> > >
> >
>
Re: Preparing release 1.3.1
Posted by Alex Boisvert <bo...@intalio.com>.
Agreed. I think we should address both ODE-580 and ODE-576 before we release
1.3.1.
alex
2009/4/16 Ciaran <ci...@gmail.com>
> Ok, so I'm horribly biased, but if ODE-580 & ODE-576 (neither one of which
> appears on list 3 as they don't have a Fix/Versions set) were able to make
> it into 1.3.1 I'd actually be able to use that release ;) (Without them I
> lose memory on long running executions and they do currently have patches
> against them to resolve these leaks)
>
> (Obviously I appreciate the name of the game is *Reducing* the set of all
> things going into 1.3.1, but it would be nice to get a version out with no
> memory leaks ? :)
>
> Sry!
> - Cj.
>
>
> On Fri, Apr 17, 2009 at 2:48 AM, Matthieu Riou <matthieu.riou@gmail.com
> >wrote:
>
> > On Thu, Apr 16, 2009 at 6:23 PM, Alexis Midon <mi...@intalio.com> wrote:
> >
> > > Hi everyone,
> > >
> > > we currently have 119 closed or resolved issues [1], I think it's time
> we
> > > prepare a release of the 1.X branch, that would be the release 1.3.1.
> > > Before going further we need to do some trillage in the jira issues
> i.e.
> > > closing the resolved issues [2], moving the opened issues [3] to the
> next
> > > version, 1.3.2. In this process your help would be appreciated for the
> > > issues you're familiar with.
> > >
> > > Of course, feel free to speak up if you have concerns, objections,
> > > blockers,
> > > etc
> > >
> >
> > Thanks a lot for taking over the release :)
> >
> >
> > >
> > > Alexis
> > >
> > > [1]
> > >
> > >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=5&status=6&fixfor=12313680&sorter/field=issuekey&sorter/order=ASC&sorter/field=summary&sorter/order=ASC&sorter/field=status&sorter/order=DESC
> > > [2]
> > >
> > >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=5&fixfor=12313680&sorter/field=issuekey&sorter/order=DESC
> > > [3]
> > >
> > >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=1&status=3&status=4&fixfor=12313680&sorter/field=issuekey&sorter/order=DESC
> > >
> >
>
Re: Preparing release 1.3.1
Posted by Ciaran <ci...@gmail.com>.
Ok, so I'm horribly biased, but if ODE-580 & ODE-576 (neither one of which
appears on list 3 as they don't have a Fix/Versions set) were able to make
it into 1.3.1 I'd actually be able to use that release ;) (Without them I
lose memory on long running executions and they do currently have patches
against them to resolve these leaks)
(Obviously I appreciate the name of the game is *Reducing* the set of all
things going into 1.3.1, but it would be nice to get a version out with no
memory leaks ? :)
Sry!
- Cj.
On Fri, Apr 17, 2009 at 2:48 AM, Matthieu Riou <ma...@gmail.com>wrote:
> On Thu, Apr 16, 2009 at 6:23 PM, Alexis Midon <mi...@intalio.com> wrote:
>
> > Hi everyone,
> >
> > we currently have 119 closed or resolved issues [1], I think it's time we
> > prepare a release of the 1.X branch, that would be the release 1.3.1.
> > Before going further we need to do some trillage in the jira issues i.e.
> > closing the resolved issues [2], moving the opened issues [3] to the next
> > version, 1.3.2. In this process your help would be appreciated for the
> > issues you're familiar with.
> >
> > Of course, feel free to speak up if you have concerns, objections,
> > blockers,
> > etc
> >
>
> Thanks a lot for taking over the release :)
>
>
> >
> > Alexis
> >
> > [1]
> >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=5&status=6&fixfor=12313680&sorter/field=issuekey&sorter/order=ASC&sorter/field=summary&sorter/order=ASC&sorter/field=status&sorter/order=DESC
> > [2]
> >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=5&fixfor=12313680&sorter/field=issuekey&sorter/order=DESC
> > [3]
> >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=1&status=3&status=4&fixfor=12313680&sorter/field=issuekey&sorter/order=DESC
> >
>
Re: Preparing release 1.3.1
Posted by Matthieu Riou <ma...@gmail.com>.
On Thu, Apr 16, 2009 at 6:23 PM, Alexis Midon <mi...@intalio.com> wrote:
> Hi everyone,
>
> we currently have 119 closed or resolved issues [1], I think it's time we
> prepare a release of the 1.X branch, that would be the release 1.3.1.
> Before going further we need to do some trillage in the jira issues i.e.
> closing the resolved issues [2], moving the opened issues [3] to the next
> version, 1.3.2. In this process your help would be appreciated for the
> issues you're familiar with.
>
> Of course, feel free to speak up if you have concerns, objections,
> blockers,
> etc
>
Thanks a lot for taking over the release :)
>
> Alexis
>
> [1]
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=5&status=6&fixfor=12313680&sorter/field=issuekey&sorter/order=ASC&sorter/field=summary&sorter/order=ASC&sorter/field=status&sorter/order=DESC
> [2]
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=5&fixfor=12313680&sorter/field=issuekey&sorter/order=DESC
> [3]
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&status=1&status=3&status=4&fixfor=12313680&sorter/field=issuekey&sorter/order=DESC
>