+1 for the deprecation

Am Fr., 29. Nov. 2024 um 09:58 Uhr schrieb Stefan Seifert
<[email protected]>:

> in preparation of a new sling starter release, I discovered that we
> currently have 10 archetypes [1] and 1 archetype-parent github projects.
>
> only one archetype is currently actively maintained, the
> sling-project-archetype [2]. the others, although partially mentioned on
> our documentation page [3], are not actively touched since 2015/2018,
> except sling-content-package-archetype [4] which was added in 2020 but also
> did not get any love since them.
>
> having archetypes to start a new project is great - but starting a new
> project with dependencies that are more than 5 years old and often using
> outdated patterns and tooling is very counterproductive.
>
> so, also after as short discussion with robert, I propose to:
>
> 1. mark all archetype repos from [1] (including sling-archetype-parent,
> but excluding sling-project-archetype) as deprecated and do not touch them
> any longer
> 2. replace the documentation page [3] with a link to the only remaining
> archetype [2]
>
>
> Please vote to approve this proposal:
>
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> stefan
>
> [1]
> https://github.com/orgs/apache/repositories?language=&q=sling+archetype+sort%3Aname-asc&sort=&type=all
> [2] https://github.com/apache/sling-project-archetype
> [3]
> https://sling.apache.org/documentation/development/maven-archetypes.html
> [4] https://github.com/apache/sling-content-package-archetype
>


-- 
https://cqdump.joerghoh.de

Reply via email to