On 9/9/07, Sergiu Dumitriu <[email protected]> wrote:
On 9/5/07, Vincent Massol <[email protected]> wrote:
What we could do is have a version like 1.0-1.1 (<xeclipse>-<XE>) but that sounds way way too complex.
I think I prefer simply documenting it on xwiki.org and inside XEclipse itself. It should check the XE version it's connecting to and tell the user if it's not compatible with it IMO.
WDYT?
+1
XEclipse is a distinct project, with its own releases. Documenting the dependencies should suffice.
Sergiu
Fair enough. Like I said, it sounded sort of silly to me as well-- I was just wondering if making it more explicit would be useful. I use the xwiki version + a unique minor to keep track of extensions/patches I maintain for our install.. that way it will be clear when what I'm working on moves to 1.1, but what I've got is not standalone-- it's a patched xwiki installation.. -- 'Waste of a good apple' -Samwise Gamgee