digitalmars.D.announce - dmd package numbering scheme - Build Master wanted
- Walter Bright (12/12) Nov 06 2013 There have been a lot of comments about the package naming scheme and nu...
- Brad Anderson (9/24) Nov 06 2013 It might need to be multiple people because very few people are
- Walter Bright (3/6) Nov 06 2013 Of course. Being in charge of something doesn't mean being expert at all...
- Mathias Lang (11/20) Nov 06 2013 Good to have a thread on it, thank you for taking this step Walter !
- Jacob Carlborg (4/14) Nov 07 2013 I fully agree.
- Jacob Carlborg (4/7) Nov 06 2013 I can help out with Mac OS X.
- Walter Bright (2/3) Nov 07 2013 And I appreciate that!
- Walter Bright (3/4) Nov 07 2013 Jordi had fixed the Linux package builder so it could also build the Win...
- Jacob Carlborg (6/9) Nov 07 2013 I can investigate, but don't think it will be straight forward. As a
- Walter Bright (3/10) Nov 07 2013 Sure, that's possible, and I'll do it that way if it turns out to be imp...
- Jacob Carlborg (9/12) Nov 20 2013 I've tried now, for a couple of days, to create an installer for Mac OS
- Dicebot (7/7) Nov 07 2013 Unfortunately, I can't help here because already volunteered for
- Andrei Alexandrescu (3/9) Nov 07 2013 No worries, we'll provide the appropriate access.
- Dejan Lekic (6/21) Nov 07 2013 This is why large projects have release manager(s). The more D
There have been a lot of comments about the package naming scheme and numbering scheme. I confess that these issues do not seem that important to me, as the user just clicks on a url, but I recognize that they are very important to others. This is why I believe that D needs a Build Master. This person needs to be someone who ensures that the packages are all properly built, the build scripts work, the versions are done right, the git tags are done, etc., and takes pride in it being done to perfection. (Note that because dmd changes constantly, and the operating system targets also change constantly, the package build scripts constantly break.) Eventually, I'd like at least the package builds to be done automatically by Brad's autotester. But someone still needs to make sure it is working properly and keeps working properly.
Nov 06 2013
On Wednesday, 6 November 2013 at 21:25:46 UTC, Walter Bright wrote:There have been a lot of comments about the package naming scheme and numbering scheme. I confess that these issues do not seem that important to me, as the user just clicks on a url, but I recognize that they are very important to others. This is why I believe that D needs a Build Master. This person needs to be someone who ensures that the packages are all properly built, the build scripts work, the versions are done right, the git tags are done, etc., and takes pride in it being done to perfection. (Note that because dmd changes constantly, and the operating system targets also change constantly, the package build scripts constantly break.) Eventually, I'd like at least the package builds to be done automatically by Brad's autotester. But someone still needs to make sure it is working properly and keeps working properly.It might need to be multiple people because very few people are experts in every platform supported. Maybe a release manager with more "platform lieutenants" to help. In any case, I think this is a good idea. Nick's tool should help whomever takes on this job until the autotester stuff is in place: https://github.com/D-Programming-Language/installer/pull/24
Nov 06 2013
On 11/6/2013 1:43 PM, Brad Anderson wrote:It might need to be multiple people because very few people are experts in every platform supported. Maybe a release manager with more "platform lieutenants" to help.Of course. Being in charge of something doesn't mean being expert at all of it or doing all the work - help from others will be necessary.
Nov 06 2013
Good to have a thread on it, thank you for taking this step Walter ! Although, it looks to me that the numbering scheme and the git tags are not related to the build, but rather related to the release. So you might consider a release master, not just build. This will involve doing (or delegating to the proper person) the changelog, define a release cycle, which will include pre-release (rc / sanity check), release (communication / building / test / upload ...), and possibly post-release (be sure the security fixes are being backported to the supported versions, ie) actions. IMO that would be very beneficial for D to have someone holding that role. 2013/11/7 Walter Bright <newshound2 digitalmars.com>On 11/6/2013 1:43 PM, Brad Anderson wrote:It might need to be multiple people because very few people are experts in every platform supported. Maybe a release manager with more "platform lieutenants" to help.Of course. Being in charge of something doesn't mean being expert at all of it or doing all the work - help from others will be necessary.
Nov 06 2013
On 2013-11-07 08:57, Mathias Lang wrote:Good to have a thread on it, thank you for taking this step Walter ! Although, it looks to me that the numbering scheme and the git tags are not related to the build, but rather related to the release. So you might consider a release master, not just build. This will involve doing (or delegating to the proper person) the changelog, define a release cycle, which will include pre-release (rc / sanity check), release (communication / building / test / upload ...), and possibly post-release (be sure the security fixes are being backported to the supported versions, ie) actions. IMO that would be very beneficial for D to have someone holding that role.I fully agree. -- /Jacob Carlborg
Nov 07 2013
On 2013-11-06 22:43, Brad Anderson wrote:It might need to be multiple people because very few people are experts in every platform supported. Maybe a release manager with more "platform lieutenants" to help.I can help out with Mac OS X. -- /Jacob Carlborg
Nov 06 2013
On 11/6/2013 11:55 PM, Jacob Carlborg wrote:I can help out with Mac OS X.And I appreciate that!
Nov 07 2013
On 11/6/2013 11:55 PM, Jacob Carlborg wrote:I can help out with Mac OS X.Jordi had fixed the Linux package builder so it could also build the Windows package. Is it possible to build the release package for OS X under Linux as well?
Nov 07 2013
On 2013-11-07 21:19, Walter Bright wrote:Jordi had fixed the Linux package builder so it could also build the Windows package. Is it possible to build the release package for OS X under Linux as well?I can investigate, but don't think it will be straight forward. As a workaround, can't you create a script that SSH in to your Mac, executes the build scripts and then sends the file back to your Linux machine? -- /Jacob Carlborg
Nov 07 2013
On 11/7/2013 1:10 PM, Jacob Carlborg wrote:On 2013-11-07 21:19, Walter Bright wrote:Sure, that's possible, and I'll do it that way if it turns out to be impractical to do it locally.Jordi had fixed the Linux package builder so it could also build the Windows package. Is it possible to build the release package for OS X under Linux as well?I can investigate, but don't think it will be straight forward. As a workaround, can't you create a script that SSH in to your Mac, executes the build scripts and then sends the file back to your Linux machine?
Nov 07 2013
On 2013-11-07 21:19, Walter Bright wrote:Jordi had fixed the Linux package builder so it could also build the Windows package. Is it possible to build the release package for OS X under Linux as well?I've tried now, for a couple of days, to create an installer for Mac OS X using tools available on other platforms. Unfortunately I haven't been able to get a working installer. I have an installer running but it cannot finish the installation. The installer uses weird archive formats and other undocumented formats. Can't all installers be built on a Mac instead? I know that's not ideal. -- /Jacob Carlborg
Nov 20 2013
Unfortunately, I can't help here because already volunteered for stuff much over my spare capabilities. But I wanted to note that this is not just about stepping up and being willing to help - such person would need to have a "push" access to website, repositories, ftp and any other infrastructure related to release. I hope you don't expect this stuff to work without "giving the keys" to someone? :)
Nov 07 2013
On 11/7/13 5:04 AM, Dicebot wrote:Unfortunately, I can't help here because already volunteered for stuff much over my spare capabilities. But I wanted to note that this is not just about stepping up and being willing to help - such person would need to have a "push" access to website, repositories, ftp and any other infrastructure related to release. I hope you don't expect this stuff to work without "giving the keys" to someone? :)No worries, we'll provide the appropriate access. Andrei
Nov 07 2013
On Wednesday, 6 November 2013 at 21:25:46 UTC, Walter Bright wrote:There have been a lot of comments about the package naming scheme and numbering scheme. I confess that these issues do not seem that important to me, as the user just clicks on a url, but I recognize that they are very important to others. This is why I believe that D needs a Build Master. This person needs to be someone who ensures that the packages are all properly built, the build scripts work, the versions are done right, the git tags are done, etc., and takes pride in it being done to perfection. (Note that because dmd changes constantly, and the operating system targets also change constantly, the package build scripts constantly break.) Eventually, I'd like at least the package builds to be done automatically by Brad's autotester. But someone still needs to make sure it is working properly and keeps working properly.This is why large projects have release manager(s). The more D becomes popular, the more work will be performed by this individual, or individuals. Especially if we want to support various Linux distributions, etc...
Nov 07 2013