Need your vote on an issue

[Charlie Mordant]

Hi Jhipster Dev, how are you?

Jhipster has reached the 8.8.0 version which is close to 9.

I propose that this last version would be the last one with API freeze so that we can accelerate and rework the codebase in depth.

I posted an Issue there https://github.com/jhipster/generator-jhipster/issues/28428 in order to get vote and feedback on this concern.

What do you think?

Thanks,

--

Charlie Mordant

[Pascal GRIMAUD]

Hi Charlie,

Thanks for your suggestion.

I vote blank, as I didn't follow enough generator-jhipster to have an opinion on it

Pascal

--
You received this message because you are subscribed to the Google Groups "JHipster dev team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jhipster-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jhipster-dev/CANHkoGx9wmFOvgHiPSjykJJCfFuHZ6QeX6ZR1edzrm0bO%3DyX7w%40mail.gmail.com.

[MathieuAA]

Same

---

MAA

-------- Message d'origine --------

To view this discussion visit https://groups.google.com/d/msgid/jhipster-dev/CALUG8VvFuWwfuArH%2BY56VL%2B5njEs59rq36rVe4NXeDZsn9xpKw%40mail.gmail.com.

[Aurélien Mino]

Hi,

Ditto for me

Aurélien

To view this discussion visit https://groups.google.com/d/msgid/jhipster-dev/CALUG8VvFuWwfuArH%2BY56VL%2B5njEs59rq36rVe4NXeDZsn9xpKw%40mail.gmail.com.

[Renan Franca]

Same for me. I vote blank. 👍

To view this discussion visit https://groups.google.com/d/msgid/jhipster-dev/CACXN3_hQq6DvG2D%2BjNxRt7nNNJQeP9sqJKDwOh61kY1_9fQUMg%40mail.gmail.com.

[Vishal Mahajan]

I also don't follow enough :)

~~~
Cheers,
Vishal

To view this discussion visit https://groups.google.com/d/msgid/jhipster-dev/CAAF%2BGw1h%3DMpQCAd54O_NO1g81YKZu93_oJfSEeDOH4FisiVZjw%40mail.gmail.com.

[Marcelo Shima]

I vote for no.

I vote for having major versions following node EOL like most of node packages.

I’ve posted a technical response at the issue.

There are other reasons:

- JHipster 8 lifecycle has been crazy in internal work to port to typescript and make the core easier to maintain in the long run.

- In the past 2 releases we started releasing blueprints together with main generator.

- Some blueprints missed the first release and some blueprints had the release delayed in the second due to CI adjustments work. I hope to have every blueprint (released by me or Matt) released together with next main generator release.

- It’s VERY difficult to keep blueprints updated in a beta release cycle.

I need to work on yeoman libs (grouped-queue, mem-fs, mem-fs-editor, yeoman-generator, yeoman-environment, yeoman-test) breaking changes, which I plan to do only once node libs start dropping node 18 support.

Yeoman project is having a Governance update https://github.com/yeoman/yeoman/issues/1779

@JoshuaKGoldberg reached me offering help with Yeoman maintenance and since I maintain only Yeoman stack used by JHipster, I reached @SBoudrias and then others Yeoman members.

There aren't any big changes planned, but we can wait a couple of months.

I hope to have a stable cycle in the coming months until April when Node 18 goes EOL.

I don’t see enough reason to start breaking things now.

Marcelo

To view this discussion visit https://groups.google.com/d/msgid/jhipster-dev/CAG2s5vOvgHx_5hpMXu0AgRaw%3Dfx2QicJOtN1ZufxjBAaPhMP%3DA%40mail.gmail.com.