On 12/02/2016 03:14 PM, Andrew Savchenko wrote: > > What about the following forkflow: > - version bump first with minimal changes required, but without > pushing commit to the tree; > - make each logical change as a separate commit without revision > bumps and without pushing stuff to the tree (of course repoman > scan/full is required as usual for each commit); > - well test package after the last commit (that it builds with > various USE flag combinations, old and new functionality works fine > and so on); > - fix any problems found and only afterwards push changes to the > tree. > > This way users will see only foo-1.0 -> foo-1.1 change in the tree, > while git will still retain each logical change as a separate > commit, which will make future maintenance and debugging much > easier.
That's reasonable but I also think that bumping and fixing an ebuild at the same time can be considered an atomic change since it's effectively a _new_ ebuild -- Regards, Markos Chandras
