Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jun 17 22:00
    paualarco assigned #653
  • Jun 17 20:41
    scala-steward opened #677
  • Jun 17 15:51
    paualarco opened #676
  • Jun 17 06:44

    paualarco on master

    Update auth, dynamodb, s3, sqs … (compare)

  • Jun 17 06:44
    paualarco closed #675
  • Jun 16 20:30
    scala-steward opened #675
  • Jun 16 16:47
    scala-steward opened #674
  • Jun 16 09:37
    paualarco labeled #673
  • Jun 16 09:37
    paualarco opened #673
  • Jun 16 09:37
    paualarco labeled #673
  • Jun 16 07:20
    paualarco closed #671
  • Jun 16 00:36
    scala-steward opened #672
  • Jun 15 20:30
    scala-steward closed #669
  • Jun 15 20:30
    scala-steward opened #671
  • Jun 15 13:10

    paualarco on master

    Update hadoop-client, hadoop-co… (compare)

  • Jun 15 13:10
    paualarco closed #670
  • Jun 15 10:37
    scala-steward opened #670
  • Jun 14 20:59
    scala-steward opened #669
  • Jun 14 19:12
    paualarco labeled #668
  • Jun 14 19:12
    paualarco opened #668
Piotr Gawryś
@Avasil
I aggre it's a good idea to release 0.1.0, it can still be useful to people and it's a chance to get feedback. Consider setting up Mima and try to preserve bincompat in 0.1.x to get used to it but also not worry about upgrading to 0.2.0 soon. Treat it like an exercise until the project fully stabilizes.
Pau Alarcón
@paualarco
Sounds good! :) Okay will have that in mind, there is no rush indeed. Some feedback would be appreciated since now people can't even play with it.
Alexandru Nedelcu
@alexandru
We should grant @paualarco access for publishing on Sonatype for io.monix and let him be in charge of the release, to get accustomed to the process.
I don't remember exactly the procedure, but I think we should open a ticket on Sonatype or reuse an old one.
We have this issue on Sonatype, we could add a comment to it: https://issues.sonatype.org/browse/MVNCENTRAL-2890
@paualarco let me know your Sonatype username
Or create an account if you don't have one
And yes, publishing a 0.1.0 sounds like a good plan. Let it mature a little before declaring 1.0.0, because afterwards you have to worry about compatibility.
Pau Alarcón
@paualarco
Hey @alexandru, I've just created an account with username paualarco, but I can't access to the ticket link you sent.
And yes, that's the plan, to stay in 0.x for a while until being confident enough. Eventually I would notify the future intentions before hand in order to get your approval / opinion.
Alexandru Nedelcu
@alexandru
@paualarco no worries, I've made the request, will let you know when an admin at Sonatype replies
Alexandru Nedelcu
@alexandru
@paualarco got a confirmation, you can now publish on Sonatype under the io.monix organization
let us know if you need help setting things up, Sonatype is a challenge
I recomment that you setup an automated deployment process via GitHub Actions
My template might provide some help in setting that up: https://github.com/alexandru/typelevel-library.g8
It's basically making use of this plugin: https://github.com/olafurpg/sbt-ci-release
Pau Alarcón
@paualarco
It will be interesting :)
Pleas let me know once the people from Sonatype have replied and given me the access.
Is web documentation something I have to worry about now? Or will be later?
I would probably come up with more questions later on :P
Alexandru Nedelcu
@alexandru
@paualarco you should already have access with your user
Worry about documentation later.
Also the first release could be a "hash release"
If you setup sbt-ci-release, it will also include: https://github.com/dwijnand/sbt-dynver
And this nice plugin can generate dynamic versions for you, so instead of publishing a 0.1.0-SNAPSHOT, you could publish something like 0.1.0-c93fa3
Where c93fa3 is the git SHA
So try publishing such a version from your localhost and see if it works
Pau Alarcón
@paualarco
Cool will go through the repos you mentioned and try to do so
You are also using github4s, aren't you?
Pau Alarcón
@paualarco
What are the reasons I should migrate travis to github actions? https://github.com/olafurpg/sbt-ci-release is using travis.
Alexandru Nedelcu
@alexandru

You are also using github4s, aren't you?

It's used by the documentation website, you can ignore that.

What are the reasons I should migrate travis to github actions? https://github.com/olafurpg/sbt-ci-release is using travis.

There are pros and cons. If you want, stay with Travis. One thing that bothers me and why I want to migrate main Monix to to GH Actions is that Travis is slow. And GH Actions is right there, no need to do anything extra.

On the other hand w/ Travis you can quickly setup a build matrix, whereas in GH Actions it might take some work depending on complexity.

Pau Alarcón
@paualarco
@alexandru followed your recommendations on moving to GitHub workflow, and it is really much better now! :)
I've deployed the first snapshot :D
If you see something wrong on that configuration please do point it out
Pau Alarcón
@paualarco
Maybe I ve exagerated a bit saying much better haha but at the end I prefered now too
Pau Alarcón
@paualarco
mmmh, the project name looks familiar XD
Piotr Gawryś
@Avasil
Probably inspired by Kafka Connect but who knows
Pau Alarcón
@paualarco
yup, same as this one
Pau Alarcón
@paualarco
first release is out :D
I don't see why the same is not present here: https://search.maven.org/search?q=monix
Piotr Gawryś
@Avasil
Congrats!
Sometimes it takes some time to synchronize
Pau Alarcón
@paualarco
👍🏻
Alexandru Nedelcu
@alexandru
nice
Pau Alarcón
@paualarco
just released 0.1.0 which is the initial good one, last one was basically testing release process
shall I let people know by sharing it in the main monix channel?
Piotr Gawryś
@Avasil
Of course!
Pau Alarcón
@paualarco
cool :)
Piotr Gawryś
@Avasil
Do you work on it full time?
Pau Alarcón
@paualarco
no haha, I have my full time job but since the isolation I am WFH, so there is no time lost on public transport :P