|
View:
New views
2 Messages
—
Rating Filter:
Alert me
|
|
|
Towards 0.7Morning all
first of all well done to everybody for all the work made to get out the 0.6 release yesterday! Really well done:) While waiting for release guidelines to be written on the wiki (;)) we have to agree on a couple of points for the coming work; but first the status: 0.6 was tagged yesterday, at http://atalayasec.org/repos-public/atalaya/tags/release-0.6/ as the guidelines will show, this tag should be read-only. A branch exist at http://atalayasec.org/repos-public/atalaya/branches/REL_0_6/ that is where bug fixing for this release should happen. The files aren't on sourceforge yet, due to their crappy file management. I will upload them again tonight or tomorrow. Now, as for things coming next: *0.6.1 vs 0.7 what do we plan to include in the next release? If we are ok with releasing 0.7 within a couple of weeks we can save some merging. *Bug tracker It is _really_ important that we use it. Beside sourceforge requiring release notes to be uploaded upon release, it's really useful to open/close tickets to mark progress, and to report what has been done and what's left. In order for this to work we _need_ to not only open a bug, but to assign it to the right group (0.7, 1.0 and so on). Like this we can have a clear view of the status at each release milestone. So please, when fixing something or working on a feature, list it on the bug tracker, found at http://sourceforge.net/tracker/?group_id=198199 There is already a 0.7 group you can browse and add stuff to. *Is the SF's bug tracker any good? IMO it sucks, it's awkward to work with tickets and this is a big barrier for anybody with a moderate interest in using it (hello Giacomooo:)). There are some alternatives (I don't include commercial stuff like JIRA) -trac: used broadly, pretty nice. given the constraints the only option is hosting it at atalayasec, but I'm not sure we want to assume this overhead as well. -launchpad.net : I don't know it much, I'd like to see if it's possible to use just the tracker. It can import from SF tracker. hosted. what do you guys think? I'm taking the time of making the SF tracker up to date, if we want to migrate fine, but let's decide it quickly. If we don't we all have to bear with SF:) byeee F ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Atalaya-developer mailing list Atalaya-developer@... https://lists.sourceforge.net/lists/listinfo/atalaya-developer |
|
|
Re: Towards 0.7I'm going straight to the main points:
I think we should plan a 0.7 release in a couple, max 3 weeks; it should include: -bugfixing at will (currently the only relevant bug known is the IE polar chart issue) - host delete - cis xml version About bugtracker: sf got the advantage that it is already there and we don't need to start up another tool; i vote to go on with sf and i promise i will put more effort on bugs auditing thanks, On Jan 11, 2008 10:14 AM, Francesco Vivoli <f.vivoli@...> wrote: Morning all -- Giacomo Collini - CISSP Information Security Analyst email: giacomo.collini@... mobile: (+34)628332736 ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Atalaya-developer mailing list Atalaya-developer@... https://lists.sourceforge.net/lists/listinfo/atalaya-developer |
| Free Forum Powered by Nabble | Forum Help |