-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release Tycho 2.6.0 #490
Comments
@mickaelistria @akurtakov I also sceduled a relase review as the release page says:
should I add this step to the release process documentation? |
@akurtakov can you create an announcement? Subject: Tycho 2.6.0 release We plan to release Tycho 2.6.0 at end of month. For details of new features and bugfixes, see release notes.
We plan to promote this release at end of month unless major regressions are found that can't be fixed at least one week before the release date. Regards, |
Announced intention to release done |
Xtext builds seem all fine. |
@mickaelistria @akurtakov can you take care of https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/169 it seems to require project-lead intervention? |
I don't think there is anything to do beyond waiting for review to complete. Did I miss something in particular? |
By the way, the release is not necessarily tied to the review now (many things changed recently in EDP). I thinkwethink can just move forward with the release and get review complete in parallel. |
Yes
Feel free to stage this as soon as it seems suitable then... 👍 |
I'd like to make you able to stage/promote release. Can you please perform the steps listed at https://central.sonatype.org/publish/publish-guide/#create-a-ticket-with-sonatype ? |
What specifically do you wan't me to do? The link seems to point to adding a new project, I assume tycho is already registered? I also have once deployed something to maven-central for another project so probably PGP key should be registered as well. |
OK, so if you think you have permission to stage to OSSRH already, please do it. Otherwise, we'll see the error code and ask for more permissions (I don't remember whether OSSRH permissions are per-project or not). |
@laeubi Any progress here? Could you push to sonatype OSSRH staging? |
I get error:
so it seems I'm not allowed for tycho. |
OK, please then open an issue against sonatype ossrh to ask for permissions for Tycho. Add me as CC so I can add a +1 as current maintainer. |
Artifacts are now deployed to sonartype |
|
Does |
I run
right before this call as indicated the document. |
But it seems tycho 2.5.0 tag is missing... |
strange https://github.com/eclipse/tycho/tags shows the tag by running git-tag locally does not show the tag... |
I have updated the release doc: ebd1cd9 |
Should I really close the repository? And what should one do with 'the staging repo URL' |
We recently agreed that the staging phase never identified any bug that couldn't be identified earlier on snapshots and decided to ignore the staging phase. So for release, we go directly from staging to release and can ignore the staging URL. |
I adjusted the docs: 8742450 How long does it takes between closing and the artifacts appear on central? |
In my experience, between 5 and 10 minutes. |
It seems I can't access |
dont you need to close AND release? |
No idea :-) Close was the only available action and the documentation indicates so... |
in xtext we hit close. then refresh button. then release |
After refresh it show |
https://central.sonatype.org/publish/release/ also says close and release |
looks like the repo still did not appear in central. can you check once more if your list is really empty? |
I can now see the repo again, but it has failures, one seems to be related to and it seems I used the wrong pgp key (will check that) |
I have updated the docs regarding the checks and how to perform the release of the staging repository: 5c83ecd |
Release is done for this now, I think we can omit advertising at [email protected] and for the twitter stuff I left this to someone else if desired (I dont use twitter at all ...). |
Announcement on tycho-dev is required as this is the "official" channel for Eclipse Foundation projects. |
Releasing Tycho 2.6.0
This describes the steps to perform a release of Tycho:
is:pr is:merged no:milestone
issues without milestone can be found withis:issue no:milestone is:closed
tycho-N.M.x
(e.g.tycho-2.4.x
) for upcoming release and push it to remote; this branch should remain frozen until the release, only major fixes for regressions could be merged in before release. Work can still happen regularly on themaster
branch.tycho-N.M.x
and adjust thestage('Deploy Snapshot')
to reference the new branch in the when conditional.master
to future release withmvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<NEXT_VERSION>-SNAPSHOT
and push to remote... Wait until review date (usually a week later)...
sonatype-nexus-staging
in~/.m2/settings.xml
git fetch eclipse tycho-N.M.x && git checkout FETCH_HEAD
to get the branch to be released-SNAPSHOT
withmvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<VERSION>
git add * && git commit
version changemvn clean deploy -Prelease -DforgeReleaseId=sonatype-nexus-staging -DforgeReleaseUrl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ -DskipTests
git tag tycho-<TYCHO_VERSION>
git push eclipse HEAD:tycho-N.M.x tycho-<TYCHO_VERSION>
(push commit to branch, and tag)mvn install site site:stage -DskipTests
and check the result fromtarget/staging
seems viable.target/staging/sitedocs
to the existingsitedocs
folder and then submit as Gerrit review (don't merge yet)The text was updated successfully, but these errors were encountered: