You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Justin Mclean <ju...@gmail.com> on 2013/09/04 02:09:32 UTC

Nighly builds and releases

Hi,

An issue just come up on the incubator general list about nightly builds. [1]

The installer lets you download the nightly build, and while convenient it looks like it's actually against Apache release guidelines [2]:
"If the general public is being instructed to download a package, then that package has been released. Each PMC must obey the ASF requirements on approving any release."
and
" Do not include any links on the project website that might encourage non-developers to download and use nightly builds, snapshots, release candidates, or any other similar package."

We probably need to remove that from the installer. Perhaps an alternative is  it only show via a command line flag or "I am a SDK developer" check box with a big disclaimer about it not being an official release etc etc

Justin

1. http://markmail.org/thread/s3ghrm7oozng3w7t
2. http://www.apache.org/dev/release.html#what

Re: Nighly builds and releases

Posted by Justin Mclean <ju...@classsoftware.com>.
HI,

> I think it's too beneficial to everyone who wants to the bleeding edge to
> not have nightlies for testing and development.
Agree but we can't be providing it to SDK users as the latest release - it's for development use only.

Justin

Re: Nighly builds and releases

Posted by Mark Kessler <ke...@gmail.com>.
I think it's too beneficial to everyone who wants to the bleeding edge to
not have nightlies for testing and development.  I'll agree we should just
post a "Here be Dragons" type caveat emptor.

-Mark


On Tue, Sep 3, 2013 at 8:25 PM, OmPrakash Muppirala <bi...@gmail.com>wrote:

> A google search for "apache nightly build" shows me quite a few Apache
> projects providing public links to nightly builds:
>
> 1.  Solr: http://wiki.apache.org/solr/NightlyBuilds
> 2.  JMeter: http://jmeter.apache.org/nightly.html
> 3.  Direcory: http://directory.apache.org/studio/nightly-builds.html
> 4.  Nutch: http://nutch.apache.org/nightly.html
> 5.  Ant: http://ant.apache.org/nightlies.html
>
> The list goes on...
>
> I think adding a warning saying this should be sufficient:
>
> The nightly builds are interim builds that are * untested and unsupported
> *.
> * Use at your own risk! *
> These unreleased builds may not even load, may have undocumented features,
> known defects, and any number of other issues.
> They are intended for use by developers and others wishing to help with
> resolving Apache Flex bugs.
>
> Thanks,
> Om
>
>

Re: Nighly builds and releases

Posted by OmPrakash Muppirala <bi...@gmail.com>.
A google search for "apache nightly build" shows me quite a few Apache
projects providing public links to nightly builds:

1.  Solr: http://wiki.apache.org/solr/NightlyBuilds
2.  JMeter: http://jmeter.apache.org/nightly.html
3.  Direcory: http://directory.apache.org/studio/nightly-builds.html
4.  Nutch: http://nutch.apache.org/nightly.html
5.  Ant: http://ant.apache.org/nightlies.html

The list goes on...

I think adding a warning saying this should be sufficient:

The nightly builds are interim builds that are * untested and unsupported *.
* Use at your own risk! *
These unreleased builds may not even load, may have undocumented features,
known defects, and any number of other issues.
They are intended for use by developers and others wishing to help with
resolving Apache Flex bugs.

Thanks,
Om


On Tue, Sep 3, 2013 at 5:09 PM, Justin Mclean <ju...@gmail.com>wrote:

> Hi,
>
> An issue just come up on the incubator general list about nightly builds.
> [1]
>
> The installer lets you download the nightly build, and while convenient it
> looks like it's actually against Apache release guidelines [2]:
> "If the general public is being instructed to download a package, then
> that package has been released. Each PMC must obey the ASF requirements on
> approving any release."
> and
> " Do not include any links on the project website that might encourage
> non-developers to download and use nightly builds, snapshots, release
> candidates, or any other similar package."
>
> We probably need to remove that from the installer. Perhaps an alternative
> is  it only show via a command line flag or "I am a SDK developer" check
> box with a big disclaimer about it not being an official release etc etc
>
> Justin
>
> 1. http://markmail.org/thread/s3ghrm7oozng3w7t
> 2. http://www.apache.org/dev/release.html#what

RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
I didn't have a look at how it was done and I would rather prefer a Justin
agreement and eventually help than spending time for nothing.

-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com] 
Envoyé : mercredi 4 septembre 2013 18:16
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

You are a committer so you can make those changes and see if anyone vetoes
it.  I won't.

On 9/4/13 9:11 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:

>The other benefit except it would make the maven converter working for 
>snapshots, would be that the flex-sdk-description.xml which is not git 
>ignored today would not hassles any more at commit time after a build.
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mercredi 4 septembre 
>2013 18:02 À : dev@flex.apache.org Objet : Re: Nighly builds and 
>releases
>
>We could change the build number back to 0 and only set the build 
>number in the release branches.
>
>On 9/4/13 5:01 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
>
>>An option could be to add a checkbox labeled "I am an Apache Flex SDK 
>>developer" above the SDKs combobox and show the "Nightly build" option 
>>if selected but please don't change the version pattern or whatever, 
>>I'm already annoyed because the build number is no more set to 0 on 
>>the dev branch.
>>
>>It won't be a problem with the installer as we know the user choose 
>>"Nightly build" but it is one when out of the installer, when one 
>>prepares the dev branch to work on an IDE and wants to run the maven 
>>converter on it.
>>Before the converter was able to create a SNAPSHOT version based on 
>>the build number set to "0", today is not, it creates a release 
>>instead which is not convenient.
>>One have to remember another step replacing  the build number to "0"
>>before
>>running it, it seems nothing but it is a waste of time when forgotten 
>>and indeed it is not documented.
>>
>>Happily with the installer maven feature, there will be a way to make 
>>a SNAPSHOT based on the user choice.
>>
>>-Fred
>>
>>-----Message d'origine-----
>>De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : mercredi
>>4 septembre 2013 02:54 À : dev@flex.apache.org Objet : Re: Nighly 
>>builds and releases
>>
>>HI,
>>
>>> The tracking is based on the Flex version.  We dont make a 
>>> distinction between the nightly vs. released sdk.  We should 
>>> probably bump up the version number in our develop branch to start 
>>> tracking the
>nightlies.
>>
>>Were is it pickup up the version from? The develop branch should have 
>>all versions at 4.11.
>>
>>Thanks,
>>Justin
>


Re: Nighly builds and releases

Posted by Alex Harui <ah...@adobe.com>.
You are a committer so you can make those changes and see if anyone vetoes
it.  I won't.

On 9/4/13 9:11 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:

>The other benefit except it would make the maven converter working for
>snapshots, would be that the flex-sdk-description.xml which is not git
>ignored today would not hassles any more at commit time after a build.
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com]
>Envoyé : mercredi 4 septembre 2013 18:02
>À : dev@flex.apache.org
>Objet : Re: Nighly builds and releases
>
>We could change the build number back to 0 and only set the build number
>in
>the release branches.
>
>On 9/4/13 5:01 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
>
>>An option could be to add a checkbox labeled "I am an Apache Flex SDK
>>developer" above the SDKs combobox and show the "Nightly build" option
>>if selected but please don't change the version pattern or whatever,
>>I'm already annoyed because the build number is no more set to 0 on the
>>dev branch.
>>
>>It won't be a problem with the installer as we know the user choose
>>"Nightly build" but it is one when out of the installer, when one
>>prepares the dev branch to work on an IDE and wants to run the maven
>>converter on it.
>>Before the converter was able to create a SNAPSHOT version based on the
>>build number set to "0", today is not, it creates a release instead
>>which is not convenient.
>>One have to remember another step replacing  the build number to "0"
>>before
>>running it, it seems nothing but it is a waste of time when forgotten
>>and indeed it is not documented.
>>
>>Happily with the installer maven feature, there will be a way to make a
>>SNAPSHOT based on the user choice.
>>
>>-Fred
>>
>>-----Message d'origine-----
>>De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : mercredi
>>4 septembre 2013 02:54 À : dev@flex.apache.org Objet : Re: Nighly
>>builds and releases
>>
>>HI,
>>
>>> The tracking is based on the Flex version.  We dont make a
>>> distinction between the nightly vs. released sdk.  We should probably
>>> bump up the version number in our develop branch to start tracking the
>nightlies.
>>
>>Were is it pickup up the version from? The develop branch should have
>>all versions at 4.11.
>>
>>Thanks,
>>Justin
>


RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
The other benefit except it would make the maven converter working for
snapshots, would be that the flex-sdk-description.xml which is not git
ignored today would not hassles any more at commit time after a build.

-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com] 
Envoyé : mercredi 4 septembre 2013 18:02
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

We could change the build number back to 0 and only set the build number in
the release branches.

On 9/4/13 5:01 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:

>An option could be to add a checkbox labeled "I am an Apache Flex SDK 
>developer" above the SDKs combobox and show the "Nightly build" option 
>if selected but please don't change the version pattern or whatever, 
>I'm already annoyed because the build number is no more set to 0 on the 
>dev branch.
>
>It won't be a problem with the installer as we know the user choose 
>"Nightly build" but it is one when out of the installer, when one 
>prepares the dev branch to work on an IDE and wants to run the maven 
>converter on it.
>Before the converter was able to create a SNAPSHOT version based on the 
>build number set to "0", today is not, it creates a release instead 
>which is not convenient.
>One have to remember another step replacing  the build number to "0"
>before
>running it, it seems nothing but it is a waste of time when forgotten 
>and indeed it is not documented.
>
>Happily with the installer maven feature, there will be a way to make a 
>SNAPSHOT based on the user choice.
>
>-Fred
>
>-----Message d'origine-----
>De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : mercredi 
>4 septembre 2013 02:54 À : dev@flex.apache.org Objet : Re: Nighly 
>builds and releases
>
>HI,
>
>> The tracking is based on the Flex version.  We dont make a 
>> distinction between the nightly vs. released sdk.  We should probably 
>> bump up the version number in our develop branch to start tracking the
nightlies.
>
>Were is it pickup up the version from? The develop branch should have 
>all versions at 4.11.
>
>Thanks,
>Justin


Re: Nighly builds and releases

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

We can fix things in release (vi hotfixs or directly) but the changes need to be tested, develop is the best place to do that as that's what the CI runs off. Last release we made changes in release and merge back to develop frequently. Even if we didn't do this at some point you need to merge any changes made in release back to develop, otherwise how do you work on the next release? The next release is branched from develop not the previous release branch.

We need a process that works with the constraints we have (ie Apache release process and our CI infrastructure) not some abstract ideal.

Thanks,
Justin

RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
In this particular case, merging fixes made on branches are enough IMO, no
needs to merge back the entire release, I guess it should be a painful job
sorting out what to keep or not otherwise.

-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com] 
Envoyé : jeudi 5 septembre 2013 18:48
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

Maybe I'm not understanding the diagram on their page.  To me there is a
line back from release branch to develop.  It shouldn't have anything to do
with hotfixes, just bug fixes found and fixed after the release branch is
cut.  I think the recommended practice when you have a release branch is to
fix bugs in the release branch and merge  back to develop as I think the
diagram also shows.  If you merge the other way you run the risk of picking
up a develop branch change you didn't intend to pick up.

So, I think we will always need to merge back.

-Alex

On 9/5/13 9:41 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:

>The only thing making this model merging back the release branch to the 
>dev one is they allow hotfixing on the release branch, so, yes, if they 
>are some, we need to merge them back but here at Apache Flex we don't 
>have this emergency to deliver, so, the bugs can be fixed on the dev 
>branch and another RC can be done.
>
>Not having hotfixes on the release branch makes the merge back useless 
>because there nothing left to, so, why do it and then change the build 
>number ?
>
>Instead, because we haven't this need to merge back as soon as we fix 
>the bugs on the dev branch only, we could simply let the dev branch 
>unmerged as it represents already what is released and the build 
>version will keep its 0 value unchanged too.
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : jeudi 5 septembre 
>2013 18:14 À : dev@flex.apache.org Objet : Re: Nighly builds and 
>releases
>
>
>
>On 9/5/13 3:23 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
>
>>After running sdk/ant, git status report only " flex-sdk-description.xml"
>>as
>>modified file, that's 5 months or so I didn't have a look in the SDK, 
>>could you tell me what should be done in order the build number be 
>>created only on the release build envisioning what impact it could 
>>introduce ?
>IMO, we just have to decide that's what we want to do.
>
>Note that the Git Branching Model does show release branches merged 
>back to develop.  It mentions that there is often a merge conflict with 
>the version number file but doesn't explicitly say what to do about it.  
>We can try leaving the version number unchanged at 0 in the develop 
>branch and after a release branch merge changes it, set it back to 0.
>
>-Alex
>


Re: Nighly builds and releases

Posted by Alex Harui <ah...@adobe.com>.
Maybe I'm not understanding the diagram on their page.  To me there is a
line back from release branch to develop.  It shouldn't have anything to
do with hotfixes, just bug fixes found and fixed after the release branch
is cut.  I think the recommended practice when you have a release branch
is to fix bugs in the release branch and merge  back to develop as I think
the diagram also shows.  If you merge the other way you run the risk of
picking up a develop branch change you didn't intend to pick up.

So, I think we will always need to merge back.

-Alex

On 9/5/13 9:41 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:

>The only thing making this model merging back the release branch to the
>dev
>one is they allow hotfixing on the release branch, so, yes, if they are
>some, we need to merge them back but here at Apache Flex we don't have
>this
>emergency to deliver, so, the bugs can be fixed on the dev branch and
>another RC can be done.
>
>Not having hotfixes on the release branch makes the merge back useless
>because there nothing left to, so, why do it and then change the build
>number ?
>
>Instead, because we haven't this need to merge back as soon as we fix the
>bugs on the dev branch only, we could simply let the dev branch unmerged
>as
>it represents already what is released and the build version will keep
>its 0
>value unchanged too.
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com]
>Envoyé : jeudi 5 septembre 2013 18:14
>À : dev@flex.apache.org
>Objet : Re: Nighly builds and releases
>
>
>
>On 9/5/13 3:23 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
>
>>After running sdk/ant, git status report only " flex-sdk-description.xml"
>>as
>>modified file, that's 5 months or so I didn't have a look in the SDK,
>>could you tell me what should be done in order the build number be
>>created only on the release build envisioning what impact it could
>>introduce ?
>IMO, we just have to decide that's what we want to do.
>
>Note that the Git Branching Model does show release branches merged back
>to
>develop.  It mentions that there is often a merge conflict with the
>version
>number file but doesn't explicitly say what to do about it.  We can try
>leaving the version number unchanged at 0 in the develop branch and after
>a
>release branch merge changes it, set it back to 0.
>
>-Alex
>


RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
The only thing making this model merging back the release branch to the dev
one is they allow hotfixing on the release branch, so, yes, if they are
some, we need to merge them back but here at Apache Flex we don't have this
emergency to deliver, so, the bugs can be fixed on the dev branch and
another RC can be done.

Not having hotfixes on the release branch makes the merge back useless
because there nothing left to, so, why do it and then change the build
number ?

Instead, because we haven't this need to merge back as soon as we fix the
bugs on the dev branch only, we could simply let the dev branch unmerged as
it represents already what is released and the build version will keep its 0
value unchanged too.

-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com] 
Envoyé : jeudi 5 septembre 2013 18:14
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases



On 9/5/13 3:23 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:

