https://kotlinlang.org logo
#feed
Title
# feed
k

Kirill Grouchnikov

02/08/2021, 1:43 PM
Probably not the best to release to JCenter now
☝️ 7
lol 7
h

Hamza GATTAL

02/08/2021, 2:01 PM
What's the main reason
v

Vampire

02/08/2021, 2:09 PM
Well, it's probably still a good idea to release updates to JCenter for existing consumers. And for new ones there is already the alternative repo on Space.
g

gammax

02/08/2021, 2:38 PM
As a side note: you can publish to JCenter only till the end of the month (Feb 28th). Afterwards it will become “read-only”.
it’s probably still a good idea to release updates to JCenter for existing consumers
I’d like to disagree here. Given the short timeline, it’s probably better to just push new releases to Central only and make sure consumer migrate.
k

Kirill Grouchnikov

02/08/2021, 2:43 PM
Indeed, I don't think you're serving existing consumers well by pretending business is as usual with JCenter
t

tddmonkey

02/08/2021, 2:46 PM
I agree. Use new versions as a carrot to get people to eagerly move.
a

altavir

02/08/2021, 5:02 PM
It is still working. And I am not happy with central release process (they are still did not request for my registration request for my university address. kotlin.link repo is a nice substitute and I am using it as a proxy for the Space repo.
And of coures, I can't push this one to central since kscience domain does not exist. I've bought kscience.space just in case though.
k

Kirill Grouchnikov

02/08/2021, 5:36 PM
You're just postponing the inevitable by three weeks
a

altavir

02/08/2021, 5:37 PM
Maybe. But I have to do breaking change and switch package again to publish to central, so I will wait and see if there are some other ideas.
d

Dominaezzz

02/08/2021, 7:00 PM
What's this about the alternative repo on Space?
v

Vampire

02/08/2021, 7:07 PM
What is your question actually? In his announcement he present an alternative repo on Space additonal to JCenter.
d

Dominaezzz

02/08/2021, 7:09 PM
Ohhh, didn't click the link. Thanks.
r

Robert MacLean

02/09/2021, 8:22 AM
Use new versions as a carrot to get people to eagerly move.
Assumes people check this; so many projects get the bits and don’t check until it breaks. I think it is a wise move but don’t think it will have any major impact. Actually need something like gradle to start raising a warning
v

Vampire

02/09/2021, 8:29 AM
Which would assume people update Gradle more often than their libs. :-D What you actually need is an intentionally broken artifact, so that at least people looking in JCenter or via some plugin for lib updates are getting "notified" :-D
💯 3
r

Robert MacLean

02/09/2021, 9:43 AM
fair shout 😆
3 Views