I was thinking to talk about these points:
- What are Conventional Commits
- Why Conventional Commits
- Plugin Development (max time here)
- Demo
- Q&A
Is there anything I should add/remove from this?
I made some suggestion to your slide
Thank you so much for it, I will expand on your suggestions, I just wanted to clarify that, the content of the slide are to be removed (my bad that it got copied along with the template)
@garethjevans: would you be available for a meeting tomorrow (7:00 am UTC) as usual
@adi10hero:matrix.org ^^^
Hi all, if it's ok for you I'd like to work on the @garethjevans proposition in the #23 to add prerelease information. If your are agree can you assign to me the issue please ?
@garethjevans, I have some difficulties while running the plugin, can we please have a discussion tomorrow. Also, can we have the meeting a little later than the usual time? I need to go collect my laptop in the morning, so I am unsure when I will be back or how much time it will take, I am expecting to be back by 8-9 am UTC
did you get anywhere with setting up some test github projects?
1 reply
PS: The reason I did not go with Make, Node or Gradle was, I primarily use Windows so I am not really comfortable with Make & as far as Node and Gradle go, they take a lot of time to build :P
2 replies
@garethjevans: Using this repo (https://github.com/ADI10HERO/maven-sample-cc) for demo
Making a python project now
Making a python project now
1 reply
i only have 5 mins, maybe less
@adi10hero:matrix.org great presentation and demo. demoing live is always nervous especially when a process takes slightly longer than you expect. Tara's suggestion was really interesting, I'm not sure how we'd do that but it could be something to look into in the future
1 reply
@ADI10HERO: I agree with @garethjevans you presentation was really great and you successfully managed the live demo part, congrats
1 reply
I was working on the blog post, plan was to make a draft a little earlier than the deadline (31st july)
@philippart-s: I was reviewing the pre-release PR and just wanted to check my understanding...
If there's a minor version bump on previously tagged:
If there's a minor version bump on previously tagged:
0.1.0-alpha, then it would become 0.2.0-alpha, right?
9 replies
I've pushed the first draft of the blog, please find it here (https://github.com/ADI10HERO/jenkins.io/blob/mid-term-blog-cc/content/blog/2021/07/2021-07-27-introducing-conventional-commits-plugin-for-jenkins.adoc)
Things I plan to add:
- link to the presentation video
- discourse link update
- Try to think of a good "start" of the blog (after the opengraph image) which establishes a few things like its a gsoc project, mentions the mentors, maybe a summary of the whole blog.
PS: docker is not working on both windows and linux boot so couldn't really test using the site generator. So please let me know in case something doesn't look right.
I've just create this bug #76 , perhaps it's me that don't understand well how the plugin must be works :wink:
@garethjevans & @adi10hero:matrix.org
Before go further I think we'll need to discuss on the strategy to bump version with prerelease information already existing or not.
Here is the use cases and what I have understand with our conversations and what I propose for other cases :
| current version | Breaking change commit msg | Feature commit msg | Other or empty commit msg | prerelease option | preservePreRelease | Output |
|---|---|---|---|---|---|---|
| 0.1.0 | X | - | - | - | - | 1.0.0 |
| 0.1.0 | - | X | - | - | - | 0.2.0 |
| 0.1.0 | - | - | X | - | - | 0.1.1 |
| 0.1.0 | X | - | - | alpha | - | 1.0.0-alpha |
| 0.1.0 | - | X | - | alpha | - | 0.2.0-alpha |
| 0.1.0 | - | - | X | alpha | - | 0.1.1-alpha |
| 0.1.0-alpha | X | - | - | - | - | 1.0.0 |
| 0.1.0-alpha | - | X | - | - | - | 0.1.0 |
| 0.1.0-alpha | - | - | X | - | - | 0.1.1 |
| 0.1.0-alpha | X | - | - | - | X | 1.0.0-alpha |
| 0.1.0-alpha | - | X | - | - | X | 0.2.0-alpha |
| 0.1.0-alpha | - | - | X | - | X | 0.1.1-alpha |
| 0.1.0-alpha | X | - | - | beta | - | 1.0.0-beta |
| 0.1.0-alpha | - | X | - | beta | - | 0.2.0-beta |
| 0.1.0-alpha | - | - | X | beta | - | 0.1.1-beta |
There is also the possibility to increment the prelease version : 0.1.0-alpha :arrow_right: 0.1.0-alpha.1.
It can be an alternative for the case where there is no commit message and the version is with a prerelease version (line 12 of the table).
12 replies
@mentors, PR for buildmetadata made (jenkinsci/conventional-commits-plugin#78), ready to be reviewed
@philippart-s: I am unable to add your name under "Request Reviews"
3 replies
Ohh actually unfortunately I wasn't able to get my docker working so could not test the changeslocally 😅
@all, Shall we start a discourse discussion which introduces conventional commits plugin? If yes, what shall the body of the post contain?
1 reply