You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Jean-Louis MONTEIRO <je...@gmail.com> on 2012/10/08 17:19:33 UTC
[RESULT] Paw-print logo to become official TomEE logo
Hi guys,
Following what we decided 4 months ago (more than 40 days).
So even if someone else disagree, the paw-print will be used as the
official Apache TomEE logo.
Jean-Louis
2012/6/4 Romain Manni-Bucau <rm...@gmail.com>
> i globally agree even if i would have had it on the 12th.
>
> - Romain
>
>
> 2012/6/4 David Blevins <da...@gmail.com>
>
> >
> > On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote:
> >
> > > If we get a higher vote for the pawprint sum(+1/-1) vs (waitFor40days)
> > we'll just go with it - pending David's decision of course.
> >
> > All things are project decisions of course. I get one vote like everyone
> > else :)
> >
> > My vote would be for the 40 day logo contest. If we don't do it we'd be
> > passing up a great chance to make some noise, attract some attention and
> > get several people contributing logos to the project which means more
> > people contributing to the project.
> >
> > Would be a shame to miss out on all that buzz and excitement.
> >
> >
> > -David
> >
> >
>
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by Neale Rudd <ne...@metawerx.net>.
+1
----- Original Message -----
From: "Thiago Veronezi" <th...@veronezi.org>
To: <de...@openejb.apache.org>
Sent: Tuesday, October 09, 2012 4:21 AM
Subject: Re: [RESULT] Paw-print logo to become official TomEE logo
> +1
>
>
> On Mon, Oct 8, 2012 at 12:24 PM, Romain Manni-Bucau
> <rm...@gmail.com>wrote:
>
>> +1
>>
>> *Romain Manni-Bucau*
>> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
>> *Blog: **http://rmannibucau.wordpress.com/*<
>> http://rmannibucau.wordpress.com/>
>> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
>> *Github: https://github.com/rmannibucau*
>>
>>
>>
>>
>> 2012/10/8 dsh <da...@gmail.com>
>>
>> > :D I think for the time being we should go with this one. If someone
>> > does a better logo in the future we could re-role a vote at any time.
>> >
>> > Cheers
>> > Daniel
>> >
>> > On Mon, Oct 8, 2012 at 5:21 PM, Jean-Louis MONTEIRO
>> > <je...@gmail.com>
>> > wrote:
>> > >>> So even if someone else disagree, the paw-print will be used as the
>> > > official Apache TomEE logo.
>> > > Sorry, wrong sentence, the good one is:
>> > >
>> > > So except if someone disagree, the paw-print will be used as the
>> official
>> > > Apache TomEE logo.
>> > >
>> > > JLouis
>> > >
>> > >
>> > > 2012/10/8 Jean-Louis MONTEIRO <je...@gmail.com>
>> > >
>> > >> Hi guys,
>> > >>
>> > >> Following what we decided 4 months ago (more than 40 days).
>> > >> So even if someone else disagree, the paw-print will be used as the
>> > >> official Apache TomEE logo.
>> > >>
>> > >> Jean-Louis
>> > >>
>> > >>
>> > >>
>> > >> 2012/6/4 Romain Manni-Bucau <rm...@gmail.com>
>> > >>
>> > >>> i globally agree even if i would have had it on the 12th.
>> > >>>
>> > >>> - Romain
>> > >>>
>> > >>>
>> > >>> 2012/6/4 David Blevins <da...@gmail.com>
>> > >>>
>> > >>> >
>> > >>> > On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote:
>> > >>> >
>> > >>> > > If we get a higher vote for the pawprint sum(+1/-1) vs
>> > (waitFor40days)
>> > >>> > we'll just go with it - pending David's decision of course.
>> > >>> >
>> > >>> > All things are project decisions of course. I get one vote like
>> > >>> everyone
>> > >>> > else :)
>> > >>> >
>> > >>> > My vote would be for the 40 day logo contest. If we don't do it
>> > we'd be
>> > >>> > passing up a great chance to make some noise, attract some
>> attention
>> > and
>> > >>> > get several people contributing logos to the project which means
>> more
>> > >>> > people contributing to the project.
>> > >>> >
>> > >>> > Would be a shame to miss out on all that buzz and excitement.
>> > >>> >
>> > >>> >
>> > >>> > -David
>> > >>> >
>> > >>> >
>> > >>>
>> > >>
>> > >>
>> >
>>
>
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by Thiago Veronezi <th...@veronezi.org>.
+1
On Mon, Oct 8, 2012 at 12:24 PM, Romain Manni-Bucau
<rm...@gmail.com>wrote:
> +1
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<
> http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
>
>
>
>
> 2012/10/8 dsh <da...@gmail.com>
>
> > :D I think for the time being we should go with this one. If someone
> > does a better logo in the future we could re-role a vote at any time.
> >
> > Cheers
> > Daniel
> >
> > On Mon, Oct 8, 2012 at 5:21 PM, Jean-Louis MONTEIRO <je...@gmail.com>
> > wrote:
> > >>> So even if someone else disagree, the paw-print will be used as the
> > > official Apache TomEE logo.
> > > Sorry, wrong sentence, the good one is:
> > >
> > > So except if someone disagree, the paw-print will be used as the
> official
> > > Apache TomEE logo.
> > >
> > > JLouis
> > >
> > >
> > > 2012/10/8 Jean-Louis MONTEIRO <je...@gmail.com>
> > >
> > >> Hi guys,
> > >>
> > >> Following what we decided 4 months ago (more than 40 days).
> > >> So even if someone else disagree, the paw-print will be used as the
> > >> official Apache TomEE logo.
> > >>
> > >> Jean-Louis
> > >>
> > >>
> > >>
> > >> 2012/6/4 Romain Manni-Bucau <rm...@gmail.com>
> > >>
> > >>> i globally agree even if i would have had it on the 12th.
> > >>>
> > >>> - Romain
> > >>>
> > >>>
> > >>> 2012/6/4 David Blevins <da...@gmail.com>
> > >>>
> > >>> >
> > >>> > On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote:
> > >>> >
> > >>> > > If we get a higher vote for the pawprint sum(+1/-1) vs
> > (waitFor40days)
> > >>> > we'll just go with it - pending David's decision of course.
> > >>> >
> > >>> > All things are project decisions of course. I get one vote like
> > >>> everyone
> > >>> > else :)
> > >>> >
> > >>> > My vote would be for the 40 day logo contest. If we don't do it
> > we'd be
> > >>> > passing up a great chance to make some noise, attract some
> attention
> > and
> > >>> > get several people contributing logos to the project which means
> more
> > >>> > people contributing to the project.
> > >>> >
> > >>> > Would be a shame to miss out on all that buzz and excitement.
> > >>> >
> > >>> >
> > >>> > -David
> > >>> >
> > >>> >
> > >>>
> > >>
> > >>
> >
>
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by Romain Manni-Bucau <rm...@gmail.com>.
+1
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2012/10/8 dsh <da...@gmail.com>
> :D I think for the time being we should go with this one. If someone
> does a better logo in the future we could re-role a vote at any time.
>
> Cheers
> Daniel
>
> On Mon, Oct 8, 2012 at 5:21 PM, Jean-Louis MONTEIRO <je...@gmail.com>
> wrote:
> >>> So even if someone else disagree, the paw-print will be used as the
> > official Apache TomEE logo.
> > Sorry, wrong sentence, the good one is:
> >
> > So except if someone disagree, the paw-print will be used as the official
> > Apache TomEE logo.
> >
> > JLouis
> >
> >
> > 2012/10/8 Jean-Louis MONTEIRO <je...@gmail.com>
> >
> >> Hi guys,
> >>
> >> Following what we decided 4 months ago (more than 40 days).
> >> So even if someone else disagree, the paw-print will be used as the
> >> official Apache TomEE logo.
> >>
> >> Jean-Louis
> >>
> >>
> >>
> >> 2012/6/4 Romain Manni-Bucau <rm...@gmail.com>
> >>
> >>> i globally agree even if i would have had it on the 12th.
> >>>
> >>> - Romain
> >>>
> >>>
> >>> 2012/6/4 David Blevins <da...@gmail.com>
> >>>
> >>> >
> >>> > On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote:
> >>> >
> >>> > > If we get a higher vote for the pawprint sum(+1/-1) vs
> (waitFor40days)
> >>> > we'll just go with it - pending David's decision of course.
> >>> >
> >>> > All things are project decisions of course. I get one vote like
> >>> everyone
> >>> > else :)
> >>> >
> >>> > My vote would be for the 40 day logo contest. If we don't do it
> we'd be
> >>> > passing up a great chance to make some noise, attract some attention
> and
> >>> > get several people contributing logos to the project which means more
> >>> > people contributing to the project.
> >>> >
> >>> > Would be a shame to miss out on all that buzz and excitement.
> >>> >
> >>> >
> >>> > -David
> >>> >
> >>> >
> >>>
> >>
> >>
>
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by dsh <da...@gmail.com>.
:D I think for the time being we should go with this one. If someone
does a better logo in the future we could re-role a vote at any time.
Cheers
Daniel
On Mon, Oct 8, 2012 at 5:21 PM, Jean-Louis MONTEIRO <je...@gmail.com> wrote:
>>> So even if someone else disagree, the paw-print will be used as the
> official Apache TomEE logo.
> Sorry, wrong sentence, the good one is:
>
> So except if someone disagree, the paw-print will be used as the official
> Apache TomEE logo.
>
> JLouis
>
>
> 2012/10/8 Jean-Louis MONTEIRO <je...@gmail.com>
>
>> Hi guys,
>>
>> Following what we decided 4 months ago (more than 40 days).
>> So even if someone else disagree, the paw-print will be used as the
>> official Apache TomEE logo.
>>
>> Jean-Louis
>>
>>
>>
>> 2012/6/4 Romain Manni-Bucau <rm...@gmail.com>
>>
>>> i globally agree even if i would have had it on the 12th.
>>>
>>> - Romain
>>>
>>>
>>> 2012/6/4 David Blevins <da...@gmail.com>
>>>
>>> >
>>> > On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote:
>>> >
>>> > > If we get a higher vote for the pawprint sum(+1/-1) vs (waitFor40days)
>>> > we'll just go with it - pending David's decision of course.
>>> >
>>> > All things are project decisions of course. I get one vote like
>>> everyone
>>> > else :)
>>> >
>>> > My vote would be for the 40 day logo contest. If we don't do it we'd be
>>> > passing up a great chance to make some noise, attract some attention and
>>> > get several people contributing logos to the project which means more
>>> > people contributing to the project.
>>> >
>>> > Would be a shame to miss out on all that buzz and excitement.
>>> >
>>> >
>>> > -David
>>> >
>>> >
>>>
>>
>>
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
>> So even if someone else disagree, the paw-print will be used as the
official Apache TomEE logo.
Sorry, wrong sentence, the good one is:
So except if someone disagree, the paw-print will be used as the official
Apache TomEE logo.
JLouis
2012/10/8 Jean-Louis MONTEIRO <je...@gmail.com>
> Hi guys,
>
> Following what we decided 4 months ago (more than 40 days).
> So even if someone else disagree, the paw-print will be used as the
> official Apache TomEE logo.
>
> Jean-Louis
>
>
>
> 2012/6/4 Romain Manni-Bucau <rm...@gmail.com>
>
>> i globally agree even if i would have had it on the 12th.
>>
>> - Romain
>>
>>
>> 2012/6/4 David Blevins <da...@gmail.com>
>>
>> >
>> > On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote:
>> >
>> > > If we get a higher vote for the pawprint sum(+1/-1) vs (waitFor40days)
>> > we'll just go with it - pending David's decision of course.
>> >
>> > All things are project decisions of course. I get one vote like
>> everyone
>> > else :)
>> >
>> > My vote would be for the 40 day logo contest. If we don't do it we'd be
>> > passing up a great chance to make some noise, attract some attention and
>> > get several people contributing logos to the project which means more
>> > people contributing to the project.
>> >
>> > Would be a shame to miss out on all that buzz and excitement.
>> >
>> >
>> > -David
>> >
>> >
>>
>
>
Re: 1.5 Clarification
Posted by Romain Manni-Bucau <rm...@gmail.com>.
just a quick note: some example uses tomee though the tomee maven plugin or
arquillian ;)
maybe that's not enough explicit...
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2012/10/10 Neale Rudd <ne...@metawerx.net>
> Hi David,
>
>
> Do you mean like this?
>>> - http://tomee.apache.org/tomee-**1.5.0-release-notes.html<http://tomee.apache.org/tomee-1.5.0-release-notes.html>
>>> Or do you want all the release notes from the previous releases? Or did
>>> you mean something else?
>>>
>>
> Yes that's pretty good, guess I'd like a little more detail in general.
> eg: http://tomcat.apache.org/**tomcat-7.0-doc/changelog.html<http://tomcat.apache.org/tomcat-7.0-doc/changelog.html>
> The sentences describe why the change was made a little more whereas the
> tomee ones seem to be a copy of the jira title, so it takes a lot longer to
> see what and why changed.
> Also the tomcat one shows change by version number and the final committer
> (just for fun)
>
>
> Any ideas on how we can improve these to better match what you imagine?
>>> - http://tomee.apache.org/**examples-trunk/index.html<http://tomee.apache.org/examples-trunk/index.html>
>>>
>> These are great examples, but none are bundled with TomEE. I understand
> they can't be put into a production folder (like Tomcat does) but maybe
> then can be easily moved into webapps to try things out rather than
> downloading them. Just an opinion though. I understand you want to keep
> download size low.
>
>
> - upgrade notes (per revision + per major revision) - very important if
>>>>> used in a production system, I review these personally for every Tomcat
>>>>> subrelease and make changes to our templates as necessary
>>>>>
>>>> We definitely don't have anything there. Wondering how we could
>>> realistically capture that information. Getting something in place and
>>> getting people to use it are always difficult initiatives.
>>>
>> This would include a simple migration guide from 1.0.x to 1.5.x. ie: if
> your app runs in 1.0, what is going to break in 1.5? what needs to be
> changed? what do we need to be aware of? ie: the /openejb app being
> change to /tomee pre the 1.0 release would be a good example of a major
> change. Any information available here can be critical for assisting smooth
> transitions to newer versions, and that means less time supporting people
> on older revisions. Much easier to say "can you try it on 1.5? the
> migration docs are here: http...".
>
> And more docs :)
>>>
>> Yes - I'd definitely start with configuration reference stuff. ie: a
> description of all non-Tomcat config files and their components
>
> - alpha, beta, rc -> release strategy (this would have avoided the 1.5.0
>>>>> win issue)
>>>>>
>>>> We did have about 3 sets of potential release binaries and another 2-3
>>> sets of preview binaries (not quite ready for voting).
>>>
>> I think Tomcat generally follows this pattern, not sure if it's the
> Apache standard way, but it seems to generate pretty stable releases:
> - an alpha-release (people start trying out the new version, normal users
> never download a snapshot)
> - a beta-release (more heavy testing, because it's about to go live)
> - a release-candidate (more testing, people have a very last chance to
> deploy and test at their workplace, or risk missing all the new features
> for another N months)
> - release vote (2-3 days or whatever is decided/mandated)
> - release
>
> Then you immediately branch whatever branches you want, such as a 1.5.1
> for fixes-only, a 1.6.0 for the next main version. Whether or not Tomcat
> upgrades go into the 1.5.1 or the 1.6.0 is up to you.
>
> Then within 2 months you release 1.6.0. The 1.5.1 would be released in
> the case of important new fixes or deployment problems (eg: the windows
> 1.5.0 issue), and never include new features.
>
> Something like that?
>
>
> Best Regards,
> Neale
>
>
>
> ----- Original Message ----- From: "David Blevins" <
> david.blevins@gmail.com>
> To: <de...@openejb.apache.org>
> Sent: Tuesday, October 09, 2012 6:42 AM
>
> Subject: Re: 1.5 Clarification
>
>
>
> On Oct 8, 2012, at 12:15 PM, Neale Rudd wrote:
>
> Suggest following Tomcat-style change-log. One file which has all 1.x.x
>> release notes with a one-liner describing the change/feature and a link to
>> Jira if people want to investigate.
>>
>
> Do you mean like this?
> - http://tomee.apache.org/tomee-**1.5.0-release-notes.html<http://tomee.apache.org/tomee-1.5.0-release-notes.html>
>
> Or do you want all the release notes from the previous releases? Or did
> you mean something else?
>
> - simple examples (helps get people started, helps to demonstrate why
>> TomEE is useful to their company)
>>
>
> Any ideas on how we can improve these to better match what you imagine?
> - http://tomee.apache.org/**examples-trunk/index.html<http://tomee.apache.org/examples-trunk/index.html>
>
> - easy to navigate docs (avoids ??% of the questions on the user list,
>> freeing up dev time, which is *so* important for bugfixes and new features)
>>
>
> And more docs :)
>
> - integration with leading IDE's (TomEE could at least have excellent
>> docs on how to use Tomcat IDE settings, linked directly from the main web
>> page for easy transition)
>>
>
> We've got a video and doc for Eclipse. The video isn't linked from the
> doc page and the doc ins't linked from the main page. Help welcome there
> -- from anyone reading. Here are the bits if someone wants to improve
> things:
>
> - http://tomee.apache.org/tomee-**and-eclipse.html<http://tomee.apache.org/tomee-and-eclipse.html>
> - http://www.youtube.com/watch?**v=Lr8pxEACVRI<http://www.youtube.com/watch?v=Lr8pxEACVRI>
>
> - easy to navigate release notes (easy to see what's changed, in 2
>> minutes, without browsing dev@ or long jiras)
>>
>
> Any ideas on how to make this easier to navigate?
>
> - http://tomee.apache.org/tomee-**1.5.0-release-notes.html<http://tomee.apache.org/tomee-1.5.0-release-notes.html>
>
> - upgrade notes (per revision + per major revision) - very important if
>> used in a production system, I review these personally for every Tomcat
>> subrelease and make changes to our templates as necessary
>>
> We definitely don't have anything there. Wondering how we could
> realistically capture that information. Getting something in place and
> getting people to use it are always difficult initiatives.
>
> - frequent releases (and TomEE should keep-up, like MariaDB does with
>> MySQL - this is critical IMHO)
>>
>
> Completely agreed.
>
> - alpha, beta, rc -> release strategy (this would have avoided the 1.5.0
>> win issue)
>>
>
> Can you elaborate on the flow you have in mind? We do have restrictions
> on the workflow Apache allows, so we may or may not be able to do that, but
> it'll be good to understand.
>
> We did have about 3 sets of potential release binaries and another 2-3
> sets of preview binaries (not quite ready for voting).
>
>
> -David
>
> ----- Original Message ----- From: "Neale Rudd" <ne...@metawerx.net>
>> To: <de...@openejb.apache.org>
>> Sent: Tuesday, October 09, 2012 6:00 AM
>> Subject: Re: 1.5 Clarification
>>
>>
>> You're right - proxy or browser cache - I clicked Reload in Chrome and
>>> got the 1.5.0 release on tomee.apache.org finally.
>>>
>>> Some sort of too-long cache time problem? I've checked this every day
>>> and only got 1.5.0 just now after I clicked Reload. Might be a problem for
>>> future releases.
>>>
>>> Best Regards,
>>> Neale
>>>
>>> ----- Original Message ----- From: "David Blevins" <
>>> david.blevins@gmail.com>
>>> To: <de...@openejb.apache.org>
>>> Sent: Tuesday, October 09, 2012 5:55 AM
>>> Subject: Re: 1.5 Clarification
>>>
>>>
>>>
>>> On Oct 8, 2012, at 11:33 AM, Neale Rudd wrote:
>>>
>>> - http://tomee.apache.org/**downloads.html<http://tomee.apache.org/downloads.html>shows 1.0.0, but
>>>> http://openejb.apache.org/**downloads.html<http://openejb.apache.org/downloads.html>shows 1.5.0 as latest release, aren't these the same site?
>>>>
>>>
>>> That's probably a browser caching issue. The tomee.apache.org is just
>>> an alias.
>>>
>>>
>>> -David
>>>
>>
>>
>
Re: 1.5 Clarification
Posted by Neale Rudd <ne...@metawerx.net>.
One other great doc I'd like to see - maybe you have it already?
Differences between Tomcat and TomEE if you're used to Tomcat.
One big gotcha when I first started using TomEE was that you had turned off
the JSP-recompilation feature which is default in Tomcat. So my JSP test
files weren't being recompiled and I needed to restart the JVM each time. I
had to find the setting myself because it wasn't so clear.
So maybe a list of important changes like that would be helpful.
Even better - major difference docs for each major container. eg: if I am
used to GlassFish or JBoss, what do I need to change for TomEE.
This would be the ideal place to document the JSF/JPA stuff we discussed
earlier (if it's still relevant). If the problem is a large or fundamental
one like the JSF one was, maybe just documenting it for people who are used
to other containers would save a lot of headaches for first-time-users.
Maybe the wiki would be the best format for this sort of stuff?
https://cwiki.apache.org/TOMEE/index.html
Best Regards,
Neale
----- Original Message -----
From: "Neale Rudd" <ne...@metawerx.net>
To: <de...@openejb.apache.org>
Sent: Wednesday, October 10, 2012 6:37 PM
Subject: Re: 1.5 Clarification
> Hi David,
>
>>> Do you mean like this?
>>> - http://tomee.apache.org/tomee-1.5.0-release-notes.html
>>> Or do you want all the release notes from the previous releases? Or did
>>> you mean something else?
>
> Yes that's pretty good, guess I'd like a little more detail in general.
> eg: http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
> The sentences describe why the change was made a little more whereas the
> tomee ones seem to be a copy of the jira title, so it takes a lot longer
> to see what and why changed.
> Also the tomcat one shows change by version number and the final committer
> (just for fun)
>
>>> Any ideas on how we can improve these to better match what you imagine?
>>> - http://tomee.apache.org/examples-trunk/index.html
> These are great examples, but none are bundled with TomEE. I understand
> they can't be put into a production folder (like Tomcat does) but maybe
> then can be easily moved into webapps to try things out rather than
> downloading them. Just an opinion though. I understand you want to keep
> download size low.
>
>>>>> - upgrade notes (per revision + per major revision) - very important
>>>>> if used in a production system, I review these personally for every
>>>>> Tomcat subrelease and make changes to our templates as necessary
>>> We definitely don't have anything there. Wondering how we could
>>> realistically capture that information. Getting something in place and
>>> getting people to use it are always difficult initiatives.
> This would include a simple migration guide from 1.0.x to 1.5.x. ie: if
> your app runs in 1.0, what is going to break in 1.5? what needs to be
> changed? what do we need to be aware of? ie: the /openejb app being
> change to /tomee pre the 1.0 release would be a good example of a major
> change. Any information available here can be critical for assisting
> smooth transitions to newer versions, and that means less time supporting
> people on older revisions. Much easier to say "can you try it on 1.5?
> the migration docs are here: http...".
>
>>> And more docs :)
> Yes - I'd definitely start with configuration reference stuff. ie: a
> description of all non-Tomcat config files and their components
>
>>>>> - alpha, beta, rc -> release strategy (this would have avoided the
>>>>> 1.5.0 win issue)
>>> We did have about 3 sets of potential release binaries and another 2-3
>>> sets of preview binaries (not quite ready for voting).
> I think Tomcat generally follows this pattern, not sure if it's the Apache
> standard way, but it seems to generate pretty stable releases:
> - an alpha-release (people start trying out the new version, normal users
> never download a snapshot)
> - a beta-release (more heavy testing, because it's about to go live)
> - a release-candidate (more testing, people have a very last chance to
> deploy and test at their workplace, or risk missing all the new features
> for another N months)
> - release vote (2-3 days or whatever is decided/mandated)
> - release
>
> Then you immediately branch whatever branches you want, such as a 1.5.1
> for fixes-only, a 1.6.0 for the next main version. Whether or not Tomcat
> upgrades go into the 1.5.1 or the 1.6.0 is up to you.
>
> Then within 2 months you release 1.6.0. The 1.5.1 would be released in
> the case of important new fixes or deployment problems (eg: the windows
> 1.5.0 issue), and never include new features.
>
> Something like that?
>
> Best Regards,
> Neale
>
>
>
> ----- Original Message -----
> From: "David Blevins" <da...@gmail.com>
> To: <de...@openejb.apache.org>
> Sent: Tuesday, October 09, 2012 6:42 AM
> Subject: Re: 1.5 Clarification
>
>
>
> On Oct 8, 2012, at 12:15 PM, Neale Rudd wrote:
>
>> Suggest following Tomcat-style change-log. One file which has all 1.x.x
>> release notes with a one-liner describing the change/feature and a link
>> to Jira if people want to investigate.
>
> Do you mean like this?
> - http://tomee.apache.org/tomee-1.5.0-release-notes.html
>
> Or do you want all the release notes from the previous releases? Or did
> you mean something else?
>
>> - simple examples (helps get people started, helps to demonstrate why
>> TomEE is useful to their company)
>
> Any ideas on how we can improve these to better match what you imagine?
> - http://tomee.apache.org/examples-trunk/index.html
>
>> - easy to navigate docs (avoids ??% of the questions on the user list,
>> freeing up dev time, which is *so* important for bugfixes and new
>> features)
>
> And more docs :)
>
>> - integration with leading IDE's (TomEE could at least have excellent
>> docs on how to use Tomcat IDE settings, linked directly from the main web
>> page for easy transition)
>
> We've got a video and doc for Eclipse. The video isn't linked from the
> doc page and the doc ins't linked from the main page. Help welcome
> there -- from anyone reading. Here are the bits if someone wants to
> improve things:
>
> - http://tomee.apache.org/tomee-and-eclipse.html
> - http://www.youtube.com/watch?v=Lr8pxEACVRI
>
>> - easy to navigate release notes (easy to see what's changed, in 2
>> minutes, without browsing dev@ or long jiras)
>
> Any ideas on how to make this easier to navigate?
>
> - http://tomee.apache.org/tomee-1.5.0-release-notes.html
>
>> - upgrade notes (per revision + per major revision) - very important if
>> used in a production system, I review these personally for every Tomcat
>> subrelease and make changes to our templates as necessary
> We definitely don't have anything there. Wondering how we could
> realistically capture that information. Getting something in place and
> getting people to use it are always difficult initiatives.
>
>> - frequent releases (and TomEE should keep-up, like MariaDB does with
>> MySQL - this is critical IMHO)
>
> Completely agreed.
>
>> - alpha, beta, rc -> release strategy (this would have avoided the 1.5.0
>> win issue)
>
> Can you elaborate on the flow you have in mind? We do have restrictions
> on the workflow Apache allows, so we may or may not be able to do that,
> but it'll be good to understand.
>
> We did have about 3 sets of potential release binaries and another 2-3
> sets of preview binaries (not quite ready for voting).
>
>
> -David
>
>> ----- Original Message ----- From: "Neale Rudd" <ne...@metawerx.net>
>> To: <de...@openejb.apache.org>
>> Sent: Tuesday, October 09, 2012 6:00 AM
>> Subject: Re: 1.5 Clarification
>>
>>
>>> You're right - proxy or browser cache - I clicked Reload in Chrome and
>>> got the 1.5.0 release on tomee.apache.org finally.
>>>
>>> Some sort of too-long cache time problem? I've checked this every day
>>> and only got 1.5.0 just now after I clicked Reload. Might be a problem
>>> for future releases.
>>>
>>> Best Regards,
>>> Neale
>>>
>>> ----- Original Message ----- From: "David Blevins"
>>> <da...@gmail.com>
>>> To: <de...@openejb.apache.org>
>>> Sent: Tuesday, October 09, 2012 5:55 AM
>>> Subject: Re: 1.5 Clarification
>>>
>>>
>>>
>>> On Oct 8, 2012, at 11:33 AM, Neale Rudd wrote:
>>>
>>>> - http://tomee.apache.org/downloads.html shows 1.0.0, but
>>>> http://openejb.apache.org/downloads.html shows 1.5.0 as latest release,
>>>> aren't these the same site?
>>>
>>> That's probably a browser caching issue. The tomee.apache.org is just
>>> an alias.
>>>
>>>
>>> -David
>>
>
Re: 1.5 Clarification
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
Hi all,
Sorry for the delay, just took some time to update the page. Lemme know if
that's clearer.
You are also free to edit it (top right button) so that we'll receive your
patch to integrate.
Jean-Louis
2012/10/10 Neale Rudd <ne...@metawerx.net>
> This is good actually:
> http://tomee.apache.org/tomee-**directory-structure.html<http://tomee.apache.org/tomee-directory-structure.html>
>
> (but very out of date)
>
> Best Regards,
> Neale
>
>
>
> ----- Original Message ----- From: "Neale Rudd" <ne...@metawerx.net>
> To: <de...@openejb.apache.org>
> Sent: Wednesday, October 10, 2012 6:37 PM
> Subject: Re: 1.5 Clarification
>
>
> Hi David,
>>
>> Do you mean like this?
>>>> - http://tomee.apache.org/tomee-**1.5.0-release-notes.html<http://tomee.apache.org/tomee-1.5.0-release-notes.html>
>>>> Or do you want all the release notes from the previous releases? Or
>>>> did you mean something else?
>>>>
>>>
>> Yes that's pretty good, guess I'd like a little more detail in general.
>> eg: http://tomcat.apache.org/**tomcat-7.0-doc/changelog.html<http://tomcat.apache.org/tomcat-7.0-doc/changelog.html>
>> The sentences describe why the change was made a little more whereas the
>> tomee ones seem to be a copy of the jira title, so it takes a lot longer to
>> see what and why changed.
>> Also the tomcat one shows change by version number and the final
>> committer (just for fun)
>>
>> Any ideas on how we can improve these to better match what you imagine?
>>>> - http://tomee.apache.org/**examples-trunk/index.html<http://tomee.apache.org/examples-trunk/index.html>
>>>>
>>> These are great examples, but none are bundled with TomEE. I understand
>> they can't be put into a production folder (like Tomcat does) but maybe
>> then can be easily moved into webapps to try things out rather than
>> downloading them. Just an opinion though. I understand you want to keep
>> download size low.
>>
>> - upgrade notes (per revision + per major revision) - very important if
>>>>>> used in a production system, I review these personally for every Tomcat
>>>>>> subrelease and make changes to our templates as necessary
>>>>>>
>>>>> We definitely don't have anything there. Wondering how we could
>>>> realistically capture that information. Getting something in place and
>>>> getting people to use it are always difficult initiatives.
>>>>
>>> This would include a simple migration guide from 1.0.x to 1.5.x. ie: if
>> your app runs in 1.0, what is going to break in 1.5? what needs to be
>> changed? what do we need to be aware of? ie: the /openejb app being
>> change to /tomee pre the 1.0 release would be a good example of a major
>> change. Any information available here can be critical for assisting smooth
>> transitions to newer versions, and that means less time supporting people
>> on older revisions. Much easier to say "can you try it on 1.5? the
>> migration docs are here: http...".
>>
>> And more docs :)
>>>>
>>> Yes - I'd definitely start with configuration reference stuff. ie: a
>> description of all non-Tomcat config files and their components
>>
>> - alpha, beta, rc -> release strategy (this would have avoided the 1.5.0
>>>>>> win issue)
>>>>>>
>>>>> We did have about 3 sets of potential release binaries and another 2-3
>>>> sets of preview binaries (not quite ready for voting).
>>>>
>>> I think Tomcat generally follows this pattern, not sure if it's the
>> Apache standard way, but it seems to generate pretty stable releases:
>> - an alpha-release (people start trying out the new version, normal users
>> never download a snapshot)
>> - a beta-release (more heavy testing, because it's about to go live)
>> - a release-candidate (more testing, people have a very last chance to
>> deploy and test at their workplace, or risk missing all the new features
>> for another N months)
>> - release vote (2-3 days or whatever is decided/mandated)
>> - release
>>
>> Then you immediately branch whatever branches you want, such as a 1.5.1
>> for fixes-only, a 1.6.0 for the next main version. Whether or not Tomcat
>> upgrades go into the 1.5.1 or the 1.6.0 is up to you.
>>
>> Then within 2 months you release 1.6.0. The 1.5.1 would be released in
>> the case of important new fixes or deployment problems (eg: the windows
>> 1.5.0 issue), and never include new features.
>>
>> Something like that?
>>
>> Best Regards,
>> Neale
>>
>>
>>
>> ----- Original Message ----- From: "David Blevins" <
>> david.blevins@gmail.com>
>> To: <de...@openejb.apache.org>
>> Sent: Tuesday, October 09, 2012 6:42 AM
>> Subject: Re: 1.5 Clarification
>>
>>
>>
>> On Oct 8, 2012, at 12:15 PM, Neale Rudd wrote:
>>
>> Suggest following Tomcat-style change-log. One file which has all 1.x.x
>>> release notes with a one-liner describing the change/feature and a link to
>>> Jira if people want to investigate.
>>>
>>
>> Do you mean like this?
>> - http://tomee.apache.org/tomee-**1.5.0-release-notes.html<http://tomee.apache.org/tomee-1.5.0-release-notes.html>
>>
>> Or do you want all the release notes from the previous releases? Or did
>> you mean something else?
>>
>> - simple examples (helps get people started, helps to demonstrate why
>>> TomEE is useful to their company)
>>>
>>
>> Any ideas on how we can improve these to better match what you imagine?
>> - http://tomee.apache.org/**examples-trunk/index.html<http://tomee.apache.org/examples-trunk/index.html>
>>
>> - easy to navigate docs (avoids ??% of the questions on the user list,
>>> freeing up dev time, which is *so* important for bugfixes and new features)
>>>
>>
>> And more docs :)
>>
>> - integration with leading IDE's (TomEE could at least have excellent
>>> docs on how to use Tomcat IDE settings, linked directly from the main web
>>> page for easy transition)
>>>
>>
>> We've got a video and doc for Eclipse. The video isn't linked from the
>> doc page and the doc ins't linked from the main page. Help welcome there
>> -- from anyone reading. Here are the bits if someone wants to improve
>> things:
>>
>> - http://tomee.apache.org/tomee-**and-eclipse.html<http://tomee.apache.org/tomee-and-eclipse.html>
>> - http://www.youtube.com/watch?**v=Lr8pxEACVRI<http://www.youtube.com/watch?v=Lr8pxEACVRI>
>>
>> - easy to navigate release notes (easy to see what's changed, in 2
>>> minutes, without browsing dev@ or long jiras)
>>>
>>
>> Any ideas on how to make this easier to navigate?
>>
>> - http://tomee.apache.org/tomee-**1.5.0-release-notes.html<http://tomee.apache.org/tomee-1.5.0-release-notes.html>
>>
>> - upgrade notes (per revision + per major revision) - very important if
>>> used in a production system, I review these personally for every Tomcat
>>> subrelease and make changes to our templates as necessary
>>>
>> We definitely don't have anything there. Wondering how we could
>> realistically capture that information. Getting something in place and
>> getting people to use it are always difficult initiatives.
>>
>> - frequent releases (and TomEE should keep-up, like MariaDB does with
>>> MySQL - this is critical IMHO)
>>>
>>
>> Completely agreed.
>>
>> - alpha, beta, rc -> release strategy (this would have avoided the 1.5.0
>>> win issue)
>>>
>>
>> Can you elaborate on the flow you have in mind? We do have restrictions
>> on the workflow Apache allows, so we may or may not be able to do that, but
>> it'll be good to understand.
>>
>> We did have about 3 sets of potential release binaries and another 2-3
>> sets of preview binaries (not quite ready for voting).
>>
>>
>> -David
>>
>> ----- Original Message ----- From: "Neale Rudd" <ne...@metawerx.net>
>>> To: <de...@openejb.apache.org>
>>> Sent: Tuesday, October 09, 2012 6:00 AM
>>> Subject: Re: 1.5 Clarification
>>>
>>>
>>> You're right - proxy or browser cache - I clicked Reload in Chrome and
>>>> got the 1.5.0 release on tomee.apache.org finally.
>>>>
>>>> Some sort of too-long cache time problem? I've checked this every day
>>>> and only got 1.5.0 just now after I clicked Reload. Might be a problem for
>>>> future releases.
>>>>
>>>> Best Regards,
>>>> Neale
>>>>
>>>> ----- Original Message ----- From: "David Blevins" <
>>>> david.blevins@gmail.com>
>>>> To: <de...@openejb.apache.org>
>>>> Sent: Tuesday, October 09, 2012 5:55 AM
>>>> Subject: Re: 1.5 Clarification
>>>>
>>>>
>>>>
>>>> On Oct 8, 2012, at 11:33 AM, Neale Rudd wrote:
>>>>
>>>> - http://tomee.apache.org/**downloads.html<http://tomee.apache.org/downloads.html>shows 1.0.0, but
>>>>> http://openejb.apache.org/**downloads.html<http://openejb.apache.org/downloads.html>shows 1.5.0 as latest release, aren't these the same site?
>>>>>
>>>>
>>>> That's probably a browser caching issue. The tomee.apache.org is just
>>>> an alias.
>>>>
>>>>
>>>> -David
>>>>
>>>
>>>
>>
>
Re: 1.5 Clarification
Posted by Neale Rudd <ne...@metawerx.net>.
This is good actually:
http://tomee.apache.org/tomee-directory-structure.html
(but very out of date)
Best Regards,
Neale
----- Original Message -----
From: "Neale Rudd" <ne...@metawerx.net>
To: <de...@openejb.apache.org>
Sent: Wednesday, October 10, 2012 6:37 PM
Subject: Re: 1.5 Clarification
> Hi David,
>
>>> Do you mean like this?
>>> - http://tomee.apache.org/tomee-1.5.0-release-notes.html
>>> Or do you want all the release notes from the previous releases? Or did
>>> you mean something else?
>
> Yes that's pretty good, guess I'd like a little more detail in general.
> eg: http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
> The sentences describe why the change was made a little more whereas the
> tomee ones seem to be a copy of the jira title, so it takes a lot longer
> to see what and why changed.
> Also the tomcat one shows change by version number and the final committer
> (just for fun)
>
>>> Any ideas on how we can improve these to better match what you imagine?
>>> - http://tomee.apache.org/examples-trunk/index.html
> These are great examples, but none are bundled with TomEE. I understand
> they can't be put into a production folder (like Tomcat does) but maybe
> then can be easily moved into webapps to try things out rather than
> downloading them. Just an opinion though. I understand you want to keep
> download size low.
>
>>>>> - upgrade notes (per revision + per major revision) - very important
>>>>> if used in a production system, I review these personally for every
>>>>> Tomcat subrelease and make changes to our templates as necessary
>>> We definitely don't have anything there. Wondering how we could
>>> realistically capture that information. Getting something in place and
>>> getting people to use it are always difficult initiatives.
> This would include a simple migration guide from 1.0.x to 1.5.x. ie: if
> your app runs in 1.0, what is going to break in 1.5? what needs to be
> changed? what do we need to be aware of? ie: the /openejb app being
> change to /tomee pre the 1.0 release would be a good example of a major
> change. Any information available here can be critical for assisting
> smooth transitions to newer versions, and that means less time supporting
> people on older revisions. Much easier to say "can you try it on 1.5?
> the migration docs are here: http...".
>
>>> And more docs :)
> Yes - I'd definitely start with configuration reference stuff. ie: a
> description of all non-Tomcat config files and their components
>
>>>>> - alpha, beta, rc -> release strategy (this would have avoided the
>>>>> 1.5.0 win issue)
>>> We did have about 3 sets of potential release binaries and another 2-3
>>> sets of preview binaries (not quite ready for voting).
> I think Tomcat generally follows this pattern, not sure if it's the Apache
> standard way, but it seems to generate pretty stable releases:
> - an alpha-release (people start trying out the new version, normal users
> never download a snapshot)
> - a beta-release (more heavy testing, because it's about to go live)
> - a release-candidate (more testing, people have a very last chance to
> deploy and test at their workplace, or risk missing all the new features
> for another N months)
> - release vote (2-3 days or whatever is decided/mandated)
> - release
>
> Then you immediately branch whatever branches you want, such as a 1.5.1
> for fixes-only, a 1.6.0 for the next main version. Whether or not Tomcat
> upgrades go into the 1.5.1 or the 1.6.0 is up to you.
>
> Then within 2 months you release 1.6.0. The 1.5.1 would be released in
> the case of important new fixes or deployment problems (eg: the windows
> 1.5.0 issue), and never include new features.
>
> Something like that?
>
> Best Regards,
> Neale
>
>
>
> ----- Original Message -----
> From: "David Blevins" <da...@gmail.com>
> To: <de...@openejb.apache.org>
> Sent: Tuesday, October 09, 2012 6:42 AM
> Subject: Re: 1.5 Clarification
>
>
>
> On Oct 8, 2012, at 12:15 PM, Neale Rudd wrote:
>
>> Suggest following Tomcat-style change-log. One file which has all 1.x.x
>> release notes with a one-liner describing the change/feature and a link
>> to Jira if people want to investigate.
>
> Do you mean like this?
> - http://tomee.apache.org/tomee-1.5.0-release-notes.html
>
> Or do you want all the release notes from the previous releases? Or did
> you mean something else?
>
>> - simple examples (helps get people started, helps to demonstrate why
>> TomEE is useful to their company)
>
> Any ideas on how we can improve these to better match what you imagine?
> - http://tomee.apache.org/examples-trunk/index.html
>
>> - easy to navigate docs (avoids ??% of the questions on the user list,
>> freeing up dev time, which is *so* important for bugfixes and new
>> features)
>
> And more docs :)
>
>> - integration with leading IDE's (TomEE could at least have excellent
>> docs on how to use Tomcat IDE settings, linked directly from the main web
>> page for easy transition)
>
> We've got a video and doc for Eclipse. The video isn't linked from the
> doc page and the doc ins't linked from the main page. Help welcome
> there -- from anyone reading. Here are the bits if someone wants to
> improve things:
>
> - http://tomee.apache.org/tomee-and-eclipse.html
> - http://www.youtube.com/watch?v=Lr8pxEACVRI
>
>> - easy to navigate release notes (easy to see what's changed, in 2
>> minutes, without browsing dev@ or long jiras)
>
> Any ideas on how to make this easier to navigate?
>
> - http://tomee.apache.org/tomee-1.5.0-release-notes.html
>
>> - upgrade notes (per revision + per major revision) - very important if
>> used in a production system, I review these personally for every Tomcat
>> subrelease and make changes to our templates as necessary
> We definitely don't have anything there. Wondering how we could
> realistically capture that information. Getting something in place and
> getting people to use it are always difficult initiatives.
>
>> - frequent releases (and TomEE should keep-up, like MariaDB does with
>> MySQL - this is critical IMHO)
>
> Completely agreed.
>
>> - alpha, beta, rc -> release strategy (this would have avoided the 1.5.0
>> win issue)
>
> Can you elaborate on the flow you have in mind? We do have restrictions
> on the workflow Apache allows, so we may or may not be able to do that,
> but it'll be good to understand.
>
> We did have about 3 sets of potential release binaries and another 2-3
> sets of preview binaries (not quite ready for voting).
>
>
> -David
>
>> ----- Original Message ----- From: "Neale Rudd" <ne...@metawerx.net>
>> To: <de...@openejb.apache.org>
>> Sent: Tuesday, October 09, 2012 6:00 AM
>> Subject: Re: 1.5 Clarification
>>
>>
>>> You're right - proxy or browser cache - I clicked Reload in Chrome and
>>> got the 1.5.0 release on tomee.apache.org finally.
>>>
>>> Some sort of too-long cache time problem? I've checked this every day
>>> and only got 1.5.0 just now after I clicked Reload. Might be a problem
>>> for future releases.
>>>
>>> Best Regards,
>>> Neale
>>>
>>> ----- Original Message ----- From: "David Blevins"
>>> <da...@gmail.com>
>>> To: <de...@openejb.apache.org>
>>> Sent: Tuesday, October 09, 2012 5:55 AM
>>> Subject: Re: 1.5 Clarification
>>>
>>>
>>>
>>> On Oct 8, 2012, at 11:33 AM, Neale Rudd wrote:
>>>
>>>> - http://tomee.apache.org/downloads.html shows 1.0.0, but
>>>> http://openejb.apache.org/downloads.html shows 1.5.0 as latest release,
>>>> aren't these the same site?
>>>
>>> That's probably a browser caching issue. The tomee.apache.org is just
>>> an alias.
>>>
>>>
>>> -David
>>
>
Re: 1.5 Clarification
Posted by Neale Rudd <ne...@metawerx.net>.
Hi David,
>> Do you mean like this?
>> - http://tomee.apache.org/tomee-1.5.0-release-notes.html
>> Or do you want all the release notes from the previous releases? Or did
>> you mean something else?
Yes that's pretty good, guess I'd like a little more detail in general.
eg: http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
The sentences describe why the change was made a little more whereas the
tomee ones seem to be a copy of the jira title, so it takes a lot longer to
see what and why changed.
Also the tomcat one shows change by version number and the final committer
(just for fun)
>> Any ideas on how we can improve these to better match what you imagine?
>> - http://tomee.apache.org/examples-trunk/index.html
These are great examples, but none are bundled with TomEE. I understand
they can't be put into a production folder (like Tomcat does) but maybe then
can be easily moved into webapps to try things out rather than downloading
them. Just an opinion though. I understand you want to keep download size
low.
>>>> - upgrade notes (per revision + per major revision) - very important if
>>>> used in a production system, I review these personally for every Tomcat
>>>> subrelease and make changes to our templates as necessary
>> We definitely don't have anything there. Wondering how we could
>> realistically capture that information. Getting something in place and
>> getting people to use it are always difficult initiatives.
This would include a simple migration guide from 1.0.x to 1.5.x. ie: if
your app runs in 1.0, what is going to break in 1.5? what needs to be
changed? what do we need to be aware of? ie: the /openejb app being change
to /tomee pre the 1.0 release would be a good example of a major change.
Any information available here can be critical for assisting smooth
transitions to newer versions, and that means less time supporting people on
older revisions. Much easier to say "can you try it on 1.5? the migration
docs are here: http...".
>> And more docs :)
Yes - I'd definitely start with configuration reference stuff. ie: a
description of all non-Tomcat config files and their components
>>>> - alpha, beta, rc -> release strategy (this would have avoided the
>>>> 1.5.0 win issue)
>> We did have about 3 sets of potential release binaries and another 2-3
>> sets of preview binaries (not quite ready for voting).
I think Tomcat generally follows this pattern, not sure if it's the Apache
standard way, but it seems to generate pretty stable releases:
- an alpha-release (people start trying out the new version, normal users
never download a snapshot)
- a beta-release (more heavy testing, because it's about to go live)
- a release-candidate (more testing, people have a very last chance to
deploy and test at their workplace, or risk missing all the new features for
another N months)
- release vote (2-3 days or whatever is decided/mandated)
- release
Then you immediately branch whatever branches you want, such as a 1.5.1 for
fixes-only, a 1.6.0 for the next main version. Whether or not Tomcat
upgrades go into the 1.5.1 or the 1.6.0 is up to you.
Then within 2 months you release 1.6.0. The 1.5.1 would be released in the
case of important new fixes or deployment problems (eg: the windows 1.5.0
issue), and never include new features.
Something like that?
Best Regards,
Neale
----- Original Message -----
From: "David Blevins" <da...@gmail.com>
To: <de...@openejb.apache.org>
Sent: Tuesday, October 09, 2012 6:42 AM
Subject: Re: 1.5 Clarification
On Oct 8, 2012, at 12:15 PM, Neale Rudd wrote:
> Suggest following Tomcat-style change-log. One file which has all 1.x.x
> release notes with a one-liner describing the change/feature and a link to
> Jira if people want to investigate.
Do you mean like this?
- http://tomee.apache.org/tomee-1.5.0-release-notes.html
Or do you want all the release notes from the previous releases? Or did you
mean something else?
> - simple examples (helps get people started, helps to demonstrate why
> TomEE is useful to their company)
Any ideas on how we can improve these to better match what you imagine?
- http://tomee.apache.org/examples-trunk/index.html
> - easy to navigate docs (avoids ??% of the questions on the user list,
> freeing up dev time, which is *so* important for bugfixes and new
> features)
And more docs :)
> - integration with leading IDE's (TomEE could at least have excellent docs
> on how to use Tomcat IDE settings, linked directly from the main web page
> for easy transition)
We've got a video and doc for Eclipse. The video isn't linked from the doc
page and the doc ins't linked from the main page. Help welcome there --
from anyone reading. Here are the bits if someone wants to improve things:
- http://tomee.apache.org/tomee-and-eclipse.html
- http://www.youtube.com/watch?v=Lr8pxEACVRI
> - easy to navigate release notes (easy to see what's changed, in 2
> minutes, without browsing dev@ or long jiras)
Any ideas on how to make this easier to navigate?
- http://tomee.apache.org/tomee-1.5.0-release-notes.html
> - upgrade notes (per revision + per major revision) - very important if
> used in a production system, I review these personally for every Tomcat
> subrelease and make changes to our templates as necessary
We definitely don't have anything there. Wondering how we could
realistically capture that information. Getting something in place and
getting people to use it are always difficult initiatives.
> - frequent releases (and TomEE should keep-up, like MariaDB does with
> MySQL - this is critical IMHO)
Completely agreed.
> - alpha, beta, rc -> release strategy (this would have avoided the 1.5.0
> win issue)
Can you elaborate on the flow you have in mind? We do have restrictions on
the workflow Apache allows, so we may or may not be able to do that, but
it'll be good to understand.
We did have about 3 sets of potential release binaries and another 2-3 sets
of preview binaries (not quite ready for voting).
-David
> ----- Original Message ----- From: "Neale Rudd" <ne...@metawerx.net>
> To: <de...@openejb.apache.org>
> Sent: Tuesday, October 09, 2012 6:00 AM
> Subject: Re: 1.5 Clarification
>
>
>> You're right - proxy or browser cache - I clicked Reload in Chrome and
>> got the 1.5.0 release on tomee.apache.org finally.
>>
>> Some sort of too-long cache time problem? I've checked this every day
>> and only got 1.5.0 just now after I clicked Reload. Might be a problem
>> for future releases.
>>
>> Best Regards,
>> Neale
>>
>> ----- Original Message ----- From: "David Blevins"
>> <da...@gmail.com>
>> To: <de...@openejb.apache.org>
>> Sent: Tuesday, October 09, 2012 5:55 AM
>> Subject: Re: 1.5 Clarification
>>
>>
>>
>> On Oct 8, 2012, at 11:33 AM, Neale Rudd wrote:
>>
>>> - http://tomee.apache.org/downloads.html shows 1.0.0, but
>>> http://openejb.apache.org/downloads.html shows 1.5.0 as latest release,
>>> aren't these the same site?
>>
>> That's probably a browser caching issue. The tomee.apache.org is just an
>> alias.
>>
>>
>> -David
>
Re: 1.5 Clarification
Posted by David Blevins <da...@gmail.com>.
On Oct 8, 2012, at 12:15 PM, Neale Rudd wrote:
> Suggest following Tomcat-style change-log. One file which has all 1.x.x release notes with a one-liner describing the change/feature and a link to Jira if people want to investigate.
Do you mean like this?
- http://tomee.apache.org/tomee-1.5.0-release-notes.html
Or do you want all the release notes from the previous releases? Or did you mean something else?
> - simple examples (helps get people started, helps to demonstrate why TomEE is useful to their company)
Any ideas on how we can improve these to better match what you imagine?
- http://tomee.apache.org/examples-trunk/index.html
> - easy to navigate docs (avoids ??% of the questions on the user list, freeing up dev time, which is *so* important for bugfixes and new features)
And more docs :)
> - integration with leading IDE's (TomEE could at least have excellent docs on how to use Tomcat IDE settings, linked directly from the main web page for easy transition)
We've got a video and doc for Eclipse. The video isn't linked from the doc page and the doc ins't linked from the main page. Help welcome there -- from anyone reading. Here are the bits if someone wants to improve things:
- http://tomee.apache.org/tomee-and-eclipse.html
- http://www.youtube.com/watch?v=Lr8pxEACVRI
> - easy to navigate release notes (easy to see what's changed, in 2 minutes, without browsing dev@ or long jiras)
Any ideas on how to make this easier to navigate?
- http://tomee.apache.org/tomee-1.5.0-release-notes.html
> - upgrade notes (per revision + per major revision) - very important if used in a production system, I review these personally for every Tomcat subrelease and make changes to our templates as necessary
We definitely don't have anything there. Wondering how we could realistically capture that information. Getting something in place and getting people to use it are always difficult initiatives.
> - frequent releases (and TomEE should keep-up, like MariaDB does with MySQL - this is critical IMHO)
Completely agreed.
> - alpha, beta, rc -> release strategy (this would have avoided the 1.5.0 win issue)
Can you elaborate on the flow you have in mind? We do have restrictions on the workflow Apache allows, so we may or may not be able to do that, but it'll be good to understand.
We did have about 3 sets of potential release binaries and another 2-3 sets of preview binaries (not quite ready for voting).
-David
> ----- Original Message ----- From: "Neale Rudd" <ne...@metawerx.net>
> To: <de...@openejb.apache.org>
> Sent: Tuesday, October 09, 2012 6:00 AM
> Subject: Re: 1.5 Clarification
>
>
>> You're right - proxy or browser cache - I clicked Reload in Chrome and got the 1.5.0 release on tomee.apache.org finally.
>>
>> Some sort of too-long cache time problem? I've checked this every day and only got 1.5.0 just now after I clicked Reload. Might be a problem for future releases.
>>
>> Best Regards,
>> Neale
>>
>> ----- Original Message ----- From: "David Blevins" <da...@gmail.com>
>> To: <de...@openejb.apache.org>
>> Sent: Tuesday, October 09, 2012 5:55 AM
>> Subject: Re: 1.5 Clarification
>>
>>
>>
>> On Oct 8, 2012, at 11:33 AM, Neale Rudd wrote:
>>
>>> - http://tomee.apache.org/downloads.html shows 1.0.0, but http://openejb.apache.org/downloads.html shows 1.5.0 as latest release, aren't these the same site?
>>
>> That's probably a browser caching issue. The tomee.apache.org is just an alias.
>>
>>
>> -David
>
Re: 1.5 Clarification
Posted by Neale Rudd <ne...@metawerx.net>.
A few more comments:
A simpler change log would be great. The download page has links to Jira.
Some Jira items have no information (they just have a title and say Fixed)
or others have a history which is hard to navigate.
Suggest following Tomcat-style change-log. One file which has all 1.x.x
release notes with a one-liner describing the change/feature and a link to
Jira if people want to investigate.
There's a number of reasons Tomcat is the world's most popular container.
IMO here's a few professional reasons that I really love Tomcat. If TomEE
addressed these, it would make TomEE more awesome and much easier for
users/companies to adopt:
- simple examples (helps get people started, helps to demonstrate why TomEE
is useful to their company)
- easy to navigate docs (avoids ??% of the questions on the user list,
freeing up dev time, which is *so* important for bugfixes and new features)
- integration with leading IDE's (TomEE could at least have excellent docs
on how to use Tomcat IDE settings, linked directly from the main web page
for easy transition)
- easy to navigate release notes (easy to see what's changed, in 2 minutes,
without browsing dev@ or long jiras)
- upgrade notes (per revision + per major revision) - very important if used
in a production system, I review these personally for every Tomcat
subrelease and make changes to our templates as necessary
- frequent releases (and TomEE should keep-up, like MariaDB does with
MySQL - this is critical IMHO)
- alpha, beta, rc -> release strategy (this would have avoided the 1.5.0 win
issue)
Hope that helps!
Best Regards,
Neale
----- Original Message -----
From: "Neale Rudd" <ne...@metawerx.net>
To: <de...@openejb.apache.org>
Sent: Tuesday, October 09, 2012 6:00 AM
Subject: Re: 1.5 Clarification
> You're right - proxy or browser cache - I clicked Reload in Chrome and got
> the 1.5.0 release on tomee.apache.org finally.
>
> Some sort of too-long cache time problem? I've checked this every day
> and only got 1.5.0 just now after I clicked Reload. Might be a problem
> for future releases.
>
> Best Regards,
> Neale
>
> ----- Original Message -----
> From: "David Blevins" <da...@gmail.com>
> To: <de...@openejb.apache.org>
> Sent: Tuesday, October 09, 2012 5:55 AM
> Subject: Re: 1.5 Clarification
>
>
>
> On Oct 8, 2012, at 11:33 AM, Neale Rudd wrote:
>
>> - http://tomee.apache.org/downloads.html shows 1.0.0, but
>> http://openejb.apache.org/downloads.html shows 1.5.0 as latest release,
>> aren't these the same site?
>
> That's probably a browser caching issue. The tomee.apache.org is just an
> alias.
>
>
> -David
>
Re: 1.5 Clarification
Posted by Neale Rudd <ne...@metawerx.net>.
You're right - proxy or browser cache - I clicked Reload in Chrome and got
the 1.5.0 release on tomee.apache.org finally.
Some sort of too-long cache time problem? I've checked this every day and
only got 1.5.0 just now after I clicked Reload. Might be a problem for
future releases.
Best Regards,
Neale
----- Original Message -----
From: "David Blevins" <da...@gmail.com>
To: <de...@openejb.apache.org>
Sent: Tuesday, October 09, 2012 5:55 AM
Subject: Re: 1.5 Clarification
On Oct 8, 2012, at 11:33 AM, Neale Rudd wrote:
> - http://tomee.apache.org/downloads.html shows 1.0.0, but
> http://openejb.apache.org/downloads.html shows 1.5.0 as latest release,
> aren't these the same site?
That's probably a browser caching issue. The tomee.apache.org is just an
alias.
-David
Re: 1.5 Clarification
Posted by David Blevins <da...@gmail.com>.
On Oct 8, 2012, at 11:33 AM, Neale Rudd wrote:
> - http://tomee.apache.org/downloads.html shows 1.0.0, but http://openejb.apache.org/downloads.html shows 1.5.0 as latest release, aren't these the same site?
That's probably a browser caching issue. The tomee.apache.org is just an alias.
-David
Re: 1.5 Clarification
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
Yes, 1.5.0 as been officially released and is available on Apache Mirrors
as well as on Central Repo.
Regarding tomee.apache.org or openejb.apache.org, there were the same as
far as I know, but i's not if I understand :D
tomee.apache.org was supposed to be just a new domain name pointing to
openejb.apache.org
Maybe David can give u more insights.
JLouis
2012/10/8 Neale Rudd <ne...@metawerx.net>
> Also just wanted to check:
>
> Has 1.5.0 been officially released yet? We've been offering it for almost
> for a week now.
>
> As far as I know:
> - 1.5.0 is good on Linux
> - pending 1.5.1 release to fix windows deployer bug
> - http://tomee.apache.org/**downloads.html<http://tomee.apache.org/downloads.html>shows 1.0.0, but
> http://openejb.apache.org/**downloads.html<http://openejb.apache.org/downloads.html>shows 1.5.0 as latest release, aren't these the same site? Maybe they
> should be redirected or auto-synced to remove inconsistencies? Or maybe
> it's better to 301 one of them (1)? (better for google)
>
> Best Regards,
> Neale
>
> (1) 301 Moved Permanently http://www.ietf.org/rfc/**rfc2616.txt<http://www.ietf.org/rfc/rfc2616.txt>
> #footnotesarecool
>
>
1.5 Clarification
Posted by Neale Rudd <ne...@metawerx.net>.
Also just wanted to check:
Has 1.5.0 been officially released yet? We've been offering it for almost
for a week now.
As far as I know:
- 1.5.0 is good on Linux
- pending 1.5.1 release to fix windows deployer bug
- http://tomee.apache.org/downloads.html shows 1.0.0, but
http://openejb.apache.org/downloads.html shows 1.5.0 as latest release,
aren't these the same site? Maybe they should be redirected or auto-synced
to remove inconsistencies? Or maybe it's better to 301 one of them (1)?
(better for google)
Best Regards,
Neale
(1) 301 Moved Permanently http://www.ietf.org/rfc/rfc2616.txt
#footnotesarecool
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by Romain Manni-Bucau <rm...@gmail.com>.
+1 use the paw then add on the site "challenge our logo"
Le 8 oct. 2012 20:52, "Neale Rudd" <ne...@metawerx.net> a écrit :
> Hi Guys,
>
> Ok I found the logos Romain originally posted.
>
> http://people.apache.org/~**rmannibucau/graphic/<http://people.apache.org/~rmannibucau/graphic/>
>
> Can someone post this out to the wider community and start a [VOTE] thread?
>
> As David said, we seem to have a consensus already, but to follow the
> Apache by-laws, let's send it out.
>
> I haven't seen any submissions but I only joined the list in March, so if
> someone knows more, please include those too.
>
> Best Regards,
> Neale
>
>
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by Neale Rudd <ne...@metawerx.net>.
Hi Guys,
Ok I found the logos Romain originally posted.
http://people.apache.org/~rmannibucau/graphic/
Can someone post this out to the wider community and start a [VOTE] thread?
As David said, we seem to have a consensus already, but to follow the Apache
by-laws, let's send it out.
I haven't seen any submissions but I only joined the list in March, so if
someone knows more, please include those too.
Best Regards,
Neale
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by David Blevins <da...@gmail.com>.
On Oct 8, 2012, at 11:27 AM, Neale Rudd wrote:
> I'll put them on a URL within the next hour if you can send it quickly, otherwise tomorrow. Someone else can count the votes over the next 72 hours.
>
> If there is a too-close vote, maybe it's better to run a competition, or if it's unanimous for the paw-print, maybe just go with it?
Don't think we need a vote. We can both use the paw-print and have a logo contest.
We never really pushed a logo contest off the list. We're getting about 10k visits a week on the website. We only have 126 people on the mailing list.
With an actual logo contest featured on the website I *guarantee* we will get entries.
-David
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by Neale Rudd <ne...@metawerx.net>.
Hi Guys,
Can someone send me the paw-print logo?
And all other submitted logos?
I'll put them on a URL within the next hour if you can send it quickly,
otherwise tomorrow. Someone else can count the votes over the next 72
hours.
If there is a too-close vote, maybe it's better to run a competition, or if
it's unanimous for the paw-print, maybe just go with it?
I personally love the paw-print and want to post it on the metawerx site to
promote TomEE (with your permission of course! ;-)
Best Regards,
Neale
----- Original Message -----
From: "David Blevins" <da...@gmail.com>
To: <de...@openejb.apache.org>
Sent: Tuesday, October 09, 2012 5:15 AM
Subject: Re: [RESULT] Paw-print logo to become official TomEE logo
On Oct 8, 2012, at 10:57 AM, Jean-Louis MONTEIRO wrote:
> Sorry David, but we have been talking about that for months.
> Some people already voted for the paw-print.
>
> Maybe they voted here on the idea to actually close the vote :D
> That's really important IMO to get something for TomEE.
>
> If you think that is important we can push a new VOTE on the list and let
> it open for 72 hours as usual.
> but to be honest I don't think at all we'll get more votes.
I think people's intentions are clear, so no need for a formal vote.
My comment was about the vote structure, not about the subject. Per Apache
by-laws votes need to have a '[VOTE]' header and run for a period of days
and close with a '[RESULT]'.
-David
> 2012/10/8 David Blevins <da...@gmail.com>
>
>> I think the fact that we're getting votes on a '[RESULTS]' thread is a
>> sign there was no actual vote :)
>>
>> That said, it's pretty clear people like the direction. It would still
>> be
>> great to have an actual logo contest and promote the project with it.
>>
>> I'll be happy to get that started this week.
>>
>>
>> -David
>>
>>
>> On Oct 8, 2012, at 8:19 AM, Jean-Louis MONTEIRO wrote:
>>
>>> Hi guys,
>>>
>>> Following what we decided 4 months ago (more than 40 days).
>>> So even if someone else disagree, the paw-print will be used as the
>>> official Apache TomEE logo.
>>>
>>> Jean-Louis
>>>
>>>
>>>
>>> 2012/6/4 Romain Manni-Bucau <rm...@gmail.com>
>>>
>>>> i globally agree even if i would have had it on the 12th.
>>>>
>>>> - Romain
>>>>
>>>>
>>>> 2012/6/4 David Blevins <da...@gmail.com>
>>>>
>>>>>
>>>>> On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote:
>>>>>
>>>>>> If we get a higher vote for the pawprint sum(+1/-1) vs
>>>>>> (waitFor40days)
>>>>> we'll just go with it - pending David's decision of course.
>>>>>
>>>>> All things are project decisions of course. I get one vote like
>> everyone
>>>>> else :)
>>>>>
>>>>> My vote would be for the 40 day logo contest. If we don't do it we'd
>> be
>>>>> passing up a great chance to make some noise, attract some attention
>> and
>>>>> get several people contributing logos to the project which means more
>>>>> people contributing to the project.
>>>>>
>>>>> Would be a shame to miss out on all that buzz and excitement.
>>>>>
>>>>>
>>>>> -David
>>>>>
>>>>>
>>>>
>>
>>
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by David Blevins <da...@gmail.com>.
On Oct 8, 2012, at 10:57 AM, Jean-Louis MONTEIRO wrote:
> Sorry David, but we have been talking about that for months.
> Some people already voted for the paw-print.
>
> Maybe they voted here on the idea to actually close the vote :D
> That's really important IMO to get something for TomEE.
>
> If you think that is important we can push a new VOTE on the list and let
> it open for 72 hours as usual.
> but to be honest I don't think at all we'll get more votes.
I think people's intentions are clear, so no need for a formal vote.
My comment was about the vote structure, not about the subject. Per Apache by-laws votes need to have a '[VOTE]' header and run for a period of days and close with a '[RESULT]'.
-David
> 2012/10/8 David Blevins <da...@gmail.com>
>
>> I think the fact that we're getting votes on a '[RESULTS]' thread is a
>> sign there was no actual vote :)
>>
>> That said, it's pretty clear people like the direction. It would still be
>> great to have an actual logo contest and promote the project with it.
>>
>> I'll be happy to get that started this week.
>>
>>
>> -David
>>
>>
>> On Oct 8, 2012, at 8:19 AM, Jean-Louis MONTEIRO wrote:
>>
>>> Hi guys,
>>>
>>> Following what we decided 4 months ago (more than 40 days).
>>> So even if someone else disagree, the paw-print will be used as the
>>> official Apache TomEE logo.
>>>
>>> Jean-Louis
>>>
>>>
>>>
>>> 2012/6/4 Romain Manni-Bucau <rm...@gmail.com>
>>>
>>>> i globally agree even if i would have had it on the 12th.
>>>>
>>>> - Romain
>>>>
>>>>
>>>> 2012/6/4 David Blevins <da...@gmail.com>
>>>>
>>>>>
>>>>> On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote:
>>>>>
>>>>>> If we get a higher vote for the pawprint sum(+1/-1) vs (waitFor40days)
>>>>> we'll just go with it - pending David's decision of course.
>>>>>
>>>>> All things are project decisions of course. I get one vote like
>> everyone
>>>>> else :)
>>>>>
>>>>> My vote would be for the 40 day logo contest. If we don't do it we'd
>> be
>>>>> passing up a great chance to make some noise, attract some attention
>> and
>>>>> get several people contributing logos to the project which means more
>>>>> people contributing to the project.
>>>>>
>>>>> Would be a shame to miss out on all that buzz and excitement.
>>>>>
>>>>>
>>>>> -David
>>>>>
>>>>>
>>>>
>>
>>
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by Romain Manni-Bucau <rm...@gmail.com>.
We waited 4 months...no need of vote IMO
David if you dont like the logo please propose sthg
Le 8 oct. 2012 19:57, "Jean-Louis MONTEIRO" <je...@gmail.com> a écrit :
> Sorry David, but we have been talking about that for months.
> Some people already voted for the paw-print.
>
> Maybe they voted here on the idea to actually close the vote :D
> That's really important IMO to get something for TomEE.
>
> If you think that is important we can push a new VOTE on the list and let
> it open for 72 hours as usual.
> but to be honest I don't think at all we'll get more votes.
>
> Jean-Louis
>
> 2012/10/8 David Blevins <da...@gmail.com>
>
> > I think the fact that we're getting votes on a '[RESULTS]' thread is a
> > sign there was no actual vote :)
> >
> > That said, it's pretty clear people like the direction. It would still
> be
> > great to have an actual logo contest and promote the project with it.
> >
> > I'll be happy to get that started this week.
> >
> >
> > -David
> >
> >
> > On Oct 8, 2012, at 8:19 AM, Jean-Louis MONTEIRO wrote:
> >
> > > Hi guys,
> > >
> > > Following what we decided 4 months ago (more than 40 days).
> > > So even if someone else disagree, the paw-print will be used as the
> > > official Apache TomEE logo.
> > >
> > > Jean-Louis
> > >
> > >
> > >
> > > 2012/6/4 Romain Manni-Bucau <rm...@gmail.com>
> > >
> > >> i globally agree even if i would have had it on the 12th.
> > >>
> > >> - Romain
> > >>
> > >>
> > >> 2012/6/4 David Blevins <da...@gmail.com>
> > >>
> > >>>
> > >>> On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote:
> > >>>
> > >>>> If we get a higher vote for the pawprint sum(+1/-1) vs
> (waitFor40days)
> > >>> we'll just go with it - pending David's decision of course.
> > >>>
> > >>> All things are project decisions of course. I get one vote like
> > everyone
> > >>> else :)
> > >>>
> > >>> My vote would be for the 40 day logo contest. If we don't do it we'd
> > be
> > >>> passing up a great chance to make some noise, attract some attention
> > and
> > >>> get several people contributing logos to the project which means more
> > >>> people contributing to the project.
> > >>>
> > >>> Would be a shame to miss out on all that buzz and excitement.
> > >>>
> > >>>
> > >>> -David
> > >>>
> > >>>
> > >>
> >
> >
>
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
Sorry David, but we have been talking about that for months.
Some people already voted for the paw-print.
Maybe they voted here on the idea to actually close the vote :D
That's really important IMO to get something for TomEE.
If you think that is important we can push a new VOTE on the list and let
it open for 72 hours as usual.
but to be honest I don't think at all we'll get more votes.
Jean-Louis
2012/10/8 David Blevins <da...@gmail.com>
> I think the fact that we're getting votes on a '[RESULTS]' thread is a
> sign there was no actual vote :)
>
> That said, it's pretty clear people like the direction. It would still be
> great to have an actual logo contest and promote the project with it.
>
> I'll be happy to get that started this week.
>
>
> -David
>
>
> On Oct 8, 2012, at 8:19 AM, Jean-Louis MONTEIRO wrote:
>
> > Hi guys,
> >
> > Following what we decided 4 months ago (more than 40 days).
> > So even if someone else disagree, the paw-print will be used as the
> > official Apache TomEE logo.
> >
> > Jean-Louis
> >
> >
> >
> > 2012/6/4 Romain Manni-Bucau <rm...@gmail.com>
> >
> >> i globally agree even if i would have had it on the 12th.
> >>
> >> - Romain
> >>
> >>
> >> 2012/6/4 David Blevins <da...@gmail.com>
> >>
> >>>
> >>> On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote:
> >>>
> >>>> If we get a higher vote for the pawprint sum(+1/-1) vs (waitFor40days)
> >>> we'll just go with it - pending David's decision of course.
> >>>
> >>> All things are project decisions of course. I get one vote like
> everyone
> >>> else :)
> >>>
> >>> My vote would be for the 40 day logo contest. If we don't do it we'd
> be
> >>> passing up a great chance to make some noise, attract some attention
> and
> >>> get several people contributing logos to the project which means more
> >>> people contributing to the project.
> >>>
> >>> Would be a shame to miss out on all that buzz and excitement.
> >>>
> >>>
> >>> -David
> >>>
> >>>
> >>
>
>
Re: [RESULT] Paw-print logo to become official TomEE logo
Posted by David Blevins <da...@gmail.com>.
I think the fact that we're getting votes on a '[RESULTS]' thread is a sign there was no actual vote :)
That said, it's pretty clear people like the direction. It would still be great to have an actual logo contest and promote the project with it.
I'll be happy to get that started this week.
-David
On Oct 8, 2012, at 8:19 AM, Jean-Louis MONTEIRO wrote:
> Hi guys,
>
> Following what we decided 4 months ago (more than 40 days).
> So even if someone else disagree, the paw-print will be used as the
> official Apache TomEE logo.
>
> Jean-Louis
>
>
>
> 2012/6/4 Romain Manni-Bucau <rm...@gmail.com>
>
>> i globally agree even if i would have had it on the 12th.
>>
>> - Romain
>>
>>
>> 2012/6/4 David Blevins <da...@gmail.com>
>>
>>>
>>> On Jun 4, 2012, at 12:05 PM, Neale Rudd wrote:
>>>
>>>> If we get a higher vote for the pawprint sum(+1/-1) vs (waitFor40days)
>>> we'll just go with it - pending David's decision of course.
>>>
>>> All things are project decisions of course. I get one vote like everyone
>>> else :)
>>>
>>> My vote would be for the 40 day logo contest. If we don't do it we'd be
>>> passing up a great chance to make some noise, attract some attention and
>>> get several people contributing logos to the project which means more
>>> people contributing to the project.
>>>
>>> Would be a shame to miss out on all that buzz and excitement.
>>>
>>>
>>> -David
>>>
>>>
>>