couple of additional items: - FC-176 [ fortress-web ] spring security page security broken - FC-190 Duplicate setter methods in Group Object
> On Oct 25, 2016, at 10:19 AM, Shawn McKinney <[email protected]> wrote: > > Hello, > > Within the next few days I will start processing another release. Unless we > find any major bugs, this will likely be the last of the year. > > Here’s list of JIRA issues resolved thus far: > - FC-181 Multitenancy for Realm and Web > - FC-183 [ fortress-core ] Use Apache IANA Number of OID > - FC-144 Ability to assign groups to roles > - FC-116 Need the ability to get user specific attributes for fine grained > access determinations > - FC-194 Change password representation from a char[] to a String > - FC-193 remove @XmlElement(nillable = true) from all fortress entities > - FC-180 [ fortress-web ] Selenium tests to also use other drivers > - FC-179 [ fortress-web ] Firefox 48 broke Selenium tests > - FC-182 [ fortress-core ] AdminRoleP.removeOccupant not using tenantId > - FC-191 sonarqube code cleanup > - FC-192 [ fortress-core ] problems with config system > > We opted for a 2.0 label because FC-183 and FC-194 have potential to break > existing contracts for apis and schemas. > http://mail-archives.apache.org/mod_mbox/directory-fortress/201609.mbox/%3C687C38E2-F786-41C7-9D1B-08D68D352761%40apache.org%3E > > There are no plans to continue work down a 1.0 codepath. All work will > commence on a 2.0 path with a GA release anticipated sometime early in ’17. > > Let me know if you have questions or concerns about any of this. > > Thanks, > Shawn > >
