You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Alex Harui <ah...@adobe.com> on 2012/12/04 19:27:34 UTC

Next SDK Release Timing

Hi,

We’ve had a couple of new locales and many bug fixes submitted that have been sitting around for a while now.  It would be great to get them out the door, but with the impending graduation (we hope), the timing becomes tricky.

I’m not sure we can get it together to get packages approved by both us and the IPMC before the next board meeting.  If we wait until after graduation, there might be a further delay as Infra transitions all of our web and source information to new URLs.

I’m leaning towards waiting, but I feel bad for folks who are waiting to see their work get out the door.  This will truly separate the Apache Flex SDK from the Adobe Flex SDK because non-Adobe code will finally be released!

Thoughts?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Next SDK Release Timing

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


On 12/4/12 2:41 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:

> Hi,
> 
>> This sounds reasonable to me.  All we need is a volunteer to be the release
>> manager.
> 
> 
> I'm willing to give it a go. (I have keys for signing the binaries etc etc)
> My time is a little bit limited at the moment so would appreciate some help.
> 
> Thanks,
> Justin
Excellent!  What kind of help are you looking for?  I'll certainly try to
answer questions and review RCs.

I just scanned all checkins since the last release and don't see anything
that needs to be pulled out, so I would say a straight up branch should be
the starting point.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


Re: Next SDK Release Timing

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

> This sounds reasonable to me.  All we need is a volunteer to be the release
> manager.


I'm willing to give it a go. (I have keys for signing the binaries etc etc)  My time is a little bit limited at the moment so would appreciate some help.

Thanks,
Justin

Re: Next SDK Release Timing

Posted by Alex Harui <ah...@adobe.com>.
This sounds reasonable to me.  All we need is a volunteer to be the release
manager.  I would rather not be it.


On 12/4/12 12:26 PM, "Greg Reddin" <gr...@gmail.com> wrote:

> On Tue, Dec 4, 2012 at 12:27 PM, Alex Harui <ah...@adobe.com> wrote:
> 
>> I¹m leaning towards waiting, but I feel bad for folks who are waiting to
>> see their work get out the door.  This will truly separate the Apache Flex
>> SDK from the Adobe Flex SDK because non-Adobe code will finally be released!
>> 
> 
> I think we should go ahead and start the process and see if it finishes
> before or after graduation. I'd suggest we wait till after graduation to
> vote for the release because we can then skip the step of having the vote
> on general@. It's true that it may take some time to get the website
> migrated, but actually, the dist directories and mirrors that will contain
> the release should be available sooner (or already there). So worst case (I
> think) is that we've voted on a release and pushed it to the mirrors, and
> announced it on the list, but the website is behind.
> 
> Regarding the arduous release process, it will be a bit less arduous once
> we're out of the incubator and we'll have more control over the process.
> 
> I expect that the board will approve graduation. I'm not putting words in
> their mouths, but I can't think of a situation where a resolution has been
> passed through the incubator and the board has rejected it. We should be
> prepared for what to do if they reject it, but I will be very surprised if
> they do.
> 
> Greg


-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


Re: Next SDK Release Timing

Posted by Greg Reddin <gr...@gmail.com>.
On Tue, Dec 4, 2012 at 12:27 PM, Alex Harui <ah...@adobe.com> wrote:

> I’m leaning towards waiting, but I feel bad for folks who are waiting to
> see their work get out the door.  This will truly separate the Apache Flex
> SDK from the Adobe Flex SDK because non-Adobe code will finally be released!
>

I think we should go ahead and start the process and see if it finishes
before or after graduation. I'd suggest we wait till after graduation to
vote for the release because we can then skip the step of having the vote
on general@. It's true that it may take some time to get the website
migrated, but actually, the dist directories and mirrors that will contain
the release should be available sooner (or already there). So worst case (I
think) is that we've voted on a release and pushed it to the mirrors, and
announced it on the list, but the website is behind.

Regarding the arduous release process, it will be a bit less arduous once
we're out of the incubator and we'll have more control over the process.

I expect that the board will approve graduation. I'm not putting words in
their mouths, but I can't think of a situation where a resolution has been
passed through the incubator and the board has rejected it. We should be
prepared for what to do if they reject it, but I will be very surprised if
they do.

Greg

Re: Next SDK Release Timing

Posted by Om <bi...@gmail.com>.
That said, there is nothing stopping us from preparing for a release before
we graduate.  The major difference would be the "incubating" tag for the
release and an additional 72 hour (minimum) voting period in the IPMC.  If
folks feel like we can pull it off, they should take it on.

Lets also keep in mind that folks will start disappearing for year end
vacations closer to the end of the year.  Getting votes might not be that
easy.

Thanks,
Om

On Tue, Dec 4, 2012 at 11:41 AM, Omar Gonzalez <om...@gmail.com>wrote:

> On Tue, Dec 4, 2012 at 11:32 AM, Justin Mclean <justin@classsoftware.com
> >wrote:
>
> > Hi,
> >
> > Release early and often should be the case, we are way overdue for a
> > release IMO.
> >
> > Justin
>
>
> While I generally agree with this statement it is predicated on the
> assumption that releasing often can happen in an efficient and timely
> manner. Given the pending graduation and moving of repositories I would
> place my vote for waiting until after the logistics of graduation are
> completed.
>
> -omar
>

Re: Next SDK Release Timing

Posted by Om <bi...@gmail.com>.
On Tue, Dec 4, 2012 at 11:49 AM, Justin Mclean <ju...@classsoftware.com>wrote:

> Hi,
>
> > Given the pending graduation
> Which we'll find out about 19th Dec at minimum.
>
> > and moving of repositories
> Which as far as I can see still up in the air and there's several
> unanswered questions about and may be at a minimum a few months off.
> (Unless I've missed some news here)
>
> Do we really want to wait and 2-3 months before starting on a new release?
>
>
No, we shouldnt.  We need to get into a cadence of releasing early and
often.  This is not going to happen because we suddenly decide to.


> Making a new release should be a fairly straight forward process, if it
> not IMO we're not doing it right. There are bug fixes and new functionality
> added to the SDK that would be useful to users of the SDK now.
>

I agree that we are not doing it right.  We should have made a second
release months ago.  But as I said, getting in to a release cadence will
take some time.


>
> Thanks,
> Justin

Re: Next SDK Release Timing

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

> I was expecting they would probably just move our existing repository as is
> to an SVN url that is not incubating.
I can't see that should cause too many issues as the release branch we're working on would also be moved over.

Thanks,
Justin

Re: Next SDK Release Timing

Posted by Omar Gonzalez <om...@gmail.com>.
On Tue, Dec 4, 2012 at 11:49 AM, Justin Mclean <ju...@classsoftware.com>wrote:

> Hi,
>
> > Given the pending graduation
> Which we'll find out about 19th Dec at minimum.
>
> > and moving of repositories
> Which as far as I can see still up in the air and there's several
> unanswered questions about and may be at a minimum a few months off.
> (Unless I've missed some news here)
>

I was expecting they would probably just move our existing repository as is
to an SVN url that is not incubating. I wasn't expecting them to do a move
to Git at the same time.


>
> Do we really want to wait and 2-3 months before starting on a new release?
>
> Making a new release should be a fairly straight forward process, if it
> not IMO we're not doing it right. There are bug fixes and new functionality
> added to the SDK that would be useful to users of the SDK now.
>
> Thanks,
> Justin


Yea I agree with most of this, 2-3 months wouldn't be nice to wait if we
have things that could go out now. Just based on what I remember went
through for the first release, like Carol, I'm not sure we have the process
down to being able to do it over the next 2 weeks which is when we'll know
about graduation. I'm unsure of how long it takes them to do the transition
to non incubating URLs. Right now I think Carol's been the only 'build
master'.

Is there a way we can maybe start to prepare it and see if we can make it
before the 19th and if we can't then put it off until after the changes are
complete?

-omar

Re: Next SDK Release Timing

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

> Given the pending graduation
Which we'll find out about 19th Dec at minimum.

> and moving of repositories
Which as far as I can see still up in the air and there's several unanswered questions about and may be at a minimum a few months off. (Unless I've missed some news here)

Do we really want to wait and 2-3 months before starting on a new release?

Making a new release should be a fairly straight forward process, if it not IMO we're not doing it right. There are bug fixes and new functionality added to the SDK that would be useful to users of the SDK now.

Thanks,
Justin

Re: Next SDK Release Timing

Posted by Omar Gonzalez <om...@gmail.com>.
On Tue, Dec 4, 2012 at 11:32 AM, Justin Mclean <ju...@classsoftware.com>wrote:

> Hi,
>
> Release early and often should be the case, we are way overdue for a
> release IMO.
>
> Justin


While I generally agree with this statement it is predicated on the
assumption that releasing often can happen in an efficient and timely
manner. Given the pending graduation and moving of repositories I would
place my vote for waiting until after the logistics of graduation are
completed.

-omar

RE: Next SDK Release Timing

Posted by "Guthmann, Scott" <sg...@on3solutions.com>.
> Hi,
> Release early and often should be the case, we are way overdue for a release IMO.
> Justin
Justin is correct. Part of the graduation criteria is to be a self-sustaining community. Concerning ourselves with whether mentors approve or disapprove of our project provides evidence that we aren't quite free of our need to get their guidance & feedback. By continuing to help ourselves, scratching our own itches, and moving forward, we show that we are ready. I think that one of the criteria we are being evaluated on is: Does the project have an diverse, creative, & unstoppable momentum? If so, then we show that our project is ready for graduation, IMHO.

Re: Next SDK Release Timing

Posted by Carol Frampton <cf...@adobe.com>.

On 12/4/12 3 :03PM, "Om" <bi...@gmail.com> wrote:

>On Tue, Dec 4, 2012 at 12:01 PM, Justin Mclean
><ju...@classsoftware.com>wrote:
>
>> Hi,
>>
>> > I don't disagree but I think a release without "-incubating" in the
>>title
>> > would be a good thing.
>> Nothing stopping us from making another release after graduation and
>>it's
>> not certain that we will graduate at the next board meeting (although I
>> hope we do).
>>
>> Does anything here need to be updated?
>> https://cwiki.apache.org/confluence/display/FLEX/Release+Guide
>>
>>
>This document looks good.  It helped me a lot with the Installer release.
> The actual scripts to build the SDK might have changed because of the new
>additions.

I spent some time on the "SDK" portion of the kit a couple of weeks ago.
There has been "script rot" in the few months since the last release.

I think it is highly desirable that the installer and the sdk are released
together.  Last I knew the installer needs a bit of work, as well as
updating the version numbers, so if if the SDK could release tomorrow the
installer isn't ready.

Are we going to release any of the maven stuff?

There is a build/build_release.sh script that can build a release on a
mac.  It assumes it is run from the build directory.  I threw the script
together to record the commands I had been typing so it is not
bullet-proof.

Carol



Re: Next SDK Release Timing

Posted by Om <bi...@gmail.com>.
On Tue, Dec 4, 2012 at 12:01 PM, Justin Mclean <ju...@classsoftware.com>wrote:

> Hi,
>
> > I don't disagree but I think a release without "-incubating" in the title
> > would be a good thing.
> Nothing stopping us from making another release after graduation and it's
> not certain that we will graduate at the next board meeting (although I
> hope we do).
>
> Does anything here need to be updated?
> https://cwiki.apache.org/confluence/display/FLEX/Release+Guide
>
>
This document looks good.  It helped me a lot with the Installer release.
 The actual scripts to build the SDK might have changed because of the new
additions.


> Thanks,
> Justin
>
>

Re: Next SDK Release Timing

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

> I don't disagree but I think a release without "-incubating" in the title
> would be a good thing.
Nothing stopping us from making another release after graduation and it's not certain that we will graduate at the next board meeting (although I hope we do).

Does anything here need to be updated?
https://cwiki.apache.org/confluence/display/FLEX/Release+Guide

Thanks,
Justin


Re: Next SDK Release Timing

Posted by Carol Frampton <cf...@adobe.com>.

On 12/4/12 2 :32PM, "Justin Mclean" <ju...@classsoftware.com> wrote:

>Hi,
>
>Release early and often should be the case, we are way overdue for a
>release IMO.

I don't disagree but I think a release without "-incubating" in the title
would be a good thing.  I also don't think we can pull off a release in
the next two weeks and if we miss that the kit has to be renamed and some
of the files removed/edited.  I am specifically thinking of the DISCLAIMER
file but I'm sure the README and some other files need edits as well.

As far as the installer goes, that work should be done now/soon since I
think we can/should release in January and it would be great if the
installer was ready with the SDK.

And when we release "what all" are we releasing other than the installer
and the sdk?

Carol


Re: Next SDK Release Timing

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

Release early and often should be the case, we are way overdue for a release IMO.

Justin

Re: Next SDK Release Timing

Posted by Om <bi...@gmail.com>.
My guess is that it will take at least a month to sort out the code, build,
test and have the artifacts prepared for a release.  Also, we want to make
changes to the Installer (ex. removing download of TLF since it is part of
the SDK now)

I think it would be better if we wait instead of trying to push another
release before we graduate.

Thanks,
Om

On Tue, Dec 4, 2012 at 10:42 AM, Jun Heider <ju...@realeyes.com> wrote:

>
> On Dec 4, 2012, at 11:27 AM, Alex Harui wrote:
> > I’m leaning towards waiting, but I feel bad for folks who are waiting to
> see their work get out the door.  This will truly separate the Apache Flex
> SDK from the Adobe Flex SDK because non-Adobe code will finally be released!
> >
> > Thoughts?
>
> Good things come to those who wait is my thought.

Re: Next SDK Release Timing

Posted by Carlos Rovira <ca...@codeoscopic.com>.
I think is better to wait.

just my 2ctns :)

2012/12/4 Jun Heider <ju...@realeyes.com>

>
> On Dec 4, 2012, at 11:27 AM, Alex Harui wrote:
> > I’m leaning towards waiting, but I feel bad for folks who are waiting to
> see their work get out the door.  This will truly separate the Apache Flex
> SDK from the Adobe Flex SDK because non-Adobe code will finally be released!
> >
> > Thoughts?
>
> Good things come to those who wait is my thought.




-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 94 80 80
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es

Re: Next SDK Release Timing

Posted by Jun Heider <ju...@realeyes.com>.
On Dec 4, 2012, at 11:27 AM, Alex Harui wrote:
> I’m leaning towards waiting, but I feel bad for folks who are waiting to see their work get out the door.  This will truly separate the Apache Flex SDK from the Adobe Flex SDK because non-Adobe code will finally be released!
> 
> Thoughts?

Good things come to those who wait is my thought.

Re: Next SDK Release Timing

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

>  It will provide a consistent spot for developers to go to for the future.  Vice once we state there is a new release and they go to the incubation page... then in the future we change to the permanent url's.
I believe the old URL will redirect to the new URLs no don't see that as a big issue.

Thanks,
Justin

RE: Next SDK Release Timing

Posted by Kessler CTR Mark J <ma...@usmc.mil>.
+1 for waiting this one time.  But then more frequent future releases.

   While I like to see more frequent releases, I prefer this next one to wait until the url's / dust settles.  It will provide a consistent spot for developers to go to for the future.  Vice once we state there is a new release and they go to the incubation page... then in the future we change to the permanent url's.



-Mark

-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com] 
Sent: Tuesday, December 04, 2012 13:28
To: flex-dev@incubator.apache.org
Subject: Next SDK Release Timing

Hi,

We've had a couple of new locales and many bug fixes submitted that have been sitting around for a while now.  It would be great to get them out the door, but with the impending graduation (we hope), the timing becomes tricky.

I'm not sure we can get it together to get packages approved by both us and the IPMC before the next board meeting.  If we wait until after graduation, there might be a further delay as Infra transitions all of our web and source information to new URLs.

I'm leaning towards waiting, but I feel bad for folks who are waiting to see their work get out the door.  This will truly separate the Apache Flex SDK from the Adobe Flex SDK because non-Adobe code will finally be released!

Thoughts?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui