On 06/06/2016 06:32 AM, Max Rydahl Andersen wrote:
On 1 Jun 2016, at 17:26, Jean-Francois Maury wrote:

https://issues.jboss.org/browse/JBIDE-22446

it is not in current sprint because we decided to be clean and not to add
issues after the sprint is started😉

This does not make sense - the GA release was part of this sprint scope.

I've marked this for 4.4.0.Final with respin-a label so we can keep track of
what we've found of issues.

Max, there is another issue [1] (linked to this one) for releasing and including  openshift-restclient-java into devstudio 10.0.0.GA
That issue was resolved before our codefreeze.
The issues is mentioned by Jeff above [2] is actually about some automated detection/test if we include some snapshot artefacts instead of released versions.
This detection/test itself is not a blocker for GA and it wasn't planed for this sprint. So I'm going to add some clarification to the jira and move it to backlog.

[1] https://issues.jboss.org/browse/JBIDE-22444
[2] https://issues.jboss.org/browse/JBIDE-22446

Thanks.


/max


Jeff

On Wed, Jun 1, 2016 at 3:28 PM, Alexey Kazakov <alkazako@redhat.com> wrote:



On 06/01/2016 03:17 AM, Jean-Francois Maury wrote:

Hello,

just as a remainder. We are still building with a SNAPSHOT version of the
Openshift REST Java Client. When do we think this will be fixed ?


Do we have it in JIRA? I can't find it in the current sprint.

Thanks.



Jeff

On Tue, May 31, 2016 at 11:17 PM, Nick Boldt <nboldt@redhat.com> wrote:

* Target platform will be updated ASAP to move to *Neon.0.RC2*. Watch
for email updates.

* Task JIRAs will be sent out tomorrow, and you will *create a branch &
update your root poms* to use the latest parent pom.

* Code freeze for all projects' jbosstools-4.4.x branches will start *Thursday
at 2pm PST / 5pm EST / 11pm CST*.

(We're back to the old way of branching and updating root & parent poms.
Did you enjoy the lightweight approach? Tell us!)

* *build will run Thursday night* and be copied to /staging/ on Friday
morning EST.

* *From Fri until the end of the sprint, you should *NOT* push anything
into the jbosstools-4.4.x stable branch unless it's a blocker fix approved
by Alexey*

** *master branch is open for new work once you've created your
jbosstools-4.4.x branch.

----

Looking ahead...

We will be moving from Neon.0.RC2 to RC4 next week as soon as the *RC4
bits are available, starting on Jun 8 or 9*.

There will be a *respin on Jun 10* to move up to RC4. This will
hopefully the LAST build before *GA on June 14.*

I hope to go rock climbing at a place call Bon Echo the weekend of June
11-12. So... please, if you need to cause/find/fix blockers, please do so
before Jun 8 so they can be fixed at the same time as the TP update on Jun
9 -- thanks!

--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com



--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com

_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev




_______________________________________________
jbosstools-dev mailing listjbosstools-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbosstools-dev



_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev



_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen