That relies on the person deciding to merge the PR to not do so until after a
certain date, while a branch that people base on would seem to help make that
easier and less prone to mistakes, not to mention people can start piling on
each other's commit history if they would happen to pull dependent work. It's a
fairly common Git workflow when you have multiple trains.
Heath Stewart
Software Engineer
Visual Studio Deployment Experience, Microsoft
http://blogs.msdn.com/heaths
From: Rob Mensching [mailto:r...@firegiant.com]
Sent: Wednesday, July 8, 2015 4:34 PM
To: WiX toolset developer mailing list <wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] New branch for wix311?
You can submit pull requests against wix3/develop. That will become v3.11 after
v3.10 moves to master.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
From: Heath Stewart [mailto:heath.stew...@microsoft.com]
Sent: Wednesday, July 8, 2015 2:41 PM
To: WiX toolset developer mailing list
Subject: [WiX-devs] New branch for wix311?
Since we're trying to lock down 3.10, can we open a branch for proposed 3.11
work? I found a bug in DTF I'd like to fix in privates at least to unblock some
automation. I can always rebase later, but figured if there's bugs we know
aren't release-blocking for 3.10 we could start queueing them up for 3.11.
Heath Stewart
Software Engineer
Visual Studio Deployment Experience, Microsoft
http://blogs.msdn.com/heaths
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
