Hallo! * J�rg Schaible <[EMAIL PROTECTED]> wrote: > Jan Schulz wrote: > Well, it depends. In case of final releases, you're probably right, but in > case of the milestones it is another case. But they should be masked > anyway ...
IMO: if you want to have a milstone release, you can have one, not more. If you want to go back, just downgrade. If you have a screwed up workspace, you shouldn't have used a risky package :) >> True. Unformtunatelly the big API breakage chnages were made so late >> and now I have my exams coming up and won't really be able to > yeah, they're really not shy to mess-up their code competely ... ;-) Hm, I think there are worse. At least the cover the changes pretty well. The bigegr problem was the moving around and rearaging for RCP. I will try to have packages for RCP, platfrom (The IDE layer) and JDT and wanted to do that in one go. In the initial plan, the RCP changed should have been made until end of September. That was the time of my uni break... > OK, in case of EARs they're very often commercial and therefore out of focus > of Debian anyway, but WARs can be detected more often as OSS. Basically > it's not different to webapps realized in PHP, it's just that there are a > lot less ISPs offering JSP/servlets on servers for private people at > interesting prices and therefore we have less applications. But looking at > the large Java developer community, I suppose the number of free webapps > and even EARs will grow. Hm, there will probably come up a lot of problem the first time someone starts to package such a thing. What fun... Jan -- [EMAIL PROTECTED] mailing list
