Adopt DEP-14 branch naming in team workflow
Let's not hijack the RFS thread...
On Fri, Sep 28, 2018 at 9:25 AM Dmitry Smirnov <onlyjob@debian.org> wrote:
>
> On Thursday, 27 September 2018 9:24:40 PM AEST Martín Ferrari wrote:
> > Dmitry, we had this discussion a long time ago in the team list and in
> > person during DebConf17
>
> I wasn't part of this discussion (probably being busy working) or I would
> have opposed it as hard as I could. No DEP-14 please.
>
>
> > and decided to adopt this as policy.
>
> What?!? We have to stop this madness. IMHO it is a disservice to team to
> introduce DEP-14 and a standard practice.
>
>
> > I really don't understand why you are so opposed to it,
>
> Because it is a bad idea, inconvenient and time consuming.
> It improves nothing and makes it mode difficult to maintain packages.
>
> Now I have to put on hold everything that have to do and write about it just
> to prevent it from happening... Why can't we work towards something useful?
>
> I'll see if I can put some ideas together in the next few days.
> I'm very very busy right now...
>
Please do give us some reasons. Just complaining doesn't help...
In section 1.4 of https://go-team.pages.debian.net/workflow-changes.html
We only adopt the branch naming. The only difference is the master
branch now called debian/sid. I don't think that could be such
terrible as you described.
>
> > maybe me or somebody else can work with you to ease that feeling?
>
> Don't make it sound like my physiological problem. It is not about feelings.
>
> Although I do feel betrayed because someone works behind my back to sabotage
> what works in practice and replace it with inferior time consuming workflow.
>
--
Shengjing Zhu
Reply to: