[Wiki] Decisions so far

[Rafael Santos <rs...@spectacompany.com.br>]

I have created a first version for a page about the descions made so far on
Apache Flex
https://cwiki.apache.org/confluence/display/FLEX/Decisions+so+far

I am still reading past emails so let me know if I am missing something.

Rafael Santos - Specta

Re: [Wiki] Decisions so far

[Rafael Santos <rs...@spectacompany.com.br>]

On Thu, Mar 1, 2012 at 12:13, Carol Frampton <cf...@adobe.com> wrote:

>
> On 2/29/12 9 :49PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
> >Coding style could be in the same format as the existing code. ie If you
> >adding a patch to a file you should code in the same style as what is
> >currently in the file.
>
> I'd also add a pointer to
> http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions.  Yes,
> I realize not all the current code follows this but at least the code
> written by the Flex team should have.
>

*Added.*

Re: [Wiki] Decisions so far

[Omar Gonzalez <om...@gmail.com>]

>
> Re versioning I thought (but could be mistaken) we we going for 4.8 as the
> > initial release as Adobe may come out with some security patches etc.
> >
>
> *Done.*


I added some notes about these reserved version numbers to the wiki page
for the sake of clarity.

https://cwiki.apache.org/confluence/display/FLEX/Decisions+so+far

--
Omar Gonzalez
s9tpepper@apache.org
Apache Flex PPMC Member

Re: [Wiki] Decisions so far

[Rafael Santos <rs...@spectacompany.com.br>]

>
> In regards to building with Ant I hate to bing this up (yet again) but
> it's probably better to say that Ant is the current way of building the
> project and people are welcome to submit other methods of building the SDK.
> There's been no decision as such it's just that the donated code base uses
> Ant as it's build tool.
>

*Note taken*


Re versioning I thought (but could be mistaken) we we going for 4.8 as the
> initial release as Adobe may come out with some security patches etc.
>

*Done.*


 I'd also add.
> Until after the initial parity release it's preferred that any commits be
> made into a separate branch. The "patches" branch have been set up for this.
>

*Done,*


Until the Adobe JIRA bug base has been import it best to try and avoid
> creating JIRA issues that already exist in the Adobe JIRA bug base.
>

*Done.*


 Coding style could be in the same format as the existing code. ie If you
> adding a patch to a file you should code in the same style as what is
> currently in the file.
>

*Note taken.*

Re: [Wiki] Decisions so far

[Carol Frampton <cf...@adobe.com>]

On 2/29/12 9 :49PM, "Justin Mclean" <ju...@classsoftware.com> wrote:


>Coding style could be in the same format as the existing code. ie If you
>adding a patch to a file you should code in the same style as what is
>currently in the file.

I'd also add a pointer to
http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions.  Yes,
I realize not all the current code follows this but at least the code
written by the Flex team should have.

Carol

Re: [Wiki] Decisions so far

[Justin Mclean <ju...@classsoftware.com>]

Hi,

That's a good start.

In regards to building with Ant I hate to bing this up (yet again) but it's probably better to say that Ant is the current way of building the project and people are welcome to submit other methods of building the SDK. There's been no decision as such it's just that the donated code base uses Ant as it's build tool.

Re versioning I thought (but could be mistaken) we we going for 4.8 as the initial release as Adobe may come out with some security patches etc.

I'd also add.
Until after the initial parity release it's preferred that any commits be made into a separate branch. The "patches" branch have been set up for this.

Until the Adobe JIRA bug base has been import it best to try and avoid creating JIRA issues that already exist in the Adobe JIRA bug base.

Coding style could be in the same format as the existing code. ie If you adding a patch to a file you should code in the same style as what is currently in the file.

Thanks,
Justin

Re: [Wiki] Decisions so far

[Rafael Santos <rs...@spectacompany.com.br>]

On Thu, Mar 1, 2012 at 04:56, Jun Heider <ju...@realeyes.com> wrote:

>
> On Feb 29, 2012, at 7:25 PM, Rafael Santos wrote:
>
> > I have created a first version for a page about the descions made so far
> on
> > Apache Flex
> > https://cwiki.apache.org/confluence/display/FLEX/Decisions+so+far
>
> I may be missing some ML posts due to the traffic and being busy but from
> reading your first version of this WIKI page my comments:
>
> 1. Code Refactoring: org.apache.flex
>
> This has not been decided according to JIRA [1]
>

*Note taken.*


2. Versioning
>
> I'm not sure where the *reserved* versioning you list comes from but I'll
> take Omar's word for it.  That being said, version number for first release
> is still undecided according to JIRA [2]
>

*This was decided on the ML. I added the Issue link to Jira.*



> [1] https://issues.apache.org/jira/browse/FLEX-7
> [2] https://issues.apache.org/jira/browse/FLEX-10
>
>
>

Re: [Wiki] Decisions so far

[Jun Heider <ju...@realeyes.com>]

On Feb 29, 2012, at 7:25 PM, Rafael Santos wrote:

> I have created a first version for a page about the descions made so far on
> Apache Flex
> https://cwiki.apache.org/confluence/display/FLEX/Decisions+so+far

I may be missing some ML posts due to the traffic and being busy but from reading your first version of this WIKI page my comments:

1. Code Refactoring: org.apache.flex

This has not been decided according to JIRA [1]

2. Versioning

I'm not sure where the *reserved* versioning you list comes from but I'll take Omar's word for it.  That being said, version number for first release is still undecided according to JIRA [2]


[1] https://issues.apache.org/jira/browse/FLEX-7
[2] https://issues.apache.org/jira/browse/FLEX-10