outcome? What you apparently strive for will de facto only be reached by
asking the committers of all projects, not anybody else. You reach
absolutely not what you want if the PMC says "yes, good idea" but some
committers simply do not follow because they possibly have a different
opinion.
Besides that, I will keep telling what the EDP says as long as I have
the impression that it is either not understood or intentionally ignored.
-Markus
*From:*Bill Shannon [mailto:bill.shannon@xxxxxxxxxx]
*Sent:* Mittwoch, 31. Oktober 2018 18:19
*To:* EE4J PMC Discussions; Markus KARG
*Subject:* Re: [ee4j-pmc] git tags naming convention?
Markus, you really are not helping by continuing to repeat your mantra.
Some of us /want/ to do things in a consistent way across the
community. Unless your goal is to /force/ every project to be
different, please just accept that you're allowed to do things
differently in your projects, but some of the rest of us might want to
do things the same way across multiple project, on purpose. We're not
going to tell you that you have to do things the same way, but please
don't tell us that we /can't/ conspire among ourselves to do things the
same way.
Thanks.
Markus KARG wrote on 10/30/2018 11:07 PM:
I know Bill and others don't like to hear it anymore, but unless
there is an urgent need to decide this topic by the PMC, according
to the EDP this is up to each project to decide or even let the
committer himself decide.
-Markus
*From:*ee4j-pmc-bounces@xxxxxxxxxxx
<mailto:ee4j-pmc-bounces@xxxxxxxxxxx>
[mailto:ee4j-pmc-bounces@xxxxxxxxxxx] *On Behalf Of *Kevin Sutter
*Sent:* Dienstag, 30. Oktober 2018 21:18
*To:* EE4J PMC Discussions
*Subject:* Re: [ee4j-pmc] git tags naming convention?
I agree. We use annotated tags when releasing MicroProfile
releases. I think we should continue that practice with Jakarta EE.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail: sutter@xxxxxxxxxx <mailto:sutter@xxxxxxxxxx> Twitter:
@kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
ee4j-pmc-bounces@xxxxxxxxxxx <mailto:ee4j-pmc-bounces@xxxxxxxxxxx>
wrote on 10/30/2018 01:28:54 PM:
> From: Raymond Auge <raymond.auge@xxxxxxxxxxx <mailto:raymond.auge@xxxxxxxxxxx>>
> To: ee4j-pmc@xxxxxxxxxxx <mailto:ee4j-pmc@xxxxxxxxxxx>
> Date: 10/30/2018 01:29 PM
> Subject: Re: [ee4j-pmc] git tags naming convention?
> Sent by: ee4j-pmc-bounces@xxxxxxxxxxx <mailto:ee4j-pmc-bounces@xxxxxxxxxxx>
>
> I think having recourse to see _who_ created the tag (annotated
> tags) is more useful than not.
>
> - Ray
>
> On Tue, Oct 30, 2018 at 2:23 PM Bill Shannon <bill.shannon@xxxxxxxxxx <mailto:bill.shannon@xxxxxxxxxx>> wrote:
> (Apparently no one cares about this stuff but I'll ask anyway...)
>
> Assuming the PMC recommendation is to use just the version number as
> the tag, do people prefer git lightweight tags or git annotated tags?
> Ivar Grimstad wrote on 10/01/2018 10:43 PM:
> We have not defined any conventions for EE4J for this. Personally, I
> like naming the tag as the version number of the released artifact.
>
> Should we define EE4J-wide conventions or just leave it to the projects?
>
> Ivar
>
> On Tue, Oct 2, 2018 at 12:58 AM Bill Shannon <bill.shannon@xxxxxxxxxx <mailto:bill.shannon@xxxxxxxxxx>> wrote:
> Is there an EE4J-wide convention for how to name the git tags for
> releases of various sorts?
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx <mailto:ee4j-pmc@xxxxxxxxxxx>
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
> --
> Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader
>
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx <mailto:ee4j-pmc@xxxxxxxxxxx>
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
>
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx <mailto:ee4j-pmc@xxxxxxxxxxx>
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/ee4j-pmc
>
>
> --
> Raymond Augé (@rotty3000)
> Senior Software Architect Liferay, Inc. (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance (@OSGiAlliance)
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx <mailto:ee4j-pmc@xxxxxxxxxxx>
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://urldefense.proofpoint.com/v2/url?
> u=https-3A__www.eclipse.org_mailman_listinfo_ee4j-2Dpmc&d=DwICAg&c=jf_iaSHvJObTbx-
> siA1ZOg&r=R9dtOS3afYnRUmu_zogmh0VnVYl2tse_V7QBUA9yr_4&m=Cm4cgUhrLD_uVH9--
> unOi7xolch9Ps9U5KcUxYzrJ04&s=oTbWjeFsbbgP3UCu8xWwwRAq3jnwsu_NVhdqE9hqUj4&e=
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx <mailto:ee4j-pmc@xxxxxxxxxxx>
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc