Jump to content

Community

Colonel_mortis

+Clients
  • Posts

    1,361
  • Joined

  • Last visited

  • Days Won

    4

Reputation Activity

  1. Like
    Colonel_mortis got a reaction from Matt in Anonymous Posting   
    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. Like
    Colonel_mortis got a reaction from sobrenome in Anonymous Posting   
    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).
  3. Like
    Colonel_mortis got a reaction from SammyS in Anonymous Posting   
    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).
  4. Like
    Colonel_mortis got a reaction from Runar in Anonymous Posting   
    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.
  5. Like
    Colonel_mortis got a reaction from Matt in Anonymous Posting   
    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.
  6. Like
    Colonel_mortis got a reaction from CodingJungle in Anonymous Posting   
    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.
  7. Confused
    Colonel_mortis got a reaction from sobrenome in Anonymous Posting   
    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.
  8. Like
    Colonel_mortis got a reaction from Matt in Anonymous Posting   
    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
  9. Like
    Colonel_mortis got a reaction from Matt in 4.5: Topic view summary and more   
    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!
  10. Like
    Colonel_mortis got a reaction from SC36DC in 4.5: Topic view summary and more   
    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!
  11. Like
    Colonel_mortis got a reaction from Daniel F in 4.5: Topic view summary and more   
    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!
  12. Thanks
    Colonel_mortis got a reaction from optinap in New: Fluid Forum View   
    This is actually a really interesting feature. However,
    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