All I wanted initially was to be able to get a description of what each series provided so that when I jump from my version to the latest, I can see what's going on. Then you guys wanted to expose the matrix of compatibilities as e.g. people do consume Search with a given version of ORM.
With that being said, here is what I think are the series with value to users today: * Search: 5.8 (latest), 5.6 (ORM 5.0/5.1), maybe whatever the version in WF is * Validator: 6.0 (latest), maybe whatever the version in WF is * OGM: 5.2 (dev), 5.1 (stable) * ORM: 5.2, 5.1, maybe the WF version if it's not 5.1 As a user, I still need to be able to go to a given series page to understand what was done (see my initial use case). But they can be in a older series section in small vs big boxes. BTW tools has a Downloads link, not Releases. Emmanuel On Fri 17-09-22 17:03, Yoann Rodiere wrote: >Ok, this will never end... It was good to merge less than 24h ago and now >you're arguing against the very point of this work: provide users with more >information regarding each series, so that they know what's new. (see the >first email by Emmanuel) > >Please make concrete, exhaustive proposals. From what I understand, your >concerns could be addressed with only simple changes to the menu (hide >older series, add an "archived series" entry), but I don't know what to >think anymore. > > >Yoann Rodière >Hibernate NoORM Team >yo...@hibernate.org > >On 22 September 2017 at 16:49, Sanne Grinovero <sa...@hibernate.org> wrote: > >> After some chats and a night of sleep on this, I think we need to stop >> obsessing about guiding people into the choice among multiple minor >> versions: it's hard enough that they have to pick a project. >> >> We need to encourage people to use the latest versions and we need to >> send a clear, strong message about this, no middle ground fiddling >> with names and definitions >> >> We can give them a choice between using the latest stable vs the >> latest development, but beyond this we're giving too much choice. >> >> Yet I do believe we should make it "not-hard" for people looking for >> details of other recent versions; could we consider them all >> "archived" ? Some drop downs on key areas like the ones in ORM today >> would still be welcome to make it easy to find - but let's remove the >> version choice from the "primary navigation path". >> >> There are some exceptional cases coming to mind which would need some >> mitigation; for example the fact that OGM won't work with the latest >> Search and ORM releases! >> But there are better solutions than to pollute the website experience >> by making the matching versions too visible, for example bundle it >> with OGM, link to the right versions from the OGM pages, or have the >> modules eventually pull-in the required dependencies, etc... >> (technical details irrelevant in this context). >> >> Thanks, >> Sanne >> >> >> >> >> On 22 September 2017 at 12:21, Guillaume Smet <guillaume.s...@gmail.com> >> wrote: >> > On Thu, Sep 21, 2017 at 6:45 PM, Sanne Grinovero <sa...@hibernate.org> >> > wrote: >> >> >> >> *IF* you are willing to improve a minor point: I didn't expect the >> >> "Releases" menu to be expanded when not being in any of these >> >> sections. >> > >> > >> > Let's keep that one for another time. >> > >> >> >> >> Related: I wouldn't highlight both the current release and the >> >> "Releases" label, the shading looks odd and misaligned. >> > >> > >> > Yoann fixed it. >> > >> > Could we push that version to production and iterate after if required? >> > >> > It's a tad better than what we have now and I don't see a reason to >> delay it >> > more. >> > >> > Emmanuel? >> > >> > -- >> > Guillaume >> > >> >_______________________________________________ >hibernate-dev mailing list >hibernate-dev@lists.jboss.org >https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