>After running sdk/ant, git status report only " flex-sdk-description.xml"
>as
>modified file, that's 5 months or so I didn't have a look in the SDK, 
>could you tell me what should be done in order the build number be 
>created only on the release build envisioning what impact it could 
>introduce ?
IMO, we just have to decide that's what we want to do.

Note that the Git Branching Model does show release branches merged back to
develop.  It mentions that there is often a merge conflict with the version
number file but doesn't explicitly say what to do about it.  We can try
leaving the version number unchanged at 0 in the develop branch and after a
release branch merge changes it, set it back to 0.

-Alex


Re: Nighly builds and releases

Posted by Alex Harui <ah...@adobe.com>.

On 9/5/13 3:23 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:

>After running sdk/ant, git status report only " flex-sdk-description.xml"
>as
>modified file, that's 5 months or so I didn't have a look in the SDK,
>could
>you tell me what should be done in order the build number be created only
>on
>the release build envisioning what impact it could introduce ?
IMO, we just have to decide that's what we want to do.

Note that the Git Branching Model does show release branches merged back
to develop.  It mentions that there is often a merge conflict with the
version number file but doesn't explicitly say what to do about it.  We
can try leaving the version number unchanged at 0 in the develop branch
and after a release branch merge changes it, set it back to 0.

-Alex


RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
After running sdk/ant, git status report only " flex-sdk-description.xml" as
modified file, that's 5 months or so I didn't have a look in the SDK, could
you tell me what should be done in order the build number be created only on
the release build envisioning what impact it could introduce ?

-Fred

-----Message d'origine-----
De : Frédéric THOMAS [mailto:webdoublefx@hotmail.com] 
Envoyé : jeudi 5 septembre 2013 11:47
À : dev@flex.apache.org
Objet : RE: Nighly builds and releases

Sorry for the delay, I was reading this before to go to sleep, it was more
than 5am so, I answer only now.

> It mostly likely be fixed on the release branch and merged back to 
> develop
when done, but fixing on develop, testing (see CI above) and then merging
into release may also be an option.

You're right and that's the good option IMO, I mean not hotfixing on the
release branch, usually, hotfixes (done on the release branch as opposed as
the bugfixes done on the dev branch) are done because there is a pressure to
deliver quickly a new version to clients, it is the case in enterprises but
not here at Apache Flex, so, there is no reasons to hotfix, the counterpart
for enterprises, of doing hotfixing is they have to merge them back to the
dev branch.

So, because we don't have the pressure to deliver quickly, we can fix RC
bugs on the dev branch at the cost of having  to launch another release once
fixed and ready.
Doing such, we don't have to merge back and the release process brings to
the release branch only what it is originally done for, the creation of a
build number which is no more merge back to the dev branch.

As reference, the following line are taken from
http://nvie.com/posts/a-successful-git-branching-model/

" Release branches support preparation of a new production release. They
allow for last-minute dotting of i’s and crossing t’s. Furthermore, they
allow for minor bug fixes and preparing meta-data for a release (version
number, build dates, etc.). By doing all of this work on a release branch,
the develop branch is cleared to receive features for the next big release."

Does this process, not allowing to hotfixes on RC and thus, not having to
merge back, look less error prone and less harder for now ?

-Fred

-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : jeudi 5
septembre 2013 05:10 À : dev@flex.apache.org Objet : Re: Nighly builds and
releases

Hi,

> That's here there is something I don't know, what should be merged 
> back to the develop branch ?
Changes would be made in the release branch and merged into develop,
otherwise the two branches would diverge and develop would no longer be a
representation of the last release. All of the CI runs off the develop
branch so it's best if that is as close to release as possible - which is
why last time we released we merged into develop several times.

> We haven't got hotfixes and if something goes wrong with the RC, it is 
> fixed on the dev branch and another RC is done, right ?
It mostly likely be fixed on the release branch and merged back to develop
when done, but fixing on develop, testing (see CI above) and then merging
into release may also be an option.

Justin

RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
Sorry for the delay, I was reading this before to go to sleep, it was more
than 5am so, I answer only now.

> It mostly likely be fixed on the release branch and merged back to develop
when done, but fixing on develop, testing (see CI above) and then merging
into release may also be an option.

You're right and that's the good option IMO, I mean not hotfixing on the
release branch, usually, hotfixes (done on the release branch as opposed as
the bugfixes done on the dev branch) are done because there is a pressure to
deliver quickly a new version to clients, it is the case in enterprises but
not here at Apache Flex, so, there is no reasons to hotfix, the counterpart
for enterprises, of doing hotfixing is they have to merge them back to the
dev branch.

So, because we don't have the pressure to deliver quickly, we can fix RC
bugs on the dev branch at the cost of having  to launch another release once
fixed and ready.
Doing such, we don't have to merge back and the release process brings to
the release branch only what it is originally done for, the creation of a
build number which is no more merge back to the dev branch.

As reference, the following line are taken from
http://nvie.com/posts/a-successful-git-branching-model/

" Release branches support preparation of a new production release. They
allow for last-minute dotting of i’s and crossing t’s. Furthermore, they
allow for minor bug fixes and preparing meta-data for a release (version
number, build dates, etc.). By doing all of this work on a release branch,
the develop branch is cleared to receive features for the next big release."

Does this process, not allowing to hotfixes on RC and thus, not having to
merge back, look less error prone and less harder for now ?

