Preparing for MXP 0.5 Release

[Tommi Laukkanen]

Hi

Created a wiki page about the release process according to Akoses
mail:

http://www.bubblecloud.org/wiki/-/wiki/Main/Release%20Process

Prepared google code issues template and labels for end user defect
reporting:

http://code.google.com/p/setp/issues/list

Feel free to comment / edit either.

-tommi

[Maróy Ákos]

Tommi,

> Created a wiki page about the release process according to Akoses
> mail:
>
> http://www.bubblecloud.org/wiki/-/wiki/Main/Release%20Process

I made some updates - please review...

Akos

[Tommi Laukkanen]

Good additions :)

--
You received this message because you are subscribed to the Google Groups "Metaverse eXchange Protocol" group.
To post to this group, send email to metaverseexc...@googlegroups.com.
To unsubscribe from this group, send email to metaverseexchangep...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/metaverseexchangeprotocol?hl=en.

[Tommi Laukkanen]

I might add distribution build targets to nant build files this weekend. Any preference on how we should call that target? I wonder whether we should build separately .NET and mono distributions? I have understood that there might be some difference in the bytecode generated by mono and .NET compilers.

-tommi

[Maróy Ákos]

Tommi,

> I might add distribution build targets to nant build files this weekend.
> Any preference on how we should call that target? I wonder whether we

a 'dist' target would the fine IMHO, that would generate the
distribution. in terms of C# and Java, I wonder if it makes sense to
create a separate 'source' and 'binary' distribution - maybe we could
just include the binary .jar / .dll file in the dist, along with the
source code?

or maybe, because a simple binary distribution package would be way
simpler / smaller (gist the .jar / .dll and the documentation), it still
makes sense to have different tarballs.

> should build separately .NET and mono distributions? I have understood
> that there might be some difference in the bytecode generated by mono
> and .NET compilers.

hm, I don't know the .NET framework that much. would a .dll generated by
.NET run in a mono environment? if so, I think we would be fine with that..

(similarly in Java, there are a number of JDKs / compilers, which
generate a little bit different bytecode, but they run in each others
environment, the point being they are all conformant to the JDK spec)

Akos

[Tommi Laukkanen]

It looks like prebuild and nant do not support doc generation tools so I need to write a shellscript for building the distribution packets. Ugly but works and should be easy to translate to linux as well. Separate source and binary distributions sound good to me.

-tommi