| Re: [sapphire-dev] Beyond 0.5 release |
0.6 would be just fine for me. I will be releasing my adopter product before 0.6 however, for now I can do my own action that relies on GEF apis for now and can remove it for 0.6.0. I'll open enhancement request for finding diagram parts action.GOn Sat, Jun 16, 2012 at 7:20 AM, Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx> wrote:
Greg,
This sounds like a really useful feature and I would be interested in having both parts of this in Sapphire. I can see linking this to Ctrl+F “Find” action. In terms of justifying putting this into 0.5.1, does adopter release schedule preclude the use of the 0.6 release?
Thanks,
- Konstantin
From: sapphire-dev-bounces@xxxxxxxxxxx [mailto:sapphire-dev-bounces@xxxxxxxxxxx] On Behalf Of Greg Amerson
Sent: Friday, June 15, 2012 3:44 PM
To: Sapphire project
Subject: Re: [sapphire-dev] Beyond 0.5 release
Sure that makes sense. The reason I'm asking is in my adopter product, I want to add a "quick-outline" type feature where you can open a popup dialog, type into a search box to filter nodes/connection labels and then when user selects one the diagram editor selects and reveals that node (useful for really large diagrams, 100+ diagram parts). So I was able to implement this for my editor, but I had to directly use GEF apis to do it. I was wondering if this could be a new feature in 0.5.1 to have a new API added to Sapphire diagram editor to "selectAndReveal" diagram parts in an editor so adopters can stay clean of GEF dependencies. If you are interested in me contributing the new API I can open a enhancement request. Also if you are interested in a similar feature for sapphire in general I could contribute that as well. Maybe just the API enhancement for 0.5.1 and if you are interested in me contributing the "quick-outline" type action that could go into 0.6.0?
G
On Sat, Jun 16, 2012 at 12:08 AM, Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx> wrote:
In general, new features should go into the 0.6.0 release, but I am willing to consider exceptions if sufficiently justified and if the work fits within the key 0.5.x line rule of full backwards compatibility with 0.5.0 release.
- Konstantin
From: sapphire-dev-bounces@xxxxxxxxxxx [mailto:sapphire-dev-bounces@xxxxxxxxxxx] On Behalf Of Greg Amerson
Sent: Friday, June 15, 2012 1:45 AM
To: Sapphire project
Subject: Re: [sapphire-dev] Beyond 0.5 release
Thanks for that, that will be useful for me to add to my integration build.
Also, would I be able to contribute new feature patches to a 0.5.1 release? Or would new patches need to come to wait 0.6.0?
On Fri, Jun 15, 2012 at 2:27 PM, Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx> wrote:
Do you mean the update site for the 0.5 release? If so, the release date is 6-27, which is controlled by Juno release train and we cannot make it official sooner. In the meantime, you can reference the RC4 repository:
http://download.eclipse.org/sapphire/0.5.0.RC4/repository
Thanks,
- Konstantin
From: sapphire-dev-bounces@xxxxxxxxxxx [mailto:sapphire-dev-bounces@xxxxxxxxxxx] On Behalf Of Greg Amerson
Sent: Thursday, June 14, 2012 6:51 PM
To: Sapphire project
Subject: Re: [sapphire-dev] Beyond 0.5 release
Do you have an estimate of when the 0.5.x update site be uploaded to downloads.eclipse.org/sapphire/0.5.x?
On Fri, Jun 15, 2012 at 4:17 AM, Konstantin Komissarchik <konstantin.komissarchik@xxxxxxxxxx> wrote:
The Hudson job for 0.6.x is now operational.
https://hudson.eclipse.org/hudson/job/sapphire-0.6.x
Thanks,
- Konstantin
From: Konstantin Komissarchik [mailto:konstantin.komissarchik@xxxxxxxxxx]
Sent: Thursday, June 14, 2012 12:50 PM
To: 'Sapphire project'
Subject: RE: [sapphire-dev] Beyond 0.5 release
Given this issue, I don’t think we can afford to wait a week before branching. We need to get started on 0.5.1 as soon as possible. To that end, I have created R_0_5_x branch and have versioned it as 0.5.1. HEAD is now versioned as 0.6.0. Both R_0_5_x and HEAD are now open for work in their respective releases.
In terms of Hudson coverage, the existing job that we’ve been using for 0.5 is now covering the 0.5.1 release.
https://hudson.eclipse.org/hudson/job/sapphire-0.5.x
I have request a new job to be created for 0.6.x line, but that hasn’t happened yet.
Thanks,
- Konstantin
From: sapphire-dev-bounces@xxxxxxxxxxx [mailto:sapphire-dev-bounces@xxxxxxxxxxx] On Behalf Of Konstantin Komissarchik
Sent: Thursday, June 14, 2012 11:37 AM
To: 'Sapphire project'
Subject: Re: [sapphire-dev] Beyond 0.5 release
I just found a major problem in the 0.5 release that will likely trigger a need for an early 0.5.1 release…
Base property services can be hidden by deriving property
https://bugs.eclipse.org/bugs/show_bug.cgi?id=382660
- Konstantin
From: Konstantin Komissarchik [mailto:konstantin.komissarchik@xxxxxxxxxx]
Sent: Wednesday, June 13, 2012 4:23 PM
To: 'Sapphire project'
Subject: Beyond 0.5 release
With 0.5 wrapped up and practically out of the door, we have a few things to go over…
1. In order to allow for an emergency respin of 0.5 prompted by the overall Juno release train need, we will go “hands off CVS” for about a week. So no commits until you hear from me. For now, stash any changes as patches attached to relevant bugs. Once I know that it is safe to do so, I will create 0.5.x branch for 0.5.1 work and HEAD will be open for 0.6 work.
2. The 0.5.1 release will be our Juno SR1 contribution. Bug fixes only. Absolutely nothing that would require any sort of migration steps or be otherwise incompatible with 0.5 release. To be released with the rest of Juno SR1 on September 28th. If we find a major issue in 0.5, we made elect to ship 0.5.1 early and create 0.5.2 to align with Juno SR1.
3. The 0.6 release will be our next feature release. It isn’t going to be tied to any release train, so the date is ours to set, but I’d like to return to quarterly feature releases, so let’s use September 28th as the working date. Same as 0.5.1 release.
4. Once dust settles after Juno release (about first or second week of July), we will do our CVS to git conversion. If you are still thinking “what’s git?”, now would be the time to find out.
Let me know if there are any questions.
- Konstantin
_______________________________________________
sapphire-dev mailing list
sapphire-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/sapphire-dev
--
Greg Amerson
Liferay, Inc.
---
8-9 October 2012 | Liferay North America Symposium | liferay.com/northamerica2012
16-17 October 2012 | Liferay Europe Symposium | liferay.com/europe2012
24-25 October 2012 | Liferay Spain Symposium | liferay.com/spain2012
_______________________________________________
sapphire-dev mailing list
sapphire-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/sapphire-dev
--
Greg Amerson
Liferay, Inc.
---
8-9 October 2012 | Liferay North America Symposium | liferay.com/northamerica2012
16-17 October 2012 | Liferay Europe Symposium | liferay.com/europe2012
24-25 October 2012 | Liferay Spain Symposium | liferay.com/spain2012
_______________________________________________
sapphire-dev mailing list
sapphire-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/sapphire-dev
--
Greg Amerson
Liferay, Inc.
---
8-9 October 2012 | Liferay North America Symposium | liferay.com/northamerica2012
16-17 October 2012 | Liferay Europe Symposium | liferay.com/europe2012
24-25 October 2012 | Liferay Spain Symposium | liferay.com/spain2012
_______________________________________________
sapphire-dev mailing list
sapphire-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/sapphire-dev
--Greg AmersonLiferay, Inc.---
8-9 October 2012 | Liferay North America Symposium | liferay.com/northamerica2012
16-17 October 2012 | Liferay Europe Symposium | liferay.com/europe2012
24-25 October 2012 | Liferay Spain Symposium | liferay.com/spain2012