Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-dev] Intended Bug-Tracker for Platform-projects hosted on GitHub

A plan is surely needed.

Let discuss it on https://github.com/eclipse-platform/eclipse.platform/issues/7 may be ?

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov


> Gesendet: Donnerstag, 31. März 2022 um 10:00 Uhr
> Von: "Ed Merks" <ed.merks@xxxxxxxxx>
> An: platform-dev@xxxxxxxxxxx
> Betreff: Re: [platform-dev] Intended Bug-Tracker for Platform-projects hosted on GitHub
>
> See, you too are hoping that your opinion matters and that your opinion 
> is included in the decision making process.  I expect we all would like 
> that very much.
> 
> -1000 for merging in the absence of a cohesive plan that the committers 
> agree is a good strategy for our project
> 
> On 31.03.2022 09:53, Christoph Läubrich wrote:
> > Am 31.03.22 um 09:42 schrieb Aleksandar Kurtakov:
> >>
> >>
> >> On Thu, Mar 31, 2022 at 10:35 AM S A 
> >> <simeon.danailov.andreev@xxxxxxxxx 
> >> <mailto:simeon.danailov.andreev@xxxxxxxxx>> wrote:
> >>
> >>     Please first finish the GitHub moves and let that settle for a month
> >>     (or better, a fe months). There are enough new problems and
> >>     disruptive changes already.
> >>
> >>
> >> The thing is in order to fix very old problems and some new we have 
> >> to change things or we are going to add even more bandaid and make it 
> >> even harder to fix later (as it has happened so many times).
> >
> > +100
> >
> > later is just another term for "probably never" in 
> > software-development ;-)


Back to the top