Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [starter-dev] Starter 1.0.0 staged
I agree. The active development branch,  in our case master does not need to be in sync with what's on the web page. The readme should be kept in sync with the ongoing work.

Ivar

On Wed, Mar 30, 2022, 13:51 <reza_rahman@xxxxxxxxx> wrote:
Ugh. Outlook is misbehaving on me. What I was trying to add is that 1.1 will take some time as I think it’s best to wait until we support at least the main non-commercial OSS servers. If we follow the strategy of a README that mainly documents the current branch/version it’s included in, there will be a difference between it and the GH page/current release. Indeed this might be true for some time. I suspect we will have active work to do in order to make this a truly compelling project for at least 12-14 months more. After that, things might stabilize, basically making any development branch and the current release mostly the same.

What are thoughts on this?

Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker

Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.
 
From: reza_rahman@xxxxxxxxx <reza_rahman@xxxxxxxxx>
Sent: Wednesday, March 30, 2022 8:44 AM
To: starter developer discussions <starter-dev@xxxxxxxxxxx>
Subject: Re: [starter-dev] Starter 1.0.0 staged
 
This is very good news indeed. Does it make sense to go ahead and issue the GH pages changes PR? Of course it could be merged after the release if needed.

Also, I tried to bring up this topic on PRs, but perhaps it’s a better discussion here. In the README, I think it’s best to document the code branch to which the README belongs. I typically try to document the current release and some key past releases in the project website/GH pages instead. Note, I typically also link to the project page/GH page from all READMEs to reduce any possible confusion with regards to versions/branches Is this a sensible strategy to adopt or have we found some other documentation strategy that works better? Note, I think 1.1 will take some time as I think it’s best to add suppo

Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker

Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.
 
From: starter-dev <starter-dev-bounces@xxxxxxxxxxx> on behalf of Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, March 30, 2022 3:51 AM
To: starter developer discussions <starter-dev@xxxxxxxxxxx>
Subject: [starter-dev] Starter 1.0.0 staged
 
Hi,

The 1.0.0 version of the starter is now staged at the Jakarta Staging Nexus.


Please try it out!

mvn archetype:generate -DarchetypeGroupId=org.eclipse.starter -DarchetypeArtifactId=jakarta-starter -DarchetypeVersion=1.0.0 -Pstaging


You will need to have the staging repository configured on your system, e.g in a staging profile as I have in the example above. Also, make sure to delete the starter from your local repository if you have built it yourself, so you are sure you are testing the right artifact.

In that case, add the following to your settings.xml file:

   <profiles>
          <profile>
            <id>staging</id>
            <activation>
                <activeByDefault>false</activeByDefault>
            </activation>
            <repositories>
                <repository>
                    <id>jakarta-nexus-staging</id>
                    <name>Sonatype Nexus Staging</name>
                    <url>https://jakarta.oss.sonatype.org/content/groups/staging/</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </repository>
            </repositories>
          </profile>
      </profiles>

I have updated the README file in the release branch with the correct groupId and version. This will be merged into master when the release is done. So there is no need to update the README file in the master branch before that.

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 

_______________________________________________
starter-dev mailing list
starter-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/starter-dev

Back to the top