4 ms·
GitLab.com co-founder here. As you noted you should upgrade version by version. This makes sure everyone uses the same upgrade path so the single focus of the c
by sytse 13y ago
GitLab.com co-founder here. As you noted you should upgrade version by version. This makes sure everyone uses the same upgrade path so the single focus of the community is on making that path rock solid. This is annoying when you are a lot of versions behind. Maybe you can already guess my recommendation, consider upgrading more frequent :-)
- bloodorange 13y agoAs a user, it doesn't look nice to hear this from the developers. I think it would be nice to have a stable upgrade mechanism that doesn't break anything for people - or maybe an automated mechanism that does all the upgrades step by step so the user doesn't have to do much. Since I have seen this 'upgrade' problem repeatedly mentioned here, I think it would be a good problem to attack to help people feel more comfortable about using your product. I recently set up gitolite internally and this thread interests me because GitLab looks like something that could be considered for Git hosting. However, someone in my place may not be so comfortable with the idea when I get the general feeling that "upgrades are a pain". I only mean this as feedback to help you make your product more palatable (because I want to see a lot of good Git hosting solutions!)
- sytse 13y agoHi bloodorange, I'm sorry if I'm sounded strict. I agree that automatic updates would be very nice, but making these rock solid is not something we are comfortable with. Many people run GitLab with some kind of customization and we want to support that as well. We try to make upgrades as easy as possible but you do have to run each upgrade.