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? The rest of the tickets (#503, #509, #540) look like they are fixed, but have not been closed/reviewed yet. Can those who worked on them please correct me, if there are still some things that have not been fixed. In short, we are close, but not there yet. If there is anything I can do to speed up resolving these tickets, please let me know. --- Ticket quick links: #201 - https://issues.apache.org/bloodhound/ticket/201 #444 - https://issues.apache.org/bloodhound/ticket/444 #446 - https://issues.apache.org/bloodhound/ticket/446 #461 - https://issues.apache.org/bloodhound/ticket/461 #501 - https://issues.apache.org/bloodhound/ticket/501 #503 - https://issues.apache.org/bloodhound/ticket/503 #509 - https://issues.apache.org/bloodhound/ticket/509 #540 - https://issues.apache.org/bloodhound/ticket/540 On Fri, Jun 21, 2013 at 9:59 AM, Matevž Bradač <[email protected]> wrote: > > On 21. Jun, 2013, at 9:46, Anze Staric wrote: > >> On Fri, Jun 21, 2013 at 9:23 AM, Matevž Bradač <[email protected]> wrote: >> [...] >>> IMO, if the default_product does not exist, we should: >>> 1. check whether the preset default (@) exists and use that >>> 2. if @ is not available, use the first product in the DB >>> (and a warning to the user would also be nice) >> >> What about simply showing and error with message along the lines of >> >> Cannot create a ticket in non-existant product (product_prefix). >> Please select different product or [link_to_create_new_product | >> create product_prefix]. >> >> (assuming that user can select in which product the ticket gets created in). > > Yes, in that case it would make sense. However this implies #569 is fixed > first, but once that is done it will be impossible to trigger #568 anyhow > if my understanding is correct. That is, the product dropdown will list all > products from the DB (not including the default_product, since it's not > stored in the DB), so the user will not be able to select the default_product > at all.
