> For example yesterday I added Jewel SimpleLoader. Don't think that kind of > change will need to be a PR.
Agree, but we should have some way to quickly see additions. Maybe immediate update of release notes? A quick note to a wiki page? > On Jun 19, 2020, at 12:56 PM, Carlos Rovira <[email protected]> wrote: > > Hi, > > I'm for what Alex suggests. Just email with some kind of "[Breaking > Change]" or "[API change]" warning, so we can discuss. > I think that would be more easy and will continue to make all flow and > avoid freezing. I think the problem is things like my > change of "BrowserResizeHandler". > > For example yesterday I added Jewel SimpleLoader. Don't think that kind of > change will need to be a PR. > > I must say that, in my mind the 1.0 version is what makes us to be even > more careful since it's what a major version dictates. > But it's real that we are currently in something that many of us consider > 1.0, so we should be more careful since now. > > thanks > > > > > El vie., 19 jun. 2020 a las 9:05, Harbs (<[email protected]>) escribió: > >> Seems like a reasonable approach. I already try to do this. >> >>> On Jun 19, 2020, at 8:24 AM, Alex Harui <[email protected]> >> wrote: >>> >>> The cheapest solution, IMO, is just to get everyone to agree not to >> change APIs in Basic without prior discussion. Probably major code-path >> changes too. >> >> > > -- > Carlos Rovira > http://about.me/carlosrovira
