On 27/02/2019 14:46, Yaroslav Halchenko wrote:
On Wed, 27 Feb 2019, Andreas Tille wrote:I'd prefer if you would move the 0.24 packaging to some separate branch (debian-experimental is covered but may be debian-0.24 or something like this?) and keep branch debian for what we are really releasing.well "releasing" is a loaded term. I guess you are talking about uploading to unstable so it manages to get into buster. Since "debian" branch already got its 0.24, what about starting debian-buster branch off debian/0.23.3-1 ?
That's what I was planning, like statsmodels already has. (I was going to call it 'buster', but I don't care about the name.)
otherwise -- I am ok to hard-reset and force push debian to the debian/0.23.3-1 state -- everyone should just beware of it, and then progress debian-experimental to current state of debian (v0.24.1-972-g1cfbd07c7)
I'd rather not rebase/force-push a public repository (even if it is in practice unlikely that anyone other than us has downloaded it). It should be possible to get to that state without doing so ("merge" debian into debian-experimental, then commit a "revert to 0.23" to debian).
(In general, I slightly prefer the "'debian' is development head, whether that's currently unstable or experimental (due to a freeze or a transition)" layout. However, that may be because the packages I currently maintain rarely needed any changes in unstable while the package was also in experimental, and this layout hence avoided branching most of the time. Something as central as pandas may need two active branches more often.)