Hi, no Problem Rupert - I will reflect the latest changes. I did some attempts to cut the release and already created a release tag but I also need to commit a few changes.
Anyway - a code freeze date would be a good idea for the 0.12 branch. This would be the deadline for creating a release tag from the branch. What date would you suggest? This Friday, Feb 7th? Best, - Fabian 2014-02-04 Rupert Westenthaler <rupert.westentha...@gmail.com>: > Hi (again), > > FYI, I did an other bug fixing commit [1] for STANBOL-1275 to the 0.12 branch > > best > Rupert > > [1] http://svn.apache.org/r1564363 > > On Tue, Feb 4, 2014 at 2:52 PM, Rupert Westenthaler > <rupert.westentha...@gmail.com> wrote: >> Hi Fabian, >> >> I have only today noticed that you have already remove the SNAPSHOT >> from the modules. Should we consider the 0.12.0 branch as frozen? >> >> Before that I made a commit [1] fixing STANBOL-1272 and also marked >> this issue as fixed in 0.12.0. >> >> So if this commit does not make it into this release, I would need to >> update the issue. >> >> best >> Rupert >> >> >> [1] http://svn.apache.org/r1563781 >> >> On Fri, Jan 31, 2014 at 6:57 PM, Rupert Westenthaler >> <rupert.westentha...@gmail.com> wrote: >>> On Fri, Jan 31, 2014 at 3:28 PM, Fabian Christ >>> <christ.fab...@googlemail.com> wrote: >>>> Hi, >>>> >>>> thanks Rupert for having a look. >>>> >>>> Is https://issues.apache.org/jira/browse/STANBOL-1182 also resolved? >>> >>> >>> yep. Forgot to close ... done >>> >>> Best >>> Rupert >>> >>> >>>> >>>> Best, >>>> - Fabian >>>> >>>> 2014-01-31 Rupert Westenthaler <rupert.westentha...@gmail.com>: >>>>> Hi Fabian, >>>>> >>>>> >>>>> >>>>> On Fri, Jan 31, 2014 at 9:32 AM, Fabian Christ >>>>> <christ.fab...@googlemail.com> wrote: >>>>>> Hi, >>>>>> >>>>>> there are two unresolved issues marked for the 0.12 release in JIRA. >>>>>> >>>>>> https://issues.apache.org/jira/browse/STANBOL-1139 >>>>>> https://issues.apache.org/jira/browse/STANBOL-1254 >>>>> >>>>> This does not affect 0.12 anymore as I have reverted the changes with >>>>> http://svn.apache.org/r1559065 and reto has reverted the change with >>>>> http://svn.apache.org/r1560050 in trunk. So I closed this one with >>>>> resolution won't fix. >>>>> >>>>> IMO we can go for the 0.12 release >>>>> >>>>> best >>>>> Rupert >>>>> >>>>>> >>>>>> Could these issues be postponed, i.e. ignored for the 0.12 release, or >>>>>> what is their status? >>>>>> >>>>>> Best, >>>>>> - Fabian >>>>>> >>>>>> -- >>>>>> Fabian >>>>>> http://twitter.com/fctwitt >>>>> >>>>> >>>>> >>>>> -- >>>>> | Rupert Westenthaler rupert.westentha...@gmail.com >>>>> | Bodenlehenstraße 11 ++43-699-11108907 >>>>> | A-5500 Bischofshofen >>>> >>>> >>>> >>>> -- >>>> Fabian >>>> http://twitter.com/fctwitt >>> >>> >>> >>> -- >>> | Rupert Westenthaler rupert.westentha...@gmail.com >>> | Bodenlehenstraße 11 ++43-699-11108907 >>> | A-5500 Bischofshofen >> >> >> >> -- >> | Rupert Westenthaler rupert.westentha...@gmail.com >> | Bodenlehenstraße 11 ++43-699-11108907 >> | A-5500 Bischofshofen > > > > -- > | Rupert Westenthaler rupert.westentha...@gmail.com > | Bodenlehenstraße 11 ++43-699-11108907 > | A-5500 Bischofshofen -- Fabian http://twitter.com/fctwitt