-Fred

-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com] 
Envoyé : jeudi 5 septembre 2013 05:10
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

Hi,

> That's here there is something I don't know, what should be merged 
> back to the develop branch ?
Changes would be made in the release branch and merged into develop,
otherwise the two branches would diverge and develop would no longer be a
representation of the last release. All of the CI runs off the develop
branch so it's best if that is as close to release as possible - which is
why last time we released we merged into develop several times.

> We haven't got hotfixes and if something goes wrong with the RC, it is 
> fixed on the dev branch and another RC is done, right ?
It mostly likely be fixed on the release branch and merged back to develop
when done, but fixing on develop, testing (see CI above) and then merging
into release may also be an option.

Justin

Re: Nighly builds and releases

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

> That's here there is something I don't know, what should be merged back to
> the develop branch ?
Changes would be made in the release branch and merged into develop, otherwise the two branches would diverge and develop would no longer be a representation of the last release. All of the CI runs off the develop branch so it's best if that is as close to release as possible - which is why last time we released we merged into develop several times.

> We haven't got hotfixes and if something goes wrong with the RC, it is fixed
> on the dev branch and another RC is done, right ?
It mostly likely be fixed on the release branch and merged back to develop when done, but fixing on develop, testing (see CI above) and then merging into release may also be an option.

Justin

RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
> How do you merge back into develop easily?

That's here there is something I don't know, what should be merged back to
the develop branch ?
We haven't got hotfixes and if something goes wrong with the RC, it is fixed
on the dev branch and another RC is done, right ?
Even if we would fix on the RC, only this fix should be merged back or I'm
wrong ?

What else ?

-Fred

-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com] 
Envoyé : jeudi 5 septembre 2013 04:05
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

HI,

> What was the problem exactly ?
One of the RCs had a build number of 0. The file in question was in
gitignore so the difference wasn't picked up until a RC had been made and
several people had tested it.

> why attributing a build number only at release time would make it harder
How do you merge back into develop easily? Isn't it simpler not to have
exceptions, rather than say merge all files except these ones. The release
process is complex enough as it is and we're had zero people other than me
to step forward to do a release (past the initial 4.8 one) because of that.

Thanks,
Justin


Re: Nighly builds and releases

Posted by Justin Mclean <ju...@classsoftware.com>.
HI,

> What was the problem exactly ?
One of the RCs had a build number of 0. The file in question was in gitignore so the difference wasn't picked up until a RC had been made and several people had tested it.

> why attributing a build number only at release time would make it harder
How do you merge back into develop easily? Isn't it simpler not to have exceptions, rather than say merge all files except these ones. The release process is complex enough as it is and we're had zero people other than me to step forward to do a release (past the initial 4.8 one) because of that.

Thanks,
Justin


RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
> That could and has caused errors, one of the 4.10.0 RC had to be redone
because of this exact issue.

What was the problem exactly ?

> Making and testing a RC is a lot of effort and I rather make that easier
rather than harder or ending up with an RC missing a build number.

Sure it is a lot of effort and coffees I guess but maybe because I can't see
why attributing a build number only at release time would make it harder and
how it can be missed if it is done that way, I can't see the relation with
the fact it makes it harder.

Thanks,
-Fred

-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com] 
Envoyé : jeudi 5 septembre 2013 03:15
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

Hi,

> I haven't look at how and when the date is added yet but can't we 
> decide to add this date from the release target only as the release 
> target is supposed to be run on a release branch only ?

That could and has caused errors, one of the 4.10.0 RC had to be redone
because of this exact issue.

Making and testing a RC is a lot of effort and I rather make that easier
rather than harder or ending up with an RC missing a build number.

Take a  look at building the release here:
https://cwiki.apache.org/confluence/display/FLEX/Release+Guide+for+the+SDK

"Other ant targets you may want to become familiar with are source-release,
source-package, binary-release, binary-package and rat-check. These are
useful if you modify the files in the kit and you want to short circuit some
of the build process to test your changes."

Thanks,
Justin

Re: Nighly builds and releases

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

> I haven't look at how and when the date is added yet but can't we decide to
> add this date from the release target only as the release target is supposed
> to be run on a release branch only ?

That could and has caused errors, one of the 4.10.0 RC had to be redone because of this exact issue.

Making and testing a RC is a lot of effort and I rather make that easier rather than harder or ending up with an RC missing a build number.

Take a  look at building the release here:
https://cwiki.apache.org/confluence/display/FLEX/Release+Guide+for+the+SDK

"Other ant targets you may want to become familiar with are source-release, source-package, binary-release, binary-package and rat-check. These are useful if you modify the files in the kit and you want to short circuit some of the build process to test your changes."

Thanks,
Justin

RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
I haven't look at how and when the date is added yet but can't we decide to
add this date from the release target only as the release target is supposed
to be run on a release branch only ?

-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com] 
Envoyé : jeudi 5 septembre 2013 02:01
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

Hi,

If you can work out how to make a release than then do the merge without
merging the build number go for it. 

You need to update this:
https://cwiki.apache.org/confluence/display/FLEX/Release+Guide+for+the+SDK

Thanks,
Justin

Re: Nighly builds and releases

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

If you can work out how to make a release than then do the merge without merging the build number go for it. 

You need to update this:
https://cwiki.apache.org/confluence/display/FLEX/Release+Guide+for+the+SDK

Thanks,
Justin

RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
I see a major difference though, because the release branch is a branch to
be released, it can add the build number without affected the normal git
workflow, the release branch is based on the develop branch (think extends),
they don't need to be equals in everything, that's the goal of doing a
release branch, make the release into, so, it means as well adding the build
number.

-Fred

-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com] 
Envoyé : jeudi 5 septembre 2013 01:48
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

Hi,

> Following nvie.com/posts/a-successful-git-branching-model/ the develop 
> branch is never merged to the trunk but the release branch yes.

Yep that right, I've not had my coffee yet :-) 

Same issue basically as the release branch is branched from develop, worked
on, tagged, released and then the release branch is merged back into both
develop and trunk.

Justin

Re: Nighly builds and releases

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

> Following nvie.com/posts/a-successful-git-branching-model/ the develop
> branch is never merged to the trunk but the release branch yes.

Yep that right, I've not had my coffee yet :-) 

Same issue basically as the release branch is branched from develop, worked on, tagged, released and then the release branch is merged back into both develop and trunk.

Justin

RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
Following nvie.com/posts/a-successful-git-branching-model/ the develop
branch is never merged to the trunk but the release branch yes.

-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com] 
Envoyé : jeudi 5 septembre 2013 00:45
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

HI,

> Are you sure this assertion is true for branches under development 
> (dev / features or bugs).
As part of the current release process, the release is tagged and then
develop is merged into trunk, otherwise it would not be a true reflexion of
what we actually released.

Can you see a better way of doing this?

Justin

Re: Nighly builds and releases

Posted by Alex Harui <ah...@adobe.com>.

On 9/4/13 3:44 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:

>HI,
>
>> Are you sure this assertion is true for branches under development (dev
>>/
>> features or bugs).
>As part of the current release process, the release is tagged and then
>develop is merged into trunk, otherwise it would not be a true reflexion
>of what we actually released.
>
>Can you see a better way of doing this?
Makes sense.  After we merge back in, can we set it back to 0 in the dev
branch?  IIRC, the git branching model somehow only changed the version in
the release branch.

I may be way off since I don't fully understand the issue.

-Alex


Re: Nighly builds and releases

Posted by Justin Mclean <ju...@classsoftware.com>.
HI,

> Are you sure this assertion is true for branches under development (dev /
> features or bugs).
As part of the current release process, the release is tagged and then develop is merged into trunk, otherwise it would not be a true reflexion of what we actually released.

Can you see a better way of doing this?

Justin

RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi Justin,

Are you sure this assertion is true for branches under development (dev /
features or bugs).

-Fred

-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com] 
Envoyé : jeudi 5 septembre 2013 00:19
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

HI,

> We could change the build number back to 0 and only set the build 
> number in the release branches.

I assume we talking about the build number in flex-sdk-description.xml?

The source code (in GIt) needs to reflect what we actually tag and release
and that includes the .xml files IMO.

Thanks,
Justin

Re: Nighly builds and releases

Posted by Justin Mclean <ju...@classsoftware.com>.
HI,

> We could change the build number back to 0 and only set the build number
> in the release branches.

I assume we talking about the build number in flex-sdk-description.xml?

The source code (in GIt) needs to reflect what we actually tag and release and that includes the .xml files IMO.

Thanks,
Justin

Re: Nighly builds and releases

Posted by Alex Harui <ah...@adobe.com>.
We could change the build number back to 0 and only set the build number
in the release branches.

On 9/4/13 5:01 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:

>An option could be to add a checkbox labeled "I am an Apache Flex SDK
>developer" above the SDKs combobox and show the "Nightly build" option if
>selected but please don't change the version pattern or whatever, I'm
>already annoyed because the build number is no more set to 0 on the dev
>branch.
>
>It won't be a problem with the installer as we know the user choose
>"Nightly
>build" but it is one when out of the installer, when one prepares the dev
>branch to work on an IDE and wants to run the maven converter on it.
>Before the converter was able to create a SNAPSHOT version based on the
>build number set to "0", today is not, it creates a release instead which
>is
>not convenient.
>One have to remember another step replacing  the build number to "0"
>before
>running it, it seems nothing but it is a waste of time when forgotten and
>indeed it is not documented.
>
>Happily with the installer maven feature, there will be a way to make a
>SNAPSHOT based on the user choice.
>
>-Fred
>
>-----Message d'origine-----
>De : Justin Mclean [mailto:justin@classsoftware.com]
>Envoyé : mercredi 4 septembre 2013 02:54
>À : dev@flex.apache.org
>Objet : Re: Nighly builds and releases
>
>HI,
>
>> The tracking is based on the Flex version.  We dont make a distinction
>> between the nightly vs. released sdk.  We should probably bump up the
>> version number in our develop branch to start tracking the nightlies.
>
>Were is it pickup up the version from? The develop branch should have all
>versions at 4.11.
>
>Thanks,
>Justin


RE: Nighly builds and releases

Posted by Frédéric THOMAS <we...@hotmail.com>.
An option could be to add a checkbox labeled "I am an Apache Flex SDK
developer" above the SDKs combobox and show the "Nightly build" option if
selected but please don't change the version pattern or whatever, I'm
already annoyed because the build number is no more set to 0 on the dev
branch.

