I think that if you are going to stop taking features in a branch, you need
to give sufficient warning beforehand. I don't know how long that should
be, but if the pull request was submitted before you gave warning it should
be accepted (unless it's a massive change like my 4299 pull request).
When I was talking about making 4.0 stable by the time 3.9 releases, that
was assuming that you stop taking feature requests in 3.x after that. I
actually don't want to stop taking feature requests in 3.x any time soon.
If the developer submitting the feature does the work of submitting
separate pull requests, I don't see why it can't be accepted in 3.x and
4.x. I don't see why you would do things like add support for "VS-Next"
but not take other feature requests.
On Tue, Apr 29, 2014 at 12:39 PM, Rob Mensching <r...@firegiant.com> wrote:
> I basically agree with your classifications.
>
>
>
> So in my comments, I was channeling Bob’s latest blob post:
> http://www.joyofsetup.com/2014/04/25/to-wix-v3-9-and-beyond/ that
> suggested now is no longer the time to be adding features to WiX v3.9.
> Definitely more Bob’s call than mine but I was playing devil’s advocate
> (because someone has too… and usually it’s Bob. <smile/>)
>
>
>
> I also feel that WiX v3.10 should be what you call a maintenance branch
> but I suppose that depends a little on what the heck Visual Studio does
> next. Maybe WiX v3.11 can be solely targeted to support VS-Next?
>
>
>
> Given that there has been very little activity in WiX v4.0 besides what
> we’ve done at FireGiant, I doubt it will be possible to make WiX v4.0
> stable at the same time we release WiX v3.9. However, I don’t know why
> that matters. WiX v4.0 shouldn’t be more than 6-9 months out (I hope closer
> to 6 than 9 since we originally stated v4.0 should go out summer or early
> fall). That means any features going there should be going there quickly.
>
>
>
> Basically, I’m once again suggesting we need to shift our focus from
> adding features to WiX v3.x to adding features to WiX v4.0 and solely
> fixing bugs in WiX v3.x. Note, this is just my suggestion (Bob still makes
> call on in/out for WiX v3.x) but I’m curious if others think I’m way off
> base.
>
>
>
> _______________________________________________________________
>
> FireGiant | Dedicated support for the WiX toolset |
> http://www.firegiant.com/
>
>
>
> *From:* Sean Hall [mailto:r.sean.h...@gmail.com]
> *Sent:* Monday, April 28, 2014 3:50 PM
> *To:* WiX toolset developer mailing list
> *Subject:* Re: [WiX-devs] Compatibility and style discussion
>
>
>
> 2. Here's my two cents on where features go. I think there should be
> three types of active branches: maintenance, stable, and unstable.
>
>
>
> Maintenance branches only take bug fixes. We don't have any of these
> right now.
>
>
>
> Stable branches take all bug fixes and new features as long as they're
> non-breaking. WiX 3.9 is a stable branch.
>
>
>
> Unstable branches take bug fixes and new features even if they're
> breaking. Unstable branches eventually convert to stable in order to
> prepare for release. WiX 4.0 is an unstable branch that hasn't converted
> yet.
>
>
>
> I think there should always be a stable branch, or at least an unstable
> branch that has converted to stable. There's much more incentive for
> people to contribute back when they can get their contribution integrated
> into the next weekly build of a stable branch.
>
>
>
> I think that the point that new features need to go only in 4.0 is when
> the 3.x branches are maintenance branches. I think you should only be able
> to declare a branch as a maintenance branch in the beginning. So if we
> want to stop taking features in 3.x, we should pick a release date for 3.9,
> declare 3.10 as a maintenance branch, and convert 4.0 into a stable branch
> no later than when 3.9 ships. In the meantime, I think it's perfectly fair
> to start requiring people to start sending separate pull requests to 3.x
> and 4.0 if they want their contribution in 3.x.
>
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
