Quick update: I now have a fix for ISIS-1132, and ISIS-1396 was already fixed. So I'm going to cut a 1.12.2 release with these two fixes.
Meantime, will keep 1.13.0-SNAPSHOT in development, with a view of a release to follow in the next week or two. Thx Dan On 1 June 2016 at 12:54, Stephen Cameron <[email protected]> wrote: > Thanks Dan, I'll try to assist in the testing of 1.13.0-SNAPSHOT where I > can. > > > > On Wed, Jun 1, 2016 at 5:30 PM, Dan Haywood <[email protected]> > wrote: > > > Thanks for this feedback, Steve. > > > > Obviously I'll take a look at ISIS-1132. Up until now that behaviour was > > puzzling but not a blocker; but Boris raised the ticket with steps to > > reproduce, so I'll take a look. > > > > With respect to stabilization, we could perhaps put a 1.12.2 out, though > > 1.13.0 is quite close to release also. Unlike in 1.12.x where there were > > lots of visible changes, the 1.13.0 is mostly internal, tidying up some > of > > the nastier kludges and simplifying/refactoring the codebase as I can. > So > > consolidation is the current name of the game. > > > > Will report back on ISIS-1132 before too long, hopefully. > > > > thx > > Dan > > > > > > > > > > > > On 31 May 2016 at 23:46, Stephen Cameron <[email protected]> > > wrote: > > > > > Hi, > > > > > > I want to suggest that the 1.12.1 release is not currently of > production > > > quality and that a decision should be made by the development team as > to > > > how to address that. > > > > > > Maybe there is a case for consolidation of 1.12 before release of 1.13 > or > > > else a recommendation to skip 1.12 and help with 1.13 release testing? > > > > > > There is a significant issue ISIS-1396 [1] that has been resolved in > > > 1.13.0-SNAPSHOT, this is my primary concern. I was going to say to > users > > > just refresh the page to see the link titles, but I have discovered > > another > > > known issue ISIS-1132 [2] that seems to me quite serious, where > datetimes > > > don't display correctly after updates. > > > > > > Also, I've now found a similar bug to 1132, where I created a > mass-update > > > action (after the edit mode discussion), but this doesn't work as some > > > property values (strings not datetimes) are not updated correctly in > the > > > viewer. This is quite bizarre and I was sure I had an problem in my > code, > > > but I cannot find one. Updates require a database lookup, which may > > > explain. > > > > > > Hoping this not taken as criticism. > > > > > > Steve > > > > > > [1] https://issues.apache.org/jira/browse/ISIS-1396 > > > <https://issues.apache.org/jira/browse/ISIS-1396> > > > [2] https://issues.apache.org/jira/browse/ISIS-1132 > > > <https://issues.apache.org/jira/browse/ISIS-1132> > > > > > >
