Re: Release preparations update

Hi Hussayn,

Short answer: yes they are in sync - seen from the trunk.
Medium answer: trunk and our release candidate are in sync in the way 
that all* changes we made to the release branch are merged back to the 
trunk and some fixes/enhancements made to the trunk are merged back to 
the release branch. So except new features in the trunk since creation 
of the release branch they are in sync. The way it should be. Johannes 
can surely tell you more about merging now...
Long answer: omitted

Releasing a 1.0.23 in the near future is fine, see my february post; web 
2.0 too (isn't 2.0 a little outdated already?-)
BUT I think it would be good to have a (at least small) roadmap to be 
discussed. We have some features too on our list (partly implemented 
already) and I think some thoughts on the underlying infrastructure, in 
the broader sense, can't be wrong too(!). Maybe that overlaps partly 
with your web-2.0 thoughts.
But let's keep calm, finish the release and then we can come back on this.

Frank
www.memocomp.de

* there should be no relevant differences, but maybe not "all" in the 
sense of absolute identical

Am 23.04.2010 12:26, schrieb Hussayn (de):
> Hi, Frank and Johannes;
>
> Glad to hear that the 1.0.22 release is finally on its way to finishing. I
> have seen
> that you have recently updated the documentation in trunk. I meanwhile have
> updated our biggest production instance with the newest version of trunk and
> so
> far we have seen no degradations. From the previous emails on this list i
> now
> conclude that trunk and your release candidate are more or less in synch now
> ?
> That would be great news!
>
> Maybe i should mention that trunk is again about to move forward to the next
> iteration...
> I will report on our current plans shortly. But beware... Our goal is making
> Scarab web-2.0
> compliant ;-)  (not easy, but doable...)
>
> Hope to see the release 1.0.22 soon. From the amount of time passing between
> 2 releases
> it might be a good idea to proceed with release preparations for 1.0.23
> immediately after
> releasing 1.0.22 has come out ;-) I think that this time i have to put some
> effort in the
> release process as i badly need to document the new features and clean up
> some of the
> weird short cuts currently living in trunk...
>
> cheers,
> Hussayn
>
>
> Frank Freund-2 wrote:
>    
>> Hi all,
>>
>> as announced some weeks ago, we have done the testing of the release
>> branch and are preparing for the next pre-release steps.
>>
>> On all systems described below we performed new installations of scarab
>> 1.0.22 and an upgrade from 1.0.21 using revision 10966 from the release
>> branch.
>> * Ubuntu 9.04 AMD64 using Tomcat 5.5.26, sun jdk 1.5.19, ant 1.7.1,
>> mysql 5.1.30
>> * Win7/64 using tomcat 5.5.28, sun jdk 1.5.21, ant 1.8.0, mysql 5.1.45
>> * Internal (permanent) test system: Debian4 (etch) AMD64, tomcat 5.5.20,
>> sun jdk 1.5.0-10, ant 1.6.5, mysql 5.0.23
>>
>> As all tests passed smoothly we will go ahead providing a release
>> candidate 1.0.22-rc1 (keeping 1.0.21 the current production release) and
>> advertise this on the scarab projects home page.
>> We will provide zip and tar.gz archives of the rc1 and the documentation
>> (separately, as it changed quite a lot) for download.
>> As usual in this context, *we appreciate any feedback*.
>>
>> Frank
>> www.memocomp.de
>>
>> ------------------------------------------------------
>> http://scarab.tigris.org/ds/viewMessage.do?dsForumId=455&dsMessageId=2593345
>>
>> To unsubscribe from this discussion, e-mail:
>> [[email protected]].
>>
>>

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=455&dsMessageId=2593423

To unsubscribe from this discussion, e-mail: [[email protected]].