On Mon, Jan 23, 2012 at 12:30 PM, Alex Harui wrote:
>
>
>
> On 1/23/12 3:00 AM, "Martin Heidegger" wrote:
>
> > I think the tension here is justified. Many people waited for a long
> > time to work on things and the expectations are high. Right now a lot
> > of requests and questions that the p
On Mon, Jan 23, 2012 at 3:17 PM, Justin Mclean wrote:
> Hi Greg,
>
>> Sort of. I wouldn't mind if patches are submitted to the mailing list until
>> Jira is ready.
> I did submit a patch to the mailing list but was told a) JIRA was the correct
> place and b) hold off until the Adobe JIRA bugs ha
On Mon, Jan 23, 2012 at 3:21 PM, Justin Mclean wrote:
> Hi Doug,
>
> Thanks for the info esp re lobbying committers on the list.
>
> I certainly meant no disrespect to Alex or anyone else who has put lots of
> hard work into getting this project this far.
No worries, was not my intent to imply y
Hi Doug,
Thanks for the info esp re lobbying committers on the list.
I certainly meant no disrespect to Alex or anyone else who has put lots of hard
work into getting this project this far.
Thanks,
Justin
Hi Greg,
> Sort of. I wouldn't mind if patches are submitted to the mailing list until
> Jira is ready.
I did submit a patch to the mailing list but was told a) JIRA was the correct
place and b) hold off until the Adobe JIRA bugs have been imported and then
resubmit my patch. I'm fine to wait a
On Mon, Jan 23, 2012 at 2:48 PM, Justin Mclean wrote:
> Hi Greg,
>
>> Nope, sorry. You have to be a committer to be able to commit to the
>> whiteboard. You can, however, submit patches in Jira.
>
> Understand. So what's the best way for non committers to submit unit tests,
> code samples showing
On Mon, Jan 23, 2012 at 3:48 PM, Justin Mclean wrote:
> Hi Greg,
>
>> Nope, sorry. You have to be a committer to be able to commit to the
>> whiteboard. You can, however, submit patches in Jira.
>
> Understand. So what's the best way for non committers to submit unit tests,
> code samples showing
Hi Greg,
> Nope, sorry. You have to be a committer to be able to commit to the
> whiteboard. You can, however, submit patches in Jira.
Understand. So what's the best way for non committers to submit unit tests,
code samples showing issues or new ideas not all of these things belong in
JIRA. Peo
On Mon, Jan 23, 2012 at 1:32 PM, Greg Reddin wrote:
> On Mon, Jan 23, 2012 at 3:28 PM, Justin Mclean
> wrote:
> >> You can work on the code in Carol's whiteboard, or do just about
> anything
> >> you want in your own whiteboard. You can discuss just about anything.
> >
> > Isn't that only true
On Mon, Jan 23, 2012 at 3:28 PM, Justin Mclean wrote:
>> You can work on the code in Carol's whiteboard, or do just about anything
>> you want in your own whiteboard. You can discuss just about anything.
>
> Isn't that only true for current committers? I asked this yesterday but no
> one answere
Hi,
> You can work on the code in Carol's whiteboard, or do just about anything
> you want in your own whiteboard. You can discuss just about anything.
Isn't that only true for current committers? I asked this yesterday but no one
answered. Is there any way for current non committers to have co
On 1/23/12 12:42 PM, "Martin Heidegger" wrote:
> On 24/01/2012 05:03, Alex Harui wrote:
>> Yes, there can be separate branches and release.
>
> Then that should be mentioned in the "versioning" thread, shouldn't it?
>
It has been mentioned in past versioning threads.
>> IMHO, Apache is more
On 24/01/2012 05:03, Alex Harui wrote:
Yes, there can be separate branches and release.
Then that should be mentioned in the "versioning" thread, shouldn't it?
IMHO, Apache is more about what actually happens, not so much about promises
and visions and missions. The missions can get changed,
On Mon, Jan 23, 2012 at 2:03 PM, Alex Harui wrote:
> IMHO, Apache is more about what actually happens, not so much about promises
> and visions and missions. The missions can get changed, forked, killed,
> whatever. It all depends on who actually gets something done.
You nailed it Alex! An Apac
On 1/23/12 11:56 AM, "Martin Heidegger" wrote:
> If there are multiple missions, will there be separate releases?
Yes, there can be separate branches and release.
> Even with multiple missions: Each mission should be properly defined.
> Its really hard to hit something without aiming.
IMHO, A
On 24/01/2012 03:30, Alex Harui wrote:
You can work on the code in Carol's whiteboard, or do just about anything
you want in your own whiteboard. You can discuss just about anything.
That is not the point: if some things are not going to make it anyway
into flex because it will not be donated a
On 1/23/12 11:04 AM, "Keith Sutton" wrote:
> If automation and SDK 3.6 (as two examples) are considered critical by
> the project to it's health and success within the ecosystem/industry
> then how is Apache Flex going to influence the decision makers at Adobe?
I don't think the issue here is
Having the vision/mission worked out is important to any project moving
forward however it is also important to have (or be aware of) the
necessary resources and support needed for success. Some of the
necessary pieces sometimes go beyond the code into the
platform/ecosystem/community/industry.
On 1/23/12 3:00 AM, "Martin Heidegger" wrote:
> I think the tension here is justified. Many people waited for a long
> time to work on things and the expectations are high. Right now a lot
> of requests and questions that the people have could be avoided if we
> had some certainties:
>
>
The odd number = dev / test release is a fairly well established approach...
I'm down with that.
--
Rick Winscot
On Monday, January 23, 2012 at 10:45 AM, David Arno wrote:
> > From: Rick Winscot [mailto:rick.wins...@gmail.com]
> > Sent: 23 January 2012 15:32
> > Is there anything that preve
> From: Rick Winscot [mailto:rick.wins...@gmail.com]
> Sent: 23 January 2012 15:32
> Is there anything that prevents us from calling the first build out the door
> a 'Release Candidate?' Then in Jira... adding a line item / known issue
> logged against it to get automation working?
"Release can
Is there anything that prevents us from calling the first build out the door a
'Release Candidate?' Then in Jira... adding a line item / known issue logged
against it to get automation working?
--
Rick Winscot
On Monday, January 23, 2012 at 8:33 AM, Frédéric Thomas wrote:
> David,
>
> Ori
David,
Originally, the plan was to make a first Apache release for testing
purposes, not for production, with or without changes/bugfixes, right ?
Then, apart from the fact that one can do w/o RSLs and Automation, at the
moment, we are still waiting for Mustella, I do not think we can release
What you are describing is a alpha/beta/pre-release/ something
not-finished. Concrete version numbers without that statement would be
widely considered "finished" and usable.
yours
Martin.
On 23/01/2012 21:23, El Koro wrote:
From: "David Arno"
It is Apache Flex that risks the bad PR if
> From: El Koro [mailto:k...@noos.fr]
> Sent: 23 January 2012 12:24
>
> David, I think there is a misunderstanding here.
> As it has been discussed previously, the goal of the first release (4.7 or
> 4.8 or 4.2012 or ... ) would be like a practice release for the project,
> not a "look world, her
From: "David Arno"
It is Apache Flex that risks the bad PR if 4.7 is released too early.
David.
David, I think there is a misunderstanding here.
As it has been discussed previously, the goal of the first release (4.7 or
4.8 or 4.2012 or ... ) would be like a practice release for the project,
> From: Giorgio Natili [mailto:g.nat...@gnstudio.com]
> Sent: 23 January 2012 11:44
>>There is a difficult line to walk between the bad PR of a too-early
>>release and the community losing interest if it takes too long. Again
>>it would be useful to try and reach a consensus on this. Maybe it's
> From: Martin Heidegger [mailto:m...@leichtgewicht.at]
> Sent: 23 January 2012 11:00
> I think this sort of questions are important right now as the lack of
answers
> seem to agitate the group and throttle the motivation.
> I also think that these questions need to be answered by the Project tea
I think the tension here is justified. Many people waited for a long
time to work on things and the expectations are high. Right now a lot
of requests and questions that the people have could be avoided if we
had some certainties:
* What can we work on/discuss about?
As far as I know A
29 matches
Mail list logo
