Jump to content
You're invited! Join our 4.6 Live Event on ZOOM 6/24 ×

Community

Colonel_mortis

+Clients
  • Posts

    1,380
  • Joined

  • Last visited

  • Days Won

    4

 Content Type 

Profiles

Downloads

IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Forums

Store

Entry Comments posted by Colonel_mortis

  1. On 11/17/2020 at 1:46 PM, Matt said:

    We're looking to find the right balance. Too many incremental releases (say weekly) and you push that burden onto admins to constantly update (and check compatibility, etc), too few and the release gets bigger.

    How about doing patch releases on a regular schedule, such as on the first Tuesday of each month? That way, people can predict and plan for the work that will be needed (which for patch releases, with no new features or breaking changes, should be pretty minimal), and we get a reasonable cadence of bug fixes.

    Features should be released in minor releases (4.6 etc). Personally, I would be happy to see more frequent but smaller feature releases, say every 6 months with a couple of changes each time, as long as the scope of a release is fairly clear (ie. there are no breaks in a patch release like 4.5.5) and it doesn't affect the cadence of bug fixes (so we're not waiting 1.5mo and counting for bug fixes).

  2. 8 hours ago, Matt said:

    We are trying to break away from large monolithic releases spaced 12-18 months apart which leaves long periods of time devoid of any significant new functionality.

    In terms of demand for this feature, it's been requested a lot for our enterprise communities for quite some time.

    I am broadly in favour of moving away from monolithic releases, but I would much prefer that you up the cadence of minor releases than push features and especially breaking changes into patch/point releases.

  3. 8 hours ago, Daniel F said:

    breaking changes

    Why are there breaking changes to add a fairly obscure [1] feature in a point release? I thought IPS had grown out of that. Are you going to update the marketplace supported versions field to have 4.5.0-4.5.4 and 4.5.5-4.5.x?

    [1] the third party plugin that provided this has 58 purchases, or approximately 0.2% of communities, and you (rightly, ish) dismissed another feature suggestion for only having 1.8% install coverage

  4. I usually complain that most of your new features have great concepts, but just don't get delivered properly and end up not being useful. There is of course still plenty of time, but I have been very pleasantly surprised by how well implemented this looks, and I'm actually looking forward to rolling this out on my site!

    Thank you, and please keep it up!

  5. Quote

    When a member searches, their identity is converted into a unique key that cannot be reversed to identify the member. This allows us to track a single member's search usage over many search sessions without being able to link it to a specific member account.

    Suspicious Someone GIF

    I don't know what you've come up with, so maybe it is legitimately irreversible (a random value stored in a cookie would probably be good). But in the world of GDPR, md5(member_id) (or anything else that I could easily reverse with an SQL query) doesn't go far enough to be described as anonymised, and I would be very cautious of advertising it as such.

  6. This is actually a really interesting feature. However,

    Quote

    Guests are not permitted to change between views.

    I do think it would be good to allow them to change views, and have it stored in a cookie, just like guests can change theme, language and activity stream view.

×
×
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy