As 2013 ramps up, we wanted to take a moment to reflect and thank you for a successful 2012. Below are some notable improvements our team accomplished in 2012 and a preview of what’s to come in 2013.
- Released the tickets Planner view which provides a simple, lightweight way to create, prioritize, and work on tasks
- Improved the way teams work on tickets with an updated ticket layout
- Improved team collaboration with @mentions, in-stream messaging, and more fine-grained email notifications
- Became the first provider of Perforce repositories on-demand
- Released advanced merge request for Git and later released similar code review and merge for Subversion users
- Released a new API and developer documentation site
- Built Jenkins plugins for Assembla team authentication and triggering builds
- Created a new support site to help user find documentation and interact with Assembla’s support team
- Released iPhone and Android apps for Assembla task management on the go
One of the biggest internal changes we made in 2012 was increasing our release frequency from once a month to daily, and many times, multiple times per day. This allows us to fix bugs quicker, release new features sooner, and ensure smoother releases with no scheduled downtime.
Migrating from iterative to continuous releases has taught us some valuable lessons that we have posted on the blog and presented in webinars. If your team is considering the move toward Continuous Delivery, we highly recommend you check out the resources below and feel free to ask us any questions.
- The “Beyond Scrum” Roadmap
- Continuous Delivery and Scalable Agile - Find Out the Secret
- Avoiding Premature Integration or: How we learned to stop worrying and ship software every day
- Continuous Delivery vs Continuous Deployment vs Continuous Integration
- Git Review and Merge like a Boss
A Peek into 2013
In 2013, we're working on "beyond Scrum" agile software development. The current agile methods built around Scrum, co-located teams, post-it-notes, and monthly releases don't work well for our teams. Our teams are globally distributed, growing, and working continuously. The new approach combines task management, code management, online collaboration, and cloud infrastructure to thrust improvements from idea to deployment. Our users are doing it, and we're paying attention, and we're working to package up what we learn.
We kicked off 2013 with the release of our SSH tool, ticket stories with subtasks, improved reports, and various improvements to our UI and global styles. This is just the tip of the iceberg. Our team is working hard on many new features and tools that will be released in the upcoming months. If you have a feature request, please submit it on our feedback site.