> On Jan. 17, 2014, 8:12 p.m., Maxim Khutornenko wrote:
> > build-support/release/tag-release, line 70
> > <https://reviews.apache.org/r/17063/diff/1/?file=427256#file427256line70>
> >
> >     Should we even support patching off of master? What if there were 
> > interim commits past minor/major release that are adding features that 
> > don't qualify for a patch? Should we rather do hotfixing off of a tagged 
> > release with reverse integration into master?

+1, i could be overthinking, but i anticipated patch releases being ~always 
cherry-picking.  So far i've been committing to master, 
cherry-picking/backporting.


- Bill


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17063/#review32193
-----------------------------------------------------------


On Jan. 17, 2014, 7:24 p.m., Brian Wickman wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/17063/
> -----------------------------------------------------------
> 
> (Updated Jan. 17, 2014, 7:24 p.m.)
> 
> 
> Review request for Aurora and Kevin Sweeney.
> 
> 
> Repository: aurora
> 
> 
> Description
> -------
> 
> Update tag-release to allow patch level increments.
> 
> (just now noticed I branched off the status checker change -- ignore that for 
> now.)
> 
> 
> Diffs
> -----
> 
>   build-support/release/tag-release 90dc5da2fcb515359174d289d69cac01009f6014 
>   src/main/python/apache/aurora/executor/common/status_checker.py 
> efffa8fda06afb830c5f65fb6eb15f4510225e96 
> 
> Diff: https://reviews.apache.org/r/17063/diff/
> 
> 
> Testing
> -------
> 
> Nope
> 
> 
> Thanks,
> 
> Brian Wickman
> 
>

Reply via email to