I have done quite a bit of looking on the Redmine website, and executed a number of Google searches, but I have not been able to find an answer to the difference between Redmine 2.x and Redmine 3.x
I imagine that, much like Redmine 1 vs Redmine 2, it has to do with the version of Rails that the platform is built on, but I would be interested to know a little more in-depth about the differences and compatibility.
I imagine, also, that plugins are not compatible between the two versions, so this leaves one to wonder, what are the benefits of using one over the other?
Edit: I do see the Rails version difference listed on the Installation page. What is the difference beyond that?
We using Redmine at work, with version 2.3.3
And now we wanted to upgrade to new versions (security updates).
We asked the same question.
And what I founded:
from their news page
This new version brings several improvements to the search engine (it's now much faster and includes new search options) and many new features: default issue status per tracker, multiple emails per user, ability to edit attachment descriptions and more
from their Changelog
...
Feature #13849: Grouped filters in the filter drop-down
Feature #13051: Support any macro in (pdf) export for wiki's and issues
Feature #12097: Multi Thread Support
Feature #8818: Repository user-mapping with multiple email addresses
Feature #11702: Add user/group to multiple projects at once
Feature #4244: Multiple email addresses for each user
Feature #1326: Add / edit an attachment description after upload
...
and more
Related
I am trying to upgrade Sitecore 9.0 to Sitecore 9.2. Couldn't find any specific way except first upgrading to Sitecore 9.0.2 and then proceed further. But, this way getting many errors related with config file. Is there any other way to upgrade directly to 9.2 verion? Any help would be a highly appreciated. Thanks.
The alternative method to 'upgrade' which I often look to is to spin up a clean install of the newer version and then migrate my old code into a new solution which will already have all the latest configs/ Sitecore base code in place.
Doing this means you can just patch your custom app config settings and ensure the Sitecore dependencies in your solution are the newer version which can often be a cleaner/simpler way to go.
There are a couple of things to consider before doing this however, such as whether you need to keep your data in XDB etc. as it would mean that you may need to look at migrating it which can be a pain and since you are looking at 9.0 to 9.2, you'd have additional services to consider as well such as Identity and may need to account for that kind of thing too.
I am currently trying to upgrade a Sitecore installation from 7.5 to 8.1 Update 3 and I can't seem to figure out a good process that won't take weeks and weeks. I have posted questions on other blog posts and also to the official Sitecore Community site but have not really gotten any good feedback. Here is what I am trying to do.
I need to upgrade Sitecore from 7.5 to 8.1 Update 3. To do that it looks like I need to do 3 separate upgrades:
7.5 to 8.0 Initial Release
8.0 Initial Release to 8.1 Initial Release
8.1 Initial Release to 8.1 Update 3
In addition we are using both the Email Campaign Manager (ECM) and the Webforms for Marketers (WFFM) modules. Each of those modules has its own separate upgrade instructions.
Also we have servers in 3 different environments: 1 in DEV, 1 in QA and 3 in PROD (1 CM and 2 CD)
The upgrades of Sitecore itself are long and tedious and filled with many manual steps prone to error. I am already on my 3rd attempt to upgrade my DEV site and it seems every time I do it I get about half way through and I run in to lots of errors. In addition the instructions for upgrading ECM/EXM seem to not allow you to skip to major releases. So to upgrade EXM itself I am going to have to do 10 individual upgrades!!!
I am trying desperately to figure out if there are any shorter ways to accomplish this upgrade. This is so complicated and tedious that I feel like it will take me one or two days just to upgrade the DEV site. Then another one or two days to upgrade the QA site - assuming I don't run in to any errors that I can't figure out.
Then after that I have absolutely no idea how I am going to upgrade PROD. I have a CM server and 2 CD servers. There's no way I can freeze content entry and editing for a week while I do the upgrade. Plus we have some user generated content like user registrations and order entries on the site. How can I upgrade PROD and not lose registrations and order entries and other user generated content?
I was hoping that there would be some easier way of doing a Sitecore upgrade from one major version to the next but I can't seem to figure it out. No matter what I try it is incredibly complex and manual and prone to error.
Any help is appreciated.
Corey
One option could also be installing a new version of Sitecore 8.1 update 3 and run a database comparison tool (such as RAZL) to get across the items in your new Sitecore instance.
You could get the items across using the regular Sitecore packages although that's more time-consuming unless you automate that using something like Sitecore Ship or Courier.
You'll also need to check your code of course, any config changes you're patching in etc. still will have to be tested.
Mind you, this is not recommended practice for reasons you can find in the blogpost jammykam posted in a comment (http://www.seanholmesby.com/the-truth-about-sitecore-upgrades/)
There's rumors of an Express upgrade tool in 8.2 that will allow you to upgrade directly from an old version. I don't have an official source, but there's a few blog posts about this, this for example: http://kverheire.blogspot.com.au/2016/06/sitecore-82-in-depth-preview-83-update.html
I believe the people who actually have more info on that are bound by NDA - so you'd have to ask Sitecore directly for more info.
If you can't wait for 8.2 - then you can also create new blank environments of a newer version and write your own processes for migrating data across. Not sure how easy this will be with EXM, WFFM, or Analytics though.
Recently Sitecore 8 has released and it has came up with lot of exciting new features. So our team decided to move from Sitecore 6.6 to Sitecore 8. Before migrating, i would like to know what all things i should be having in handy. Such as, .net Framework, Hardware configuration, environment etc.
Also, i would like to know the procedure to migrate from 6.6 to 8? I, never involved in sitecore migration project before. Please suggest me some good articles or post here your thoughts.
Thanks in advance. :)
See the Sitecore Compatibility Table for the .NET Framework, SQL Server version and Windows version.
Two common approaches.
1) Follow the Sitecore upgrade path.
2) Package the content, and start with a clean install.
Currently I working on a upgrade with an scripted upgrade that follow the Sitecore path. So I can easy repeat the steps and have the latest content in the databases.
I have some of my findings put down here Sitecore update and modules this article contain also a Related links section. Such as the upgrade white paper from Varun
Depending on how 'cluttered' your existing instance is, you may also want to consider installing a fresh copy of Sitecore 8 and then migrate your data/code to avoid all the hops that would be necessary to get to 8.
May be the following blog might help. Take a look at it.
https://varunvns.wordpress.com/2014/11/11/sitecore-version-upgrade-whitepaper/
I would recommend you make a backup of your site to use as a "sandbox" for the upgrade. Copy your databases and the web root for your site to a new location and then set up an IIS site with appropriate permissions pointing to your copy, and change your connection strings in the copy to point to a copy of the databases you backed up.
Perform the update there and ensure everything is working correctly. Work slowly to make sure you are following instructions correctly and note any special actions you had to take to perform the upgrade. Once you have it upgraded, perform the same process on the "real" site.
If you work with a Sitecore partner, I would highly encourage you to discuss the process with them to learn more specifics about the risks and challenges you may encounter during your upgrade.
We are already using Redmine internally for issue tracking.
Now we also need to track the inventory and maintenance history of equipments of a customer (which should be able to connect and change the state/location of their equipment).
Which Redmine plugins would you recommend for this purpose?
I don't know your exact requirements but you may find the following plugins helpful. You may build your own plugin on top of these with some customization as per your requirements so that its compatible with the latest version of Redmine.
http://www.redmine.org/projects/redmine/wiki/PluginEzlibrarian
https://github.com/danielanguita/Redmine-Inventory-Manager
We are planning to move over our project management to Redmine and also our Git repositories from Github to Redmine. Are there any potential hazards or drawbacks we should consider? We are a growing team. We will be using these across cross functional teams. Members will range from 20 to 60 or more (in all teams).
I can only suggest you look at this list of issues on the Redmine project's site - naturally, they use Redmine to track them.
We have been using Redmine for a year now (although not with git), we have about 15 users, and have not experienced any issues with it.
If you are concerned about stability, it might be an idea to use an older version with no known serious bugs, rather than the latest version.
I have customized Redmine for our team here. It is a great piece of Software with some really useful and agile-focused plug-ins. We use Redmine Backlogs, stuff-to-do plugins which are great. I was wondering if anyone was successful in setting multiple repositories in a single project? I know that I can create a sub-project and set up a different repo. But there could be cases where there is a need to have more than one repos in the 'Repository' tab of Redmine(For example code might be in development environment initially and then moved to staging and production and so need for two repos for a project) and also to get the issues associated with the commit messages. That is one of the drawbacks for some people.
This could get mandatory if you have a pre-commit hook to refer to issue numbers.