On Tue, Jul 2, 2013 at 11:43 AM, Ryan Ollos <[email protected]> wrote:
> On Tue, Jul 2, 2013 at 11:28 AM, Olemis Lang <[email protected]> wrote: > >> On 7/2/13, Ryan Ollos <[email protected]> wrote: >> > On Tue, Jul 2, 2013 at 8:24 AM, Anze Staric <[email protected]> >> wrote: >> > >> >> It's been about two weeks since we started closing tickets that should >> >> be resolved before the release, but some are still open. If I >> >> understood Ryan correctly, #201, #444, #461 and #501 were close to >> >> being resolved two weeks ago. Any status updates? >> >> >> >> #446 seems to be fixed in trac. Are we updating the trac version in >> >> our repository before the release? >> >> >> >> I recommend not to do so and defer this to Release 7 or 8 in spite of >> spending some time testing what'd happen with vendor branch update. >> Besides, I guess the task should not be a trivial task these days ... >> > > #446 is fixed in Trac, but the changes are entirely isolated to the > templates so whether it is or is not fixed in Trac has no impact on our > ability to fix it in Bloodhound. I prepared the change a while ago and was > waiting for feedback on the Trac ticket to proceed - that never happened, > and I've since pushed the change to the Trac core. If I find time to > adequately test the change in Bloodhound today I will push it, otherwise I > will defer until the next release. > > In general though, I think our policy is to only update Trac when there is > a stable release. I'm hoping we can get Trac 1.0.2 released by the end of > July. > I need to take another close look at #569 since I stumbled across some cases in which the View/Edit link doesn't direct to the correct product. I had previously thought this issue was fixed. After I get that sorted out in the morning, I will finally proceed with the release.
