On 8/25/06, Wendy Smoak [EMAIL PROTECTED] wrote:
I'd be thrilled to have every commit reference a JIRA issue, but
that's probably too much to ask all at once. For now I'll be happy
with seeing more of them, and maybe we can move closer to 'all' at
some point in the future.
I am also strongly
Partial Page Rendering for tomahawk
---
Key: TOMAHAWK-618
URL: http://issues.apache.org/jira/browse/TOMAHAWK-618
Project: MyFaces Tomahawk
Issue Type: New Feature
Components: New Component
This is not the first time that the use of JIRA for tracking changes
has come up.
http://www.mail-archive.com/dev@myfaces.apache.org/msg13737.html
Every commit has the possibility of breaking the codebase or changing
expected behavior, and having JIRA issues helps to know why and how
these
[ http://issues.apache.org/jira/browse/TOMAHAWK-618?page=all ]
Catalin Kormos updated TOMAHAWK-618:
Status: Patch Available (was: Open)
Partial Page Rendering for tomahawk
---
Key: TOMAHAWK-618
Hi,Well, sandbox or not. I missed the discussion. Remember client sidevalidation stuff?
That was a good thread. Or the s:secureTag thread? These two weremuch more open development than here, I guess. Maybe that's all Imissed here. But to me this particular commit *smells*. Sorry, but
that's my
Hi all!
This is a initial commit so it is not yet well tested and there are
still a lot of
things to do, but if anyone wants to start playing around with it and
making
suggestions for improvements I would be thankful for some feedback.
JFYI - I've started to try to use it in our application,
Ok, but that's a far cry from Matze's for all commits. For all major
enhancements, I'm absolutely d'accord.
regards,
Martin
On 8/23/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 8/22/06, Martin Marinschek [EMAIL PROTECTED] wrote:
I really don't see the necessity for MyFaces committers to do
almost all ;)
wendy pointed out more detailed, what I was thinking about :)
On 8/23/06, Martin Marinschek [EMAIL PROTECTED] wrote:
Ok, but that's a far cry from Matze's for all commits. For all major
enhancements, I'm absolutely d'accord.
regards,
Martin
On 8/23/06, Wendy Smoak [EMAIL
In my case, JIRA helps me to keep track of things I'm working on. For example I've created issues for stuff like security resolver, excel exporter, client side validation and assigned these to myself. Of course this seems unnecessary for minor commits.
On 8/23/06, Matthias Wessendorf [EMAIL
yeah
same for fixing typos or else ;)
I had your stuff in mind, when I wrote these emails
I quoted some threads
On 8/23/06, Cagatay Civici [EMAIL PROTECTED] wrote:
In my case, JIRA helps me to keep track of things I'm working on. For
example I've created issues for stuff like security
Hello everyone,
After verifying the patches I send him Catalin was so kind and commited the
new sandbox component called PPRPanelGroup to the sandbox. With this
component you can souround areas of a page which you want to be updated
by AJAX calls. You just specify in the
After verifying the patches I send him Catalin was so kind and commited the
which patches?
what is the Jira issue number for that?
new sandbox component called PPRPanelGroup to the sandbox. With this
component you can souround areas of a page which you want to be updated
by AJAX calls. You
On 8/22/06, Ernst Fastl [EMAIL PROTECTED] wrote:
Hello everyone,
After verifying the patches I send him Catalin was so kind and commited the
new sandbox component called PPRPanelGroup to the sandbox.
Hi there! I think that's the commit I just commented on. :)
Matthias already asked if
For a substantial contribution like this, we'll need a CLA on file in
any case (even if the code came in through a jira-issue).
regards,
Martin
On 8/22/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 8/22/06, Ernst Fastl [EMAIL PROTECTED] wrote:
Hello everyone,
After verifying the patches I
I am not concerned about the icla or not
I am more concerned about the fact that patches sent offline
and not through Jira.
I mean, why ?
On 8/22/06, Martin Marinschek [EMAIL PROTECTED] wrote:
For a substantial contribution like this, we'll need a CLA on file in
any case (even if the code came
what about using Jira first.
for almost all commits ?
I mean this makes us more efficent to follow the development process ;)
So each change to API, non trivial enhancement, etc must! go through jira.
WDYT ?
-Matthias
On 8/22/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
I am not
On 8/22/06, Matthias Wessendorf [EMAIL PROTECTED]
wrote:
I am not concerned about the icla or notAs a PMC member for Apache MyFaces, you *should* be concerned about this.Part of the responsibility that the ASF Board delegates to each PMC is to ensure that all code ultimately included in the
Hi Matthias!
The sort of offline development. Sending offline a patch to a
committer for letting him commit the stuff is to me a -1. Looks like a
bypass.
Do you propose to use jira as mini-incubator?
I am not sure this is what it is meant for.
In this case it was committed to the sandbox, no?
On 8/22/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi Matthias!
The sort of offline development. Sending offline a patch to a
committer for letting him commit the stuff is to me a -1. Looks like a
bypass.
Do you propose to use jira as mini-incubator?
I am not sure this is what it is meant
Matthias, you're absolutely right - I'm just as concerned as you about
offline development, and asked Ernst several times to engage in an
discussion on the mailing list.
He did so in the beginning, but then ended up going back to his desk
to finish off his first draft of what the PPR support
I really don't see the necessity for MyFaces committers to do all
extensions of MyFaces through jira, if sufficient communication has
happened on the developer list first.
Why do you think that opening a jira-issue and adding patches will
make us more efficient in the development process?
One clarification: For external contributions, a jira-issue definitely
makes sense.
regards,
Martin
On 8/23/06, Martin Marinschek [EMAIL PROTECTED] wrote:
I really don't see the necessity for MyFaces committers to do all
extensions of MyFaces through jira, if sufficient communication has
On 8/22/06, Martin Marinschek [EMAIL PROTECTED] wrote:
One clarification: For external contributions, a jira-issue definitelymakes sense.A behavior that both the Struts and Shale communities have adopted (albeit recently in the case of Shale :-) is to have a JIRA issue for pretty much any
23 matches
Mail list logo
