What do we do with wicket-experimental modules on the 6.0.1 release? As far as my understanding of semantic version goes, 6.0.1 should only contain bug fixes, 6.1 will be the next version with new features, but still api-compatible. Experimental modules, however, are all versioned below 1.0, allowing any change, because semver starts at 1.0. I did not break the API, but you could see this as a new feature (multi-tab support).
IMHO, 6.1.0 should be the next release, where 6.0.1 will only contain some bugfixes. For example, selenium releases a new 2.x.0 every few weeks, and only release a 2.x.1 when a critical bug is found. This also makes it easier to cope with the experimental modules, because we can simply release them with 6.1 and skip 6.0.1. Best regards, Emond On Tue, Sep 4, 2012 at 8:41 PM, Martin Grigorov (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/WICKET-4729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Martin Grigorov updated WICKET-4729: > ------------------------------------ > > Fix Version/s: (was: 6.1.0) > 6.0.1 > >> atmosphere example will stop working if opening the same url in a different >> tab in the same browser >> --------------------------------------------------------------------------------------------------- >> >> Key: WICKET-4729 >> URL: https://issues.apache.org/jira/browse/WICKET-4729 >> Project: Wicket >> Issue Type: Bug >> Components: wicket-atmosphere >> Affects Versions: 6.0.0-beta3 >> Reporter: Sean Lin >> Assignee: Emond Papegaaij >> Fix For: 6.0.1 >> >> >> If the url of a running atmosphere example is copied and then opened in a >> different tab while the old one left open in the same browser, >> i.e. there are two atmosphere examples of the same url opened at the same >> time in a browser, >> one of them will stop working. >> I found the cause of this problem is that trackingPages in EventBus is using >> a BiMap. >> If there are different tracking-ids mapping to the same PageKey, one of the >> map entry will be removed. >> The simple solution would be replacing the BiMap with HashMap, but I think >> there might be reasons why BiMap is used here. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira
