AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2017.11.30 15:44 "Re: [Tiff] Switching to gitlab ?", by
2017.11.30 13:52 "Re: [Tiff] Switching to gitlab ?", by Bob Friesenhahn
2017.11.30 14:04 "Re: [Tiff] Switching to gitlab ?", by Even Rouault
2017.11.30 10:31 "Re: [Tiff] Switching to gitlab ?", by Roger Leigh
2017.11.30 13:22 "Re: [Tiff] Switching to gitlab ?", by Olivier Paquet
2017.11.30 14:00 "Re: [Tiff] Switching to gitlab ?", by
2017.11.30 15:26 "Re: [Tiff] Switching to gitlab ?", by Bob Friesenhahn
2017.11.30 15:57 "[Tiff] [DONE] Switching to gitlab !", by Even Rouault
2017.11.30 16:14 "Re: [Tiff] [DONE] Switching to gitlab !", by Even Rouault
2017.11.30 17:36 "Re: [Tiff] [DONE] Switching to gitlab !", by Roger Leigh

2017.11.30 10:31 "Re: [Tiff] Switching to gitlab ?", by Roger Leigh

> Have we acted the switch to the gitlab repository?

There haven't been any CVS commits since I did the conversion, so from a practical point of view, it's ready to use whenever you want to--just be sure not to make any further CVS commits!

For gitlab, while it's possible to use in the same style as CVS (direct push to the master branch), it's also possible to prevent direct pushes and require all changes to go via a merge request. The workflow is entirely up to what you prefer. The merge request workflow has the benefit of running continuous integration builds and tests, so you can validate the change before merging it into master. It's also configurable to require all CI builds to pass before merging.

Regards,
Roger