ImageMagick has a ridiculous development workflow
Re: ImageMagick has a ridiculous development workflow
Thanks for setting this up.
It seems that for a lot of commits the commit message has not been brought across from SVN successfully, instead they have a commit message of something like:
git-svn-id: https://subversion.imagemagick.org/subv ... runk@18691 aa41f4f7-0bf4-0310-aa73-e5a19afd5a74
If it was a conscious decision to do that, then that's your prerogative. There is some value in preserving the commit messages - so if it wasn't a conscious decision someone (possibly myself) could investigate how to get those commit messages back.
Also, it would be a good idea if you could specify how Pull Requests should be done. The two branches in https://github.com/ImageMagick/ImageMagick have a common origin of 4 years ago but both have been maintained? So should PRs be done for one, and then have the change copied across by whoever is doing the merge or should two matching PRs be made?
It seems that for a lot of commits the commit message has not been brought across from SVN successfully, instead they have a commit message of something like:
git-svn-id: https://subversion.imagemagick.org/subv ... runk@18691 aa41f4f7-0bf4-0310-aa73-e5a19afd5a74
If it was a conscious decision to do that, then that's your prerogative. There is some value in preserving the commit messages - so if it wasn't a conscious decision someone (possibly myself) could investigate how to get those commit messages back.
Also, it would be a good idea if you could specify how Pull Requests should be done. The two branches in https://github.com/ImageMagick/ImageMagick have a common origin of 4 years ago but both have been maintained? So should PRs be done for one, and then have the change copied across by whoever is doing the merge or should two matching PRs be made?
Re: ImageMagick has a ridiculous development workflow
We have a lot of commits that don't have a commit message. And the 'git-svn-id' junk is just there for 'git svn' to keep track of the revisions. ImageMagick has two branches IM7 (master) and IM6 (ImageMagick-6). Pull request should be made to both the branches since we actively maintain both of them.
Re: ImageMagick has a ridiculous development workflow
Dirk, will you also be monitoring the "issues" submitted there?
Re: ImageMagick has a ridiculous development workflow
We will be also monitoring the "issues" that are submitted there. You can now decide if you want to open a bug topic or create an issue on github.
Re: ImageMagick has a ridiculous development workflow
Why are you so obnoxiously holding on to the past? This is ridiculous. You're moving forward an inch at a time.
Commit to moving to git. Handle patches correctly. This project is literally insane.
Commit to moving to git. Handle patches correctly. This project is literally insane.
- fmw42
- Posts: 25562
- Joined: 2007-07-02T17:14:51-07:00
- Authentication code: 1152
- Location: Sunnyvale, California, USA
Re: ImageMagick has a ridiculous development workflow
All of the developers hold full time jobs, besides trying to fix bugs on IM. So they have little time to do this all at once. Be kind and patient. You will get more from either helping or giving positive feedback and not displaying such a negative attitude.
Re: ImageMagick has a ridiculous development workflow
I'm in the same position. I do tons of open source on the side and I manage to do a whole lot better than these guys.fmw42 wrote:All of the developers hold full time jobs, besides trying to fix bugs on IM. So they have little time to do this all at once. Be kind and patient. You will get more from either helping or giving positive feedback and not displaying such a negative attitude.
Re: ImageMagick has a ridiculous development workflow
> I do tons of open source on the side and I manage to do a whole lot better than these guys
Moving to GIT was a step up for the ImageMagick project and addressed some of your concerns. If the projects lack other qualities you think will improve the ImageMagick development workflow, we're listening. Post them here and we will work on them as time permits.
Moving to GIT was a step up for the ImageMagick project and addressed some of your concerns. If the projects lack other qualities you think will improve the ImageMagick development workflow, we're listening. Post them here and we will work on them as time permits.
Re: ImageMagick has a ridiculous development workflow
We have fully moved to GIT, you can find our repository here: http://git.imagemagick.org/repos/ImageMagick. We will maintain the github mirror.
Re: ImageMagick has a ridiculous development workflow
Finally! Thanks!
-
- Posts: 2
- Joined: 2018-08-23T07:24:43-07:00
- Authentication code: 1152
Re: ImageMagick has a ridiculous development workflow
Hi,
I just checked the URL http://git.imagemagick.org/repos/ImageMagick
It seems to be not active. Is the https://github.com/ImageMagick/ImageMagick URL the official repo now?
Greets,
Andreas
I just checked the URL http://git.imagemagick.org/repos/ImageMagick
It seems to be not active. Is the https://github.com/ImageMagick/ImageMagick URL the official repo now?
Greets,
Andreas
Re: ImageMagick has a ridiculous development workflow
Yes it is. This is also stated on our website https://imagemagick.org:
The authoritative ImageMagick web site is https://www.imagemagick.org. The authoritative source code repository is https://github.com/ImageMagick. We maintain a source code mirror at https://gitlab.com/ImageMagick.