Re: [polymer-dev] Status update on the .08 release?

256 views
Skip to first unread message

Eric Bidelman

unread,
Feb 17, 2015, 12:54:49 PM2/17/15
to Daniel Elebash, polym...@googlegroups.com, tjsa...@google.com
+Taylor

On Sun Feb 15 2015 at 2:49:53 AM Daniel Elebash <danel...@hotmail.com> wrote:
Any new time frame on the .08 release since this release seems to be a major change, just would like to get an update on expected release date.

Thanks.

Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/96f5cf37-5cc8-46ae-a12e-698e8669bd57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Taylor Savage

unread,
Feb 17, 2015, 10:24:03 PM2/17/15
to Eric Bidelman, Daniel Elebash, polym...@googlegroups.com
Hey Daniel,

The 0.8 release of the core library is still actively being worked on - you can check out its progress in the 0.8-preview branch of Polymer/polymer, which is updated very frequently. The primer is especially useful in seeing what 0.8 will include, and how it differs from 0.5.

We're being very cautious in when we're tagging the library as "released" - our aim is to make 0.5 to 0.8 the last major "port," and minimize the upgrade difficulty from 0.8 to the eventual "production-ready" 1.0. That said, we're looking to have the 0.8 feature set locked and API stabilized by next month, and will tag it then.

Hope that helps!
Taylor 

Carl Youngblood

unread,
Feb 18, 2015, 10:59:27 AM2/18/15
to polym...@googlegroups.com, ebi...@gmail.com, danel...@hotmail.com
Taylor, when you say the feature set will be locked and the API stabilized, does that mean you will also update all the core and paper elements to the new API? One of the biggest challenges for us is that kicking the tires on the new API requires us to manually fork all the elements we're using and update them to the new syntax.

Thanks,
Carl


On Tuesday, February 17, 2015 at 8:24:03 PM UTC-7, Taylor Savage wrote:
Hey Daniel,

The 0.8 release of the core library is still actively being worked on - you can check out its progress in the 0.8-preview branch of Polymer/polymer, which is updated very frequently. The primer is especially useful in seeing what 0.8 will include, and how it differs from 0.5.

We're being very cautious in when we're tagging the library as "released" - our aim is to make 0.5 to 0.8 the last major "port," and minimize the upgrade difficulty from 0.8 to the eventual "production-ready" 1.0. That said, we're looking to have the 0.8 feature set locked and API stabilized by next month, and will tag it then.

Hope that helps!
Taylor 
On Tue, Feb 17, 2015 at 9:54 AM, Eric Bidelman <ebi...@gmail.com> wrote:
+Taylor


On Sun Feb 15 2015 at 2:49:53 AM Daniel Elebash <danel...@hotmail.com> wrote:
Any new time frame on the .08 release since this release seems to be a major change, just would like to get an update on expected release date.

Thanks.

Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev...@googlegroups.com.

Taylor Savage

unread,
Feb 18, 2015, 8:03:43 PM2/18/15
to Carl Youngblood, polym...@googlegroups.com, Eric Bidelman, Daniel Elebash
Hey Carl,

We're aiming for the elements and the library to be versioned independently beginning with 0.8 - we're looking to treat the element sets like true standalone product lines with their own roadmaps and with a dependency on Polymer. We're hoping to have the most used subset of the elements ported by the release, but we're threading the needle a bit between hitting API stability, porting elements, and tagging the release.  We don't want to gate the release of the library on the readiness of all the core and paper elements, so some will necessarily slightly lag behind, but there will be a good chunk ready to go on release-day.

Taylor

Reply all
Reply to author
Forward
0 new messages