It won't be a problem with the installer as we know the user choose "Nightly
build" but it is one when out of the installer, when one prepares the dev
branch to work on an IDE and wants to run the maven converter on it.
Before the converter was able to create a SNAPSHOT version based on the
build number set to "0", today is not, it creates a release instead which is
not convenient.
One have to remember another step replacing  the build number to "0" before
running it, it seems nothing but it is a waste of time when forgotten and
indeed it is not documented.

Happily with the installer maven feature, there will be a way to make a
SNAPSHOT based on the user choice.

-Fred

-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com] 
Envoyé : mercredi 4 septembre 2013 02:54
À : dev@flex.apache.org
Objet : Re: Nighly builds and releases

HI,

> The tracking is based on the Flex version.  We dont make a distinction 
> between the nightly vs. released sdk.  We should probably bump up the 
> version number in our develop branch to start tracking the nightlies.

Were is it pickup up the version from? The develop branch should have all
versions at 4.11.

Thanks,
Justin

Re: Nighly builds and releases

Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Wed, Sep 4, 2013 at 11:15 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> The job that creates the artifacts is simply running "ant super-clean
> release create-md5". It is not explicitly changing the filenames. I
> guess there is still something/somewhere left to update to "4.11.0"?
>
> EdB
>
>
I see that in flex-sdk-description.xml, we have this section:

# flex-sdk-description values
release = Apache Flex 4.10.0
release.version = 4.10.0

Now that 4.10 has shipped, these can be bumped up to 4.11.0, right?

Thanks,
Om


>
>
> On Wed, Sep 4, 2013 at 7:25 PM, OmPrakash Muppirala
> <bi...@gmail.com> wrote:
> > On Wed, Sep 4, 2013 at 10:14 AM, Erik de Bruin <er...@ixsoftware.nl>
> wrote:
> >
> >> The artifacts are simple copies of the output files in the workspace.
> >> If needed, we can add a copy and rename action to the 'release' job
> >> and create artifacts that fit your needs...
> >>
> >> EdB
> >>
> >
> > Isn't the filename driven off of a properties file?  At least, that is
> how
> > the Installer works.  Is there any reason why we are calling them 4.10
> > artifacts still?
> >
> > Om
> >
> >
> >>
> >>
> >>
> >> On Wed, Sep 4, 2013 at 7:01 PM, OmPrakash Muppirala
> >> <bi...@gmail.com> wrote:
> >> > On Tue, Sep 3, 2013 at 5:54 PM, Justin Mclean <
> justin@classsoftware.com
> >> >wrote:
> >> >
> >> >> HI,
> >> >>
> >> >> > The tracking is based on the Flex version.  We dont make a
> distinction
> >> >> > between the nightly vs. released sdk.  We should probably bump up
> the
> >> >> > version number in our develop branch to start tracking the
> nightlies.
> >> >>
> >> >> Were is it pickup up the version from? The develop branch should have
> >> all
> >> >> versions at 4.11.
> >> >>
> >> >>
> >> > It is picked up from the file name.  The artifacts are still has
> 4.10.0
> >> in
> >> > their file names:
> >> >
> >>
> https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifact/out/
> >> >
> >> > Thanks,
> >> > Om
> >> >
> >> >
> >> >> Thanks,
> >> >> Justin
> >>
> >>
> >>
> >> --
> >> Ix Multimedia Software
> >>
> >> Jan Luykenstraat 27
> >> 3521 VB Utrecht
> >>
> >> T. 06-51952295
> >> I. www.ixsoftware.nl
> >>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>

Re: Nighly builds and releases

Posted by Erik de Bruin <er...@ixsoftware.nl>.
The job that creates the artifacts is simply running "ant super-clean
release create-md5". It is not explicitly changing the filenames. I
guess there is still something/somewhere left to update to "4.11.0"?

EdB



On Wed, Sep 4, 2013 at 7:25 PM, OmPrakash Muppirala
<bi...@gmail.com> wrote:
> On Wed, Sep 4, 2013 at 10:14 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>
>> The artifacts are simple copies of the output files in the workspace.
>> If needed, we can add a copy and rename action to the 'release' job
>> and create artifacts that fit your needs...
>>
>> EdB
>>
>
> Isn't the filename driven off of a properties file?  At least, that is how
> the Installer works.  Is there any reason why we are calling them 4.10
> artifacts still?
>
> Om
>
>
>>
>>
>>
>> On Wed, Sep 4, 2013 at 7:01 PM, OmPrakash Muppirala
>> <bi...@gmail.com> wrote:
>> > On Tue, Sep 3, 2013 at 5:54 PM, Justin Mclean <justin@classsoftware.com
>> >wrote:
>> >
>> >> HI,
>> >>
>> >> > The tracking is based on the Flex version.  We dont make a distinction
>> >> > between the nightly vs. released sdk.  We should probably bump up the
>> >> > version number in our develop branch to start tracking the nightlies.
>> >>
>> >> Were is it pickup up the version from? The develop branch should have
>> all
>> >> versions at 4.11.
>> >>
>> >>
>> > It is picked up from the file name.  The artifacts are still has 4.10.0
>> in
>> > their file names:
>> >
>> https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifact/out/
>> >
>> > Thanks,
>> > Om
>> >
>> >
>> >> Thanks,
>> >> Justin
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Nighly builds and releases

Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Wed, Sep 4, 2013 at 10:14 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> The artifacts are simple copies of the output files in the workspace.
> If needed, we can add a copy and rename action to the 'release' job
> and create artifacts that fit your needs...
>
> EdB
>

Isn't the filename driven off of a properties file?  At least, that is how
the Installer works.  Is there any reason why we are calling them 4.10
artifacts still?

Om


>
>
>
> On Wed, Sep 4, 2013 at 7:01 PM, OmPrakash Muppirala
> <bi...@gmail.com> wrote:
> > On Tue, Sep 3, 2013 at 5:54 PM, Justin Mclean <justin@classsoftware.com
> >wrote:
> >
> >> HI,
> >>
> >> > The tracking is based on the Flex version.  We dont make a distinction
> >> > between the nightly vs. released sdk.  We should probably bump up the
> >> > version number in our develop branch to start tracking the nightlies.
> >>
> >> Were is it pickup up the version from? The develop branch should have
> all
> >> versions at 4.11.
> >>
> >>
> > It is picked up from the file name.  The artifacts are still has 4.10.0
> in
> > their file names:
> >
> https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifact/out/
> >
> > Thanks,
> > Om
> >
> >
> >> Thanks,
> >> Justin
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>

Re: Nighly builds and releases

Posted by Erik de Bruin <er...@ixsoftware.nl>.
The artifacts are simple copies of the output files in the workspace.
If needed, we can add a copy and rename action to the 'release' job
and create artifacts that fit your needs...

EdB



On Wed, Sep 4, 2013 at 7:01 PM, OmPrakash Muppirala
<bi...@gmail.com> wrote:
> On Tue, Sep 3, 2013 at 5:54 PM, Justin Mclean <ju...@classsoftware.com>wrote:
>
>> HI,
>>
>> > The tracking is based on the Flex version.  We dont make a distinction
>> > between the nightly vs. released sdk.  We should probably bump up the
>> > version number in our develop branch to start tracking the nightlies.
>>
>> Were is it pickup up the version from? The develop branch should have all
>> versions at 4.11.
>>
>>
> It is picked up from the file name.  The artifacts are still has 4.10.0 in
> their file names:
> https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifact/out/
>
> Thanks,
> Om
>
>
>> Thanks,
>> Justin



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Nighly builds and releases

Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Tue, Sep 3, 2013 at 5:54 PM, Justin Mclean <ju...@classsoftware.com>wrote:

> HI,
>
> > The tracking is based on the Flex version.  We dont make a distinction
> > between the nightly vs. released sdk.  We should probably bump up the
> > version number in our develop branch to start tracking the nightlies.
>
> Were is it pickup up the version from? The develop branch should have all
> versions at 4.11.
>
>
It is picked up from the file name.  The artifacts are still has 4.10.0 in
their file names:
https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifact/out/

Thanks,
Om


> Thanks,
> Justin

Re: Nighly builds and releases

Posted by Justin Mclean <ju...@classsoftware.com>.
HI,

> The tracking is based on the Flex version.  We dont make a distinction
> between the nightly vs. released sdk.  We should probably bump up the
> version number in our develop branch to start tracking the nightlies.

Were is it pickup up the version from? The develop branch should have all versions at 4.11.

Thanks,
Justin

Re: Nighly builds and releases

Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Tue, Sep 3, 2013 at 5:30 PM, Justin Mclean <ju...@classsoftware.com>wrote:

> Hi,
>
> Also noticed we don't seem to be tracking nightly build installs either?
>
> Justin
>

The tracking is based on the Flex version.  We dont make a distinction
between the nightly vs. released sdk.  We should probably bump up the
version number in our develop branch to start tracking the nightlies.

Thanks,
Om

Re: Nighly builds and releases

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

Also noticed we don't seem to be tracking nightly build installs either?

Justin

Re: Nighly builds and releases

Posted by Alex Harui <ah...@adobe.com>.

On 9/3/13 5:09 PM, "Justin Mclean" <ju...@gmail.com> wrote:

>Hi,
>
>An issue just come up on the incubator general list about nightly builds.
>[1]
>
>The installer lets you download the nightly build, and while convenient
>it looks like it's actually against Apache release guidelines [2]:
>"If the general public is being instructed to download a package, then
>that package has been released. Each PMC must obey the ASF requirements
>on approving any release."
>and
>" Do not include any links on the project website that might encourage
>non-developers to download and use nightly builds, snapshots, release
>candidates, or any other similar package."
>
>We probably need to remove that from the installer. Perhaps an
>alternative is  it only show via a command line flag or "I am a SDK
>developer" check box with a big disclaimer about it not being an official
>release etc etc
I don't know that we are "encouraging" folks to use it any more than the
various nightly build pages for several Apache projects. Google "Apache
Nightly".  What VXQuery was doing is having its default installation
instructions pull right from SVN.

A simpler 'fix' might be to rename the "Flex SDK Nightly" to "Flex SDK
Nightly (unsupported)", then we are clearly not "encouraging".  In the
next release, we can add an alert that warns you even more, but I think
the name change might be good enough for now.

-Alex