Reminder, we have code freeze for JBT 4.2 / JBDS 8 Alpha1 this Thursday,
Dec 05. (It was postponed from last week due to holiday conflicts & PTO.)
If you will be *unable to code freeze on time*, please respond here
ASAP. Otherwise, I will send the usual Task JIRA emails out tomorrow
night so everyone can freeze and branch on Thursday in your time zone.
---
FYI, there are compilation failures for these projects:
* Forge - job set to use Luna TP and Maven 3.1.0. Should it be 3.1.1?
* Hibernate - job set to use Kepler TP. Should it be Luna?
---
Also seeing build failures (tests or timeouts) for these projects, but
am respinning today to see if they were transient Jenkins problems not
due to github sources:
* Base
* Central
* JavaEE
* JST
* Server
* Webservices
Thanks,
Nick
On 11/28/2013 06:40 AM, Max Rydahl Andersen wrote:
On Wed, Nov 27, 2013 at 01:14:56PM -0500, Nick Boldt wrote:
> Thursday the 5th works too - gives people a bit more time to churn out
> some alpha content and for Hibernate to solve is compilation issues.
>
> Whether it's Monday Dec 2 or Thursday Dec 5, either way the release
> would be like this:
>
> Mon Dec 02 (or 05) :: JBDS 8 Alpha1 Code Freeze/Branch
> Mon Dec 09 :: JBDS 8 Alpha1 QE start (earlier if possible)
> Fri Dec 13 :: JBDS 8 Alpha1 release to EA/dev milestone
>
> How about we aim for Monday and see who needs more time?
Since noone of these are around before Monday its not really apropriate.
If you want it earlier than Thursday as usual I would say Wednesday.
Giving everyone a chance to react to any failures found and the
tagging/branching needed.
/max
>
> Nick
>
> On 11/27/2013 07:11 AM, Max Rydahl Andersen wrote:
>> On Tue, Nov 26, 2013 at 02:56:19PM -0500, Nick Boldt wrote:
>>> Yes, that could work.
>>>
>>> When does the whole Brno team disappear for the holiday shutdown /
>>> PTO? That is, when is the last *effective* date when we have a QE team
>>> to review & approve the Alpha build?
>>
>> Recall that for the alpha builds we only wanted very basic testing and
>> it wouldn't really prevent us from doing the alpha1 build - at most just
>> provide input on wether
>> we would publish jboss tools alpha1 to marketplace or not.
>>
>> I'm suggesting we move the codefreeze to Thursday next week, but lets
>> finalize the
>> date on the pm call today.
>>
>> /max
>>
>>
>>>
>>> Nick
>>>
>>>
>>> On 11/26/2013 02:50 PM, Alexey Kazakov wrote:
>>>> Thursday, Nov 28 is not good time for code freeze because of
>>>> Thanksgiving in USA.
>>>> Can we move it to Monday, December 2?
>>>>
>>>> Slava is on PTO this week.
>>>> I took a day off on Wednesday (+ Thursday and Friday)
>>>> Denis, Daniel - Thursday, Friday
>>>>
>>>> So it's pretty hard to freeze base, jst, javaee this week for us.
>>>>
>>>> On 11/20/2013 08:51 AM, Nick Boldt wrote:
>>>>> I know we're barely half way through the testing cycle for JBDS
>>>>> 7.1.0.CR1, but in order to be able to get a first Alpha for JBDS 8
>>>>> out
>>>>> by year's end, we need to start looking at building JBDS 8 on
Luna
>>>>> ASAP.
>>>>>
>>>>> To that end, Mickael will be producing a new Luna M3 target platform
>>>>> this week - watch for that email w/ instructions.
>>>>>
>>>>> The goal is to test building your projects w/ Luna, so that if
you're
>>>>> a project who tends to be broken every year by upstream API
>>>>> changes in
>>>>> platform or WTP (eg., hibernate tools), you can find those problems
>>>>> and fix them ASAP. Or if necessary, report problems upstream.
>>>>>
>>>>> Attached is a screenshot of the proposed schedule for the first 3
>>>>> milestones of JBDS 8. I'm hoping to have code freeze for JBDS 8
>>>>> Alpha1
>>>>> next Thursday, Nov 28, so that we can get Alpha1 out in early
>>>>> December.
>>>>>
>>>>> Cheers,
>>>>>
>>>>
>>>
>>> --
>>> 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
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio