Back in April, we announced a change to the way we were going to be working moving forward, so we wanted to give you a quick update on how that’s all going. Quick recap: we decided to try moving all of our feature requests, bug reports, and tasks into Github, versus having them siloed in the helpdesk, Shortcut, Rollbar, Github, Discord, email, Mastodon, and so on. This meant: going through...
If you’re watching the Snipe-IT repo closely (which it’s totally fine if you aren’t – go be a normal person! Do normal people stuff!), you will have noticed some changes recently. Lots of older issues being closed, lots of them being resurfaced, lots of new categorizing of things, etc. We’ve decided to try something new for us. It’s going to get weird, a little...
Important! You should not have to do anything to continue using and upgrading Snipe-IT. Github’s redirects should handle everything for you. Don’t worry – this won’t affect you much (if at all), we’re just letting you know in case you have any bespoke integrations, or in case you get freaked out that the namespace has changed. Why the move? Moving the repo to...
As you likely know, we have two public demos of Snipe-IT, the version that’s on the master branch, and the version that’s on develop. We’ve had these public demos for years, so we’ve learned a thing or two about how people behave on public demos. 99% of the time, folks use the demos for their intended purpose, but that 1% can make things really annoying. We’ve seen...
As you likely know by now, v7 of Snipe-IT dropped a few weeks ago. Those of you who have been with us for a long time know that those major version releases can be pretty tough. When you’re hoisting the underlying framework by several versions, upgrading dependencies, plus adding features, things can get messy fast. Making sure that we cover as many possible versions as possible for our...