Comments (19)
Yes, since scala-swing is not officially supported, the cycle from major version to major version is faster, we didn't even have a 2.1.x
branch. So I'd suggest to keep it simple and merge to work
and once released back to main
.
from scala-swing.
released — artifacts should arrive at e.g. https://repo1.maven.org/maven2/org/scala-lang/modules/scala-swing_2.13/3.0.0/ soon
from scala-swing.
not sure if you want to make a 3.0.x branch, or just let 3.0.x development proceed on the default work
branch
do you want to do a 3.0.0-M1 or a 3.0.0-RC1, or just go straight to 3.0.0? the main difference would be that users will expect 3.0.0 to lock bincompat
from scala-swing.
I think, since it makes sense to publish the new stable version 2.2.0, it should be just merged into work
, and from there straight into main
. I also find it easiest to remember that main
has the latest stable (non-SNAPSHOT) version. So perhaps merge to work
, then I tag v2.2.0
, then merge to main. I don't think we need a dedicated 3.0.x branch.
from scala-swing.
gah, I forgot that we had both work
and main
in this repo
I'm fine with whatever you decide
from scala-swing.
It's important that the artifacts released to maven are built on JDK 8 not 11; because there might be some API changes in Java, so to be on the safe side. I don't think we need to enforce JDK 6 for Scala 2.11 any longer.
from scala-swing.
It's important that the artifacts released to maven are built on JDK 8 not 11; because there might be some API changes in Java, so to be on the safe side.
agree. the isReleaseJob
logic in build.sh
ensures that.
I don't think we need to enforce JDK 6 for Scala 2.11 any longer.
agree
from scala-swing.
I think artifacts have been staged at sonatype: https://travis-ci.com/github/scala/scala-swing/builds/199608189
from scala-swing.
We ended up with four staging repos, all containing 2.13 artifacts only. I dropped them
Let's merge #127 and try again
from scala-swing.
Okay, let's try again. You can either delete and recreate the 3.0.0 tag, or just push a 3.0.1 tag 🤷♂️
I won't be surprised if we need to do at least one more round of this, but 🤞
from scala-swing.
ok, will delete and re-push
from scala-swing.
dammit
2020-11-10 18:12:51.962Z info [SonatypeService] sonatypeProfileName : org.scala-lang - (SonatypeService.scala:25)
2020-11-10 18:12:51.995Z error [Sonatype]
java.io.IOException: Supplied file /home/travis/build/scala/scala-swing/target/sonatype-staging/3.0.0 is a not an existing directory!
at org.sonatype.spice.zapper.fs.AbstractDirectory.<init>(AbstractDirectory.java:32)
at org.sonatype.spice.zapper.fs.DirectoryIOSource.<init>(DirectoryIOSource.java:68)
at org.sonatype.spice.zapper.fs.DirectoryIOSource.<init>(DirectoryIOSource.java:59)
I don't know what this is. I'm out of time, I'll have to look at it a bit later
from scala-swing.
Google brings up this, which might be the same cause: xerial/sbt-sonatype#103
from scala-swing.
Also: sbt/sbt-ci-release#122
from scala-swing.
Might be worth an attempt to revert to sbt 1.3 ; I think there are quite a few things that are different and/or not yet ironed out in 1.4.
from scala-swing.
Looking into build.sh
and comparing with the one of scala-xml, we might just set projectPrefix="swing/"
and can remove the publish / skip := true
for the other sub-projects AFAICS. that might also clear up any strangeness with regard to the synthetic root project? Should I try that?
from scala-swing.
Ok, almost there: https://travis-ci.com/github/scala/scala-swing/builds/200029393
Of course dottydoc was giving us the middle finger in the last moment. I don't know why it's not even disabled by default. It essentially never works. I will disable dottydoc and push again.
from scala-swing.
All green, check contents at sonatype.
from scala-swing.
Thanks for figuring this out.
Over at https://github.com/scala/scala-swing/releases , looks like there's a draft release which can be deleted, and then release notes added to https://github.com/scala/scala-swing/releases/tag/v3.0.0
from scala-swing.
Related Issues (20)
- Nested class shadowing in "override" position HOT 3
- Missing support for JInternalFrame and JDesktopPane
- Add support for Dotty HOT 6
- ScrollBar should publish adjustment event
- Add release process info to README
- Release for Dotty 3.0.0-M2 HOT 8
- Release for Scala 3.0.0-M3 HOT 1
- Release for Scala 3.0.0-RC1 HOT 2
- Build should declare a `versionScheme`
- Release for Scala 3.0.0-RC2 HOT 1
- SplitPane.lastDividerLocation missing HOT 1
- Release for Scala 3.0.0-RC3 HOT 1
- Release for Scala 3.0.0 HOT 1
- Publish for Scala 3.0.0 HOT 2
- which jdk version is adviced ? HOT 1
- API documentation links to 404 HOT 2
- How to override paint() method from subclass of frame? HOT 2
- Accessing FileChooser results HOT 2
- Scala Setup Troubles
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from scala-swing